Skip to content

feat(triparty): governed-triparty marketplace contract (netting cell + bundles)#192

Closed
mdheller wants to merge 1 commit into
mainfrom
feat/triparty-marketplace-contract
Closed

feat(triparty): governed-triparty marketplace contract (netting cell + bundles)#192
mdheller wants to merge 1 commit into
mainfrom
feat/triparty-marketplace-contract

Conversation

@mdheller

@mdheller mdheller commented Jul 4, 2026

Copy link
Copy Markdown
Contributor

Stage 2 of the 5 handoff specs — the marketplace/settlement layer from the Governed Triparty Netting Fabric whitepaper. The three-party clearing cell that couples value + proof + authority + disclosure and governs release/refund/export by policy rather than confidence.

  • NettingCell — three legs (A/B counterparties, C clearing/verifier), each carrying value / capability-right / proof kept distinct (evidence ≠ permission). stage (Observed→…→Released→Exported / Refunded / Reversed), truthClass (PROVEN⊐ATTESTED⊐INFERRED⊐REPUTED), admissibility (evidence⊇admit⊇release⊇export — export stricter than local validity), policyKernelRef, reserveRef, and an optional supplyChainRef so a cell can clear a supply-chain trade.
  • TripartyBundle — the typed proof-carrying bundle (intent/acceptance/escrow/fill/verification/export) that advances a cell, carrying payload + proof + attestation (the Truth Record) so release is a function of evidence + admissibility + freshness.

Composes over the Truth-Engine constitution and ties into the TriTRPC/membrane moat. Examples + tools/validate_triparty_examples.py + make validate target; both validate.

🤖 Generated with Claude Code

…+ bundles)

Stage 2 of the 5 handoff specs — the marketplace/settlement layer from the
Governed Triparty Netting Fabric whitepaper. The three-party clearing cell that
couples value + proof + authority + disclosure and governs release/refund/export
by policy rather than confidence.

- NettingCell: three legs (A/B counterparties, C clearing/verifier), each
  carrying value / capability-right / proof kept DISTINCT (evidence != permission).
  stage (Observed→Proposed→Ready→Escrowed→Filled→Verified→Released→Exported /
  Refunded/Reversed), truthClass (PROVEN⊐ATTESTED⊐INFERRED⊐REPUTED), admissibility
  (evidence⊇admit⊇release⊇export — export stricter than local validity),
  policyKernelRef, reserveRef, and an optional supplyChainRef so a cell can clear
  a supply-chain trade.
- TripartyBundle: the typed proof-carrying bundle (intent/acceptance/escrow/fill/
  verification/export) that advances a cell, carrying payload + proof + attestation
  (the Truth Record) so release is a function of evidence + admissibility + freshness.

Composes over the Truth-Engine constitution + ties to the TriTRPC/membrane moat.
+ examples + tools/validate_triparty_examples.py + Makefile target. Both validate.
@mdheller

mdheller commented Jul 4, 2026

Copy link
Copy Markdown
Contributor Author

Superseded by #195 (cockpit contract pack) — merged to main in c516779.

@mdheller mdheller closed this Jul 4, 2026
@mdheller mdheller deleted the feat/triparty-marketplace-contract branch July 4, 2026 23:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant