tgss-mem

Memory #138 CURRENT

σ₁/σ₃ Duality — Architectural Pattern for Sovereign-over-Standard Canonical Tribernachi pattern where a sovereign primitive rides encapsulated through a standards-compatible carrier, hash-bound via TCHAS; applies transport, identity, and future layers Confirmed 2026-04-19 while reviewing APP.TGSS-SSH.09 (dual-protocol coexistence). **Pattern:** Two channels share one substrate; each carries different information; they do not interfere. The sovereign primitive (PrIA-native) rides inside a standards-compatible carrier, with a TCHAS-256 hash attestation binding the two identities together. Three-phase progression: Encapsulated → Hybrid → Native. **Canonical reference:** `D:/GitHub/tgss-mem/docs/implementation/APP.TGSS-SSH.09-dual-protocol.md` §11 ("The dual-protocol design follows the σ₁/σ₃ duality that runs through the entire Tribernachi framework: two channels sharing one substrate, each carrying different information, neither interfering with the other"). **Existing applications:** - **Transport layer (TGSS-SSH.09):** PrIA identity ↔ MAC address, bound by TCHAS attestation, GEO frames ride EtherType 0x88B5 through legacy Ethernet. - **Identity layer (planned, APP.TTI.WALLET-INTEROP-001):** PrIA alias prime ↔ P-256 keypair, bound by TCHAS attestation; alias-derived content rides inside SD-JWT VC / mdoc / W3C VC envelopes. **Reusable library naming:** `libgeocoexist` (transport); follow-ups should match the convention (e.g. `libidcoexist`). **Three-phase ladder (when to apply):** 1. **Encapsulated** — sovereign primitive travels inside the standard carrier; ship day-one with no new standards registration needed. 2. **Hybrid** — dual signatures / dual addresses / dual primitives coexist on the same artifact; verifiers pick whichever they understand. 3. **Native** — sovereign primitive becomes first-class after registration with the relevant standards body (IANA, IEEE, W3C, ISO). **Why:** Mark emphasized 2026-04-19 that internal applications and code already tunnel through traditional IP communication paths, and hash-based certificates/encoding are the Tribernachi norm. The pattern is architectural, not a workaround. **How to apply:** - When proposing any Lydian-to-external interop, check first whether the σ₁/σ₃ pattern is the right frame. - Use TCHAS-256 as the binding primitive between sovereign and standards-compatible identifiers — consistent across layers. - Present progression as Encapsulated → Hybrid → Native explicitly; do not hide the concession that Phase 1 uses the external curve / algorithm. - Match library / spec naming to the existing `libgeocoexist` convention. — [project_sigma_duality_pattern.md]

Outgoing Edges

No outgoing edges.

Link to Another Memory