A unified, interactive reference bridging CIRISConstitution@rc17, CIRISServer, CIRISClient, CEWPOS, and CEWP: the closed catalogue of 20 topologies (T0βT19), 105 CSD cards (101 in CIRISClient across 22 files [43 CSD/4 four-field + 58 earlier bullet cards] + 4 CEWPOS cards CSD-CEWPOS-001..004), 191 namespace families, 474 constitutional transitions, 17 role tokens, and 12 governance policies running live against the browser-executable CEWP kernel. The CSD-to-namespace mapping is CEWP's synthesis of CIRISClient/CEWPOS cards against CC rc17's namespace_registry.json (191 families) and csd4_chain.json (156 vocabulary atoms, 152 state-table atoms, 110 promised atoms across T0..T19, catalogue v6).
In traditional decentralized software, application interfaces, network protocols, and cryptographic rulebooks drift apart. Client developers build UI screens with ad-hoc assumptions; server teams invent unconstrained RPC APIs; and formal rulebooks exist only as abstract mathematical proofs disconnected from what a user actually clicks.
CSD/4 (Card-first Specification Design, 4-field card format: shows / reads / emits / checks), grounded by Cornerstone Invariants X1βX5, completely eliminates this drift. It bridges five core repositories into an unbroken formal loop:
Instead of permitting arbitrary, untestable graph topologies, CSD/4 proves that every human and device interaction in the epistemic web maps into a closed catalogue of 20 canonical topologies (T0βT19). Each topology is a formal state trace with explicit initial preconditions, step-by-step actions, and constitutional promises.
| ID | Title & Story | Key State Atoms & Promises | Cards | Families |
|---|
[start, end)
State in CSD/4 is not a static property; it is step-indexed. Atoms exist during specific, bounded transient windows [start, end) during which constitutional actions must be performed:
T0 node.unclaimed [0, 1): A fresh device waiting for key establishment. Exists exclusively at step 0; transitions immediately to node.claimed at step 1.T3 device.join_requested [3, 4): Ephemeral pairing negotiation window. Admits approve or refuse from an existing authenticated device.T5 member.applicant_pending [4, 5): Applicant waiting on community quorum threshold voting before admission or decline.T8 root.halted [1, 2): Emergency brake suspension window where standard mutations are refused until quorum confirmation resumes or revokes the root.T10 key.membership.proposed_evict [18, 19): Isolation window before key revocation and quorum eviction of compromised hardware (key.membership.evicted).
Formal cross-plane safety properties verified by CewpNode.tla (CIRISConstitution rc17 formal/cewp_node/README.md:54-58) over the normalized state table:
accord_halt) freezes agent operations without creating a trust edge. The latch moves no standing, stops no serving and no replication, and moves exactly the agent's act gate; a latched node can still serve and replicate (ENABLED).local_only) never leaves its node and never crosses a federation link; a served row is always a signed federation-tier row.
The CSD/4 simulator does not brute-force mesh states. It runs a subset-search cost-minimizing planner that finds the optimal sequence of actions folding an initial topology into a destination topology (e.g., folding T0 into T2 at steps 1 & 2: claim node, key holder, pair room) with zero redundant round trips.
formal/STATE_TABLE.tsv)x_private:* refusal vectors (RefusedPrivateNamespace) Β·
3 retired holds_bytes refusal vectors (RefusedRetiredHoldingClaim)
Note on Remaining Atoms: The 6 file.durable.* atoms (file.durable, file.durable.at_target, file.durable.below_floor, file.durable.descending, file.durable.recovered, file.durable.unmarked) correspond to the target-holder replication durability tier (CC 6.1.5) and await the planned T20 durability topology.
| Family Pattern | Category | Authority | Roles Required | Trans. | Referencing CSD Cards | Details |
|---|
Test any wire namespace against the CC RC17 segment dimension grammar running live in kernel.js.
The matcher validates dimension counts, vocabularies, hex encodings, aliases, and version segments, resolving the canonical family and all admissible transitions.
-
-
| Verb | From β To | Roles | Scope | Policy |
|---|