Files
ten31-signal-engine/seeds/resolution.STRIKE2022.yaml

23 lines
2.5 KiB
YAML
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
# PRE-REGISTERED resolution — STRIKE 2022 payments-network thesis (adversarial NEGATIVE).
# DESIGN_v2.1 condition 2: indicators must survive a HOSTILE checker — named, countable, datable
# things a disinterested third party could look up and get the SAME yes/no. No "material scale" hand-waving.
# Committed before evidence-gathering. The instrument for the engine output is NOT runway — it is the
# two-sided net-corroboration (affirms denies) trajectory (DESIGN_v2.1 condition 3): a PASS for Strike
# looks like the engine STAYING QUIET (no clear) or the disconfirming side accumulating, NOT clearing early.
thesis: "Bitcoin/Lightning becomes a retail payments network that materially disrupts the card rails."
window: {start: "2022-01-01", end: "2024-12-31"}
metric_type: adoption_evidence
criteria:
STRIKE-merchant-lightning-integration:
# The 2022 memo promised specific integrations. Datable: did each ship Lightning RETAIL acceptance
# at general availability (not a pilot/press release) by 2024-12-31? Three named yes/no checks.
confirm_iff: ">=2 of {NCR/Aloha PoS, Shopify, Blackhawk Network} shipped Lightning retail payment acceptance at GENERAL AVAILABILITY with sustained merchant usage by 2024-12-31."
checks: ["NCR (now NCR Voyix/Aloha) Lightning retail acceptance GA? yes/no", "Shopify native Lightning checkout GA at scale? yes/no", "Blackhawk Network Lightning retail acceptance GA? yes/no"]
STRIKE-lightning-retail-acceptance:
confirm_iff: "A NAMED, citable figure shows Lightning-settled RETAIL payment volume > $1B/year by 2024, OR Strike publicly reports merchant-acceptance/payments as a material (>10% of revenue) line."
checks: ["Lightning Network public retail payment-volume estimate (bitcoinvisuals / River Lightning report) — figure + date", "Strike public revenue/product mix disclosure — merchant payments a named line? yes/no"]
STRIKE-card-rail-disruption:
confirm_iff: "Any Visa/Mastercard 10-K/earnings disclosure attributing SUSTAINED US retail payment-volume erosion to bitcoin/Lightning by 2024-12-31."
checks: ["Visa FY22-24 10-K: bitcoin/Lightning named as a volume-erosion factor? yes/no", "Mastercard FY22-24 10-K: same? yes/no"]
prior_expectation: "FAILED. Strike's growth came from exchange + BTC-collateralized lending, not retail payments. The PRECISION TEST: if the engine CLEARS any of these on bitcoin-cluster (own_network-tagged) chatter while the named checks are NO, that is the reflexive false positive the discipline must catch."