← Church Machine

Figure 28 — Scale-Free Security Model

Identical security mechanisms — Golden Token + NS entry + CALL lump split + mLoad validation — apply at every scale: individual, family, school, and organization. Outform GTs (type=10, F-bit auto) bridge namespace boundaries. The architecture scales without changing the security model.

Identical Security Mechanism at Every Scale GT + NS Entry + CALL Split + mLoad → same invariants whether one child or one million users Individual: Alice Private namespace — her own digital shadow NS Table @7 Memory (clistCount=2) @28 MyRobot (clistCount=3) @29 MyGame (clistCount=1) MyRobot Lump Code (X) C-List (L) Same mechanism: Inform E-GT → mLoad validates → CALL splits lump → CR14(X) + CR6(L) Alice's abstractions are isolated — no one can reach in without a valid GT Revoke GT → instant access cut (version increment) Family: Parent + Children Parent namespace governs children's namespaces Parent NS Alice NS @28 Bob NS @29 Family @30 Alice NS Bob NS Same mechanism: Parent holds E-GTs into children's namespaces C-list IS parental approval — children cannot access beyond their c-list Revoke child's GT → instant isolation (grounding!) Outform GT (type=10, F-bit auto) crosses NS crosses NS School: Classrooms + Students School namespace contains classroom namespaces School NS Classroom1 @28 Classroom2 @29 SharedLib @30 Negotiate @32 Classroom 1 Alice, Bob, Carol Classroom 2 Dave, Eve, Frank Negotiate @32: dual-approval (parent+teacher) Same mechanism: Teacher holds E-GTs into student namespaces Schoolroom @29 abstraction: teacher's c-list grants access to shared resources Cross-classroom sharing requires Negotiate (dual-approval) Organization: Departments + Teams Org namespace contains department namespaces Org NS Engineering @28 Finance @29 HR @30 Audit @31 Engineering Teams + services Finance Ledgers + reports HR Records + policy Same mechanism: Org admin holds E-GTs into department namespaces Department isolation: Finance cannot reach Engineering without Outform GT Audit gets read-only GTs (R perm) — same GT mechanism, different grants Outform GT (type=10, F-bit auto) The Invariant: One Mechanism, Any Scale Golden Token Version(7) | Index(17) Perms(6) | Type(2) Unforgeable, revocable Same format at all scales NS Entry (3 words) W0: location W1: type | clistCount | limit W2: CRC seal Navana is sole writer CALL Lump Split clistCount → clistStart CR14 = X-only (hardcoded) CR6 = L-only (hardcoded) Domain purity enforced mLoad Validation Type → Version → Seal → Bounds → Perms → F-bit 7-step pipeline Every access, every time GT Type Taxonomy — Bridging Scales 00 = NULL Zero value, no capability 01 = Inform Points to local NS entry 10 = Outform Points to remote NS (F-bit auto) 11 = Abstract GT IS the value (constants) Inform GTs stay within a namespace. Outform GTs cross namespace boundaries — same mLoad pipeline, F-bit triggers tunnel. Alice (individual) ↔ Family ↔ School ↔ Organization: Outform GTs are the edges; namespaces are the nodes.
Individual namespace
Family namespace
School namespace
Organization namespace
Outform GT (cross-namespace)
Invariant mechanism