Part IX. Company and Investing · Chapter 80
Moats, Partnerships, and Standards
Every quantum company claims a moat; few can say what would still be true about their advantage if a well-funded competitor started tomorrow. This chapter separates durable advantage from press, grants, and conference logos.
In this chapter 9 sections
A defensible moat changes customer switching cost or the company’s learning rate through controlled rights, hard-to-reproduce evidence, embedded interfaces, or compounding data; test it against standardization, partner exit, backend substitution, and time.
A moat claim needs a counterfactual: what happens if the partner leaves, an interface standardizes, the preferred backend becomes replaceable, or the team has twelve months to imitate the asset? Partnerships and standards can accelerate learning or distribution, but association alone creates no controlled right.
Moats require a counterfactual
The register separates asset, legal right, observed adoption, embedded workflow, switching procedure, exclusive duration, partner dependency, data accumulation, and renewal evidence. It then runs four survival tests. The residual advantage can be a renewable execution lead without being permanent exclusion.
Dated rights-and-dependency register
A standards contribution survives only if adoption matters
A platform contributes to a standard and integrates deeply with two buyer workflows. The contribution itself is public, so exclusion does not survive. Migration tooling, compatibility data, and proven cutover procedure remain useful after a partner exit and can shorten delivery. The result is an execution lead that must be renewed, not an unassailable standards moat.
| Moat candidate | Controlled right | Survival test | Residual |
|---|---|---|---|
| Standards contribution | public specification | standardization | no exclusion |
| Partner access | revocable relationship | partner exit | fails |
| Migration data | contract-bound dataset | backend substitution | partial |
| Embedded workflow | deployed integration | twelve-month imitation | execution lead |
Artifact contract. A dated asset/rights/adoption/substitution table with executable survival tests. The claimed moat must survive at least one partner exit, one interface standardization event, and one backend substitution; rights and adoption evidence are recorded separately.
SCENARIOS = ("backend_substitution", "partner_exit", "standardization")
FIELDS = {"asset": str, "rights_basis": str, "adoption": dict, "survives": list, "source_id": str}
def falsify(dossier, minimum_deployments):
errors = []
coverage = {scenario: [] for scenario in SCENARIOS}
for row in dossier.get("assets", []):
missing = [name for name, kind in FIELDS.items()
if name not in row or type(row[name]) is not kind]
missing += [name for name in ("asset", "rights_basis", "source_id") if not row.get(name)]
adoption = row.get("adoption", {})
if type(adoption.get("value")) is not int or adoption.get("unit") != "deployments":
missing.append("adoption_schema")
unknown = set(row.get("survives", [])) - set(SCENARIOS)
if unknown:
missing.append("unknown_scenario")
if missing:
errors.append(row.get("asset", "asset") + ":" + ",".join(sorted(set(missing))))
continue
if adoption["value"] >= minimum_deployments:
for scenario in row["survives"]:
coverage[scenario].append(row["asset"])
uncovered = sorted(name for name, assets in coverage.items() if not assets)
decision = "invalid" if errors else ("renewable-execution-lead" if not uncovered else "unproven")
return {"decision": decision, "errors": errors, "uncovered": uncovered,
"survivors": {name: sorted(assets) for name, assets in coverage.items()}}
dossier = {"scenario": "platform moat red-team", "assets": [
{"asset": "owned integration playbook", "rights_basis": "company copyright",
"adoption": {"value": 6, "unit": "deployments"},
"survives": ["partner_exit", "standardization", "backend_substitution"],
"source_id": "scenario:deployment-ledger"},
{"asset": "preferred backend access", "rights_basis": "revocable agreement",
"adoption": {"value": 3, "unit": "deployments"}, "survives": [],
"source_id": "scenario:partner-contract"}]}
base_result = falsify(dossier, 2)
bad_assets = [{**dossier["assets"][0], "adoption": {"value": 6, "unit": ""}}, dossier["assets"][1]]
bad_result = falsify({**dossier, "assets": bad_assets}, 2)
low_adoption = [{**dossier["assets"][0], "adoption": {"value": 1, "unit": "deployments"}}, dossier["assets"][1]]
sensitive_result = falsify({**dossier, "assets": low_adoption}, 2)
assert base_result["decision"] == "renewable-execution-lead" and base_result["uncovered"] == []
assert bad_result["decision"] == "invalid" and "adoption_schema" in bad_result["errors"][0]
assert sensitive_result["decision"] == "unproven" and sensitive_result["uncovered"] == sorted(SCENARIOS)
print(f"PASS: 80 moat dossier base={base_result['decision']} survivors={base_result['survivors']} invalid={bad_result['errors']} low_adoption={sensitive_result['decision']}")Exact validation command: python3 tools/validate_briefs.py --briefs data/editorial_briefs_64_87.json --from 64 --through 87 --check-rewritten-sources --execute-artifacts
Partnership press is weaker than enforceable access
Value rights and adoption separately. Request license terms, data-use rights, integration depth, customer switching tests, and evidence that each deployment improves the next. Re-run the substitution and partner-exit scenarios annually. If the advantage depends entirely on access that can be revoked, price it as a dependency.
Run four falsification tests on a moat claim
Prompt. Falsify one claimed moat using partner exit, standardization, substitution, and time-decay scenarios.
Deliverable. Rights register, adoption evidence, switching workflow, four scenario results, residual advantage, and next review event.
Pass condition. The conclusion distinguishes owned rights from relationship access, uses observed adoption rather than membership, and weakens when a scenario removes the advantage.
Model answer: integration advantage, not permanent exclusion
Format. Integration moat recast as a renewable execution lead rather than exclusion.
The model answer passes the workflow-integration and learning-data tests, fails permanent exclusivity, and partially survives partner exit. It labels the residual advantage a renewable execution lead. The decision remains conditional on observed migration-time improvement and customer retention; standards membership and press announcements carry no independent weight.
Verification. The survival tests show which adoption and migration assets persist after partner exit and which claimed benefits disappear under an open interface.
Companion work
Artifacts for this chapter
These entries resolve to checked-in local source. Commands are reproduced exactly from the chapter manifest, and source-embedded fixtures are exported as direct downloads.
diligence dossier
Quantum moat falsification register
Reproduce or test
python3 tools/validate_briefs.py --briefs data/editorial_briefs_64_87.json --from 64 --through 87 --check-rewritten-sources --execute-artifacts
Provenance
Sources and review
- National Institute of Standards and Technology. Post-Quantum Cryptography Standards. NIST. 2024official standardization project
- Dustin Moody et al.. Transition to Post-Quantum Cryptography Standards. National Institute of Standards and Technology. 2024official transition guidance (initial public draft)
- OpenQASM Technical Steering Committee. OpenQASM 3 specification. Linux Foundation Joint Development Foundation. 2026official technical specification
- IBM Quantum. Qiskit documentation. IBM. 2026official documentation
- Google Quantum AI. Cirq documentation. Google. 2026official documentation
- Association for Computing Machinery. Artifact Review and Badging. ACM Publications. 2026official reproducibility policy
- Lieven M. K. Vandersypen et al.. A look at the full stack. Nature Reviews Physics. 2021peer-reviewed perspective
- National Academies of Sciences, Engineering, and Medicine. Quantum Computing: Progress and Prospects. National Academies Press. 2019consensus study report
The load-bearing claims in the chapter are mapped inline to this registered source set. A citation supports only the bounded claim beside it.