tgss-mem

Memory #86 CURRENT

Frame-class alignment principle Any Lydian-stack primitive that lives in both storage AND on the wire MUST align to the LCF frame classes (NANO/STANDARD/BULK/ARCHIVE) from the umbrella §6.6.1, not hand-pick a standalone size Whenever we design a new on-the-wire + on-disk primitive — HLR records, API request/response envelopes, clock-cycle heartbeats, settlement messages, biometric challenge/response, etc. — size it to match one of the four LCF frame classes (NANO 256 B, STANDARD 1024 B, BULK 4096 B, ARCHIVE 16384 B) rather than deriving a new size from first principles. **Why:** The stack already commits to the four-class system (umbrella V2.2 §6.6.1, TRIVA-Go shipped with 118 tests validating it). Any new primitive that diverges from it creates a translation layer between "my format" and "LCF." One primitive per semantic unit; LCF is the framing primitive for the whole stack. **How to apply:** - First draft: ask "which LCF class does this fit?" *before* picking a size - Small records (state transitions, heartbeats, simple events) → NANO primary_payload (96 B) - Default (wallet ops, attestations, enrollments) → STANDARD primary_payload (416 B) - Payload-carrying records (LatticeSigs, embeddings, multi-witness ring) → BULK primary_payload (2048 B) - Snapshots / bundles → ARCHIVE primary_payload (8192 B) - If no class fits cleanly, the RIGHT move is to argue for a 5th class in the umbrella, NOT to invent a parallel sizing **Origin:** 2026-04-24, HLR-001 design pass. I initially proposed 48 B then 96 B for HLR records based on (4,1)-cascade geometry. Mark pointed out the existing 4-class LCF system should be the sizing source, not first-principles derivation. Result: HLR revised to a multi-class design (NANO for transitions, STANDARD for ops, BULK for witness-ring records, ARCHIVE for snapshots). Mark explicitly flagged this principle will recur for "API and clock cycles" work — applies there too. **Names to watch for this pattern:** if a spec draft mentions byte counts that aren't `256 × 2^N` where N ∈ {0,2,4,6}, stop and reconsider alignment before the design freezes. — [feedback_frame_class_alignment.md]

Outgoing Edges

No outgoing edges.

Link to Another Memory