A network needs jurisprudence, not just code. These are the rules every governed agent action clears under — the Auth·Clear·Settle lifecycle, the issuer/provider liability shift, the dispute reason-code matrix, and SLA-based automated arbitration. Every clause maps to a deterministic kernel that enforces it, and every attestation carries the network_rules_version these rules version under.
// schema-as-code: the versioned spec registry indexes every network specification — constitution · settlement instruction · these regulations · passport · the governance-kernel suite — each with its version, status, and conformance pointer. The single target members implement and self-certify against in CI. EcoCloud publishes and tests these specs; it issues no certification and sets no fees (measure, never money).
network_rules_version tag (this document = or-1).| Code | Condition | Liable |
|---|---|---|
| 10.4 | Unauthorized agent action — mutation outside the agent's Constitution scope | issuer |
| 10.5 | Hallucinated payload — wrote data to the SOR that didn't match input context | issuer unless acquirer skipped schema validation |
| 12.1 | Escrow bypass — executed without the mandated four-eyes approval (immediate network suspension) | issuer |
| 13.2 | Reversal failure — acquirer system failed a deterministic compensating transaction | acquirer |
Settlement_Instruction.json per member.Honest scope. These regulations are deterministically enforced by the kernels linked above + a versioned written rulebook (or-1) — they are not a live multi-member network. EcoCloud has the message grammar, the dispute jurisprudence, and the settlement schema; it does not run a federated switch or onboard acquirer members, and it never moves money (settlement amounts are a billable basis, a measure). This is the standard, published openly so issuers, acquirers, and auditors can build to it. See the Trust Layer for every enforcing kernel.