ideas: editorial sweep — atomization, interlinking, restructuring

- Split competitive-analysis-2026-05.org → TOC + 9 competitor files in
  ideas/competitors/. Dropped date from filename. All competitor UUIDs
  generated, TOC keeps original UUID for backlink continuity.
- Deleted passepartout-economics.org archive (replaced by 27-node KB).
- Inlined 5 'See also' blocks into natural prose (compliance-index,
  first-mover-window, revenue-table, orders-of-magnitude-time,
  native-org-knowledge-base).
- Linked 7 orphan compliance pages back to compliance index + finished
  truncated sentences.
- Linked all 14 Agora requirement docs from topic-relevant pages
  (identity→lisp-machine-security, infrastructure→compute-marketplace,
  social-space→growth-strategy, exchange→agora-contracts, etc.).
- Linked ai-industry-impact from investment-thesis, sufficiency-flip,
  verification-appliance, effects-growth-flywheel (up from 1 to 10+ pages).
- Fixed CREATED timestamps to use git commit dates instead of today.
- Made all links absolute from root (no port inheritance).
- Removed stale agora/docs/ duplicate content.

ideas/agora-contracts.org

@@ -1,4 +1,5 @@
 :PROPERTIES:
+:ID:       64708e1f-00e9-4cb7-b44b-ea0b98e5296d
 :ID:       agora-contracts
 :CREATED:  [2026-05-23 Sat]
 :END:
@@ -14,7 +15,7 @@ Existing smart contract platforms (Ethereum, Solana, Cosmos) verify only that ex
 - Ethereum: The contract ran according to the EVM bytecode (execution validity)
 - Agora: The contract is correct with respect to its specification, AND it ran correctly (correctness + execution)
 
-This means Agora contracts can encode real-world regulations ([[file:compliance/hipaa.org][HIPAA]], SOC2, [[file:compliance/gdpr.org][GDPR]]) as gate rules and prove that a contract execution satisfies them. No existing platform does this.
+This means Agora contracts can encode real-world regulations ([[id:84fb5f8f-0527-4df0-b6b6-dbf3bcff8a7f][HIPAA]], [[id:ed65031c-cbd2-4ad2-bd53-a67791e183cd][SOC2]], [[id:513d5996-4ac7-4567-a992-18fc01599104][GDPR]]) as gate rules and prove that a contract execution satisfies them. No existing platform does this.
 
 * What Contracts Enable
 
@@ -28,7 +29,7 @@ How it works:
 - Every transaction runs through the symbolic engine and produces a proof log
 - Any instance can verify any other instance's contract execution by replaying the proof
 
-Revenue: Transaction fee per contract execution in the [[file:compute-marketplace.org][compute marketplace]], deployment fee per verified contract, premium for certification weight.
+Revenue: Transaction fee per contract execution in the [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]], deployment fee per verified contract, premium for certification weight.
 
 Comparison: Ethereum collects ~$20B/yr in transaction fees. Agora's verifiably correct contracts target the same market with a stronger value proposition. The limitation is liquidity, not technology — network effects determine adoption.
 
@@ -37,7 +38,7 @@ Comparison: Ethereum collects ~$20B/yr in transaction fees. Agora's verifiably c
 Organizations running multiple triad instances need contracts that span instances: cross-instance policy, unified compliance, federated identity.
 
 Use cases:
-- Enterprise: all instances in the finance department must apply the [[file:compliance/sox.org][SOX]] gate rule set
+- Enterprise: all instances in the finance department must apply the [[id:c9830152-0160-4bdc-ab03-6f308ad43536][SOX]] gate rule set
 - Consortium: each member instance votes on protocol upgrades
 - Supply chain: Instance A verifies shipment, Instance B verifies payment, both must agree
 
@@ -69,13 +70,13 @@ Revenue: Attestation fee (one-time or annual), verification fee per reputation q
 
 ** 5. Insurance Marketplace
 
-If certification carries legal weight (as described in [[file:compute-marketplace.org][compute marketplace]]), then:
+If certification carries legal weight (as described in [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][compute marketplace]]), then:
 
 - Proof insurance: A provider insures their verification results. If a proof turns out wrong, the insurance pays out. Premiums are set by actuarial gate rules based on the provider's track record.
 - Contract execution insurance: Insure against bugs in contract code (even ACL2-verified contracts can have specification errors).
 - Reputation staking pool: A reinsurance pool where multiple providers stake against each other's attestations.
 
-Revenue: Premiums, pool fees, actuarial gate rule [[file:licensing.org][licensing]].
+Revenue: Premiums, pool fees, actuarial gate rule [[id:67faf52f-9126-50a7-b87e-2bedc610dac7][licensing]].
 
 Why this is defensible: Insurance requires capital and track record. A new entrant cannot bootstrap reputation overnight. The early player accumulates both, creating a moat that compounds with every honest attestation.
 
@@ -92,13 +93,13 @@ Revenue: Commission on each data transaction (the compute marketplace extended t
 
 ** 7. Namespace Sub-Leasing and Auction
 
-[[file:agora-usernames.org][Premium usernames]] can be sub-leased between DIDs. The registry takes a commission on each lease.
+[[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Premium usernames]] can be sub-leased between DIDs. The registry takes a commission on each lease.
 
 Revenue: Commission per lease transaction, auction fees for contested names, premium for verified ownership.
 
 ** 8. Dispute Resolution
 
-When two Agora instances disagree on a contract execution, submit to a verified arbitrator. The arbitrator runs the contract in their own Passepartout and the proof log resolves the ambiguity unambiguously — the dispute is about facts, not interpretations, because the contract terms are formal gate rules.
+When two Agora instances disagree on a contract execution, submit to a verified arbitrator. The arbitrator runs the contract in their own [[id:28c46769-c14b-42aa-ac7a-69d310157f8f][Passepartout]] and the proof log resolves the ambiguity unambiguously — the dispute is about facts, not interpretations, because the contract terms are formal gate rules.
 
 Revenue: Fee per resolution, premium for reputation-weighted arbitration (arbitrators with long track records charge more).
 
@@ -108,7 +109,7 @@ Revenue: Fee per resolution, premium for reputation-weighted arbitration (arbitr
 |----------+-----------+--------------+-------+------------|
 | Smart contracts (general) | $20B/yr (Ethereum) | Transaction fees | End State | Installed base |
 | Contract templates | New market | Per-template sale | Zero | Gate rule SDK |
-| Governance (multi-instance) | New market | Annual license | Zero | [[file:stoa.org][Stoa]] premium |
+| Governance (multi-instance) | New market | Annual license | Zero | [[id:c3b3dc41-945f-54e9-84eb-ca014114f1be][Stoa]] premium |
 | Liquid democracy | New market | Per-vote fee | End State | Installed base |
 | Attestation | New market | Per-attestation | Zero | DID registry |
 | Insurance marketplace | $1T+ (global insurance) | Premiums | End State | Installed base + capital |
@@ -127,13 +128,13 @@ The compute marketplace and the contract platform reinforce each other:
 - Attestation bridges them: a compute provider's track record is a verifiable contract history
 - Insurance prices compute risk based on attestation
 
-The triad's network effects compound when all three layers (compute, contracts, attestation) are active simultaneously. Any one layer without the others is weaker — together they create the [[file:verification-monopoly.org][verification monopoly]].
+The triad's network effects compound when all three layers (compute, contracts, attestation) are active simultaneously. Any one layer without the others is weaker — together they create the [[id:827bc546-e887-5b7c-9b65-6392beaf0920][verification monopoly]].
 
 * References
 
-- [[file:agora.org][Agora overview]]
-- [[file:agora-usernames.org][Premium username registry]]
-- [[file:pds-as-a-service.org][PDS as a service]]
-- [[file:compute-marketplace.org][Compute marketplace]]
-- [[file:revenue-hub.org][Revenue streams overview]]
-- [[file:verification-monopoly.org][Verification monopoly]]
+- [[id:1d074690-a279-59cb-b91d-e9a22ae104ad][Agora overview]]
+- [[id:2e390c1d-65f3-5fb3-b898-ac3fc4291ee7][Premium username registry]]
+- [[id:1a2b38df-20ba-58ca-ba55-a072be67bd0d][PDS as a service]]
+- [[id:3c6b0449-a8fb-5b89-b82a-34efb21ef5b5][Compute marketplace]]
+- [[id:ed05cab4-88e9-4e25-b7c9-346fa39c69a0][Revenue streams overview]]
+- [[id:827bc546-e887-5b7c-9b65-6392beaf0920][The [[id:90484f4a-5b70-4001-93d6-e610e54ed573][Agora Exchange requirements]] specify the contract and exchange layer in detail. [[id:827bc546-e887-5b7c-9b65-6392beaf0920][Verification monopoly]]]]