WIKI TIER ARCHITECTURE 4 TIERS MLW HEART FC QUEUE LINEAGE TTL=NEVER γ₁=14.134725141734693 γ₁ = 14.134725141734693
§1 — THE FOUR WIKI ORGANS
Documentation is not one thing. Like a body, it has organs with different biological roles — teaching, operating, proving, protecting. A wiki that flattens these roles into "pages with permissions" is not a wiki. It is a drawer. PEMOS V13 gives the wiki organs.
TIER 1 — PUBLIC MEMBRANE L0/L1
RoleTeaching. Onboarding. Public trust formation.
WhoAnyone. No SOSTLE required.
ContentELI5 concepts, what-is-this, why-does-it-exist, one-example-per-concept
TTL30d review cycle
FC QueueNo — public, no review gate
RequirementEvery concept MUST have a Tier 1 page before it may appear in Tier 2.
Test: "Can a non-technical person read this and understand what problem it solves?"
Gap rule: If Tier 1 missing → concept is probably still fog.
TIER 2 — CREW TISSUE L2/L3
RoleOperating. SRE manual. Per-silo implementation.
WhoCrew + GID-validated agents
ContentRunbooks, MCP endpoints, known cracks, spine details, per-silo implementation
TTLSource-hash + 7d operational TTL
FC QueueYES → publish enters FC queue, reviewable
Requiredowner, silo, wall, source-hash, last-tested, linked KCF, MCP tool, SORRY, raincheque
Promotion path: Tier 1 must exist first. Then CLO or crew-lead approves Tier 2 publish.
TIER 3 — SOVEREIGN SKELETON L4/L5
RoleProving. Legal memory. Decision lineage.
WhoCLO bench + Admirals
ContentARBs, TRBs, Latin verdicts, why-not-chosen options, debt birth certificates
TTLLINEAGE NEVER EXPIRES. Status annotations can update.
FC QueueYES + CLO sign-off required
Requireddecision, authority, options tried, deferred raincheque, debt created, evidence chain, verdict
Key rule: Every matter that exits in a Latin verdict MUST have a Tier 3 record.
MLW — PRIVATE HEART L6/L7
RoleHuman sovereignty vault. Family/private artifacts.
WhoKay Joffe only. No agent access without explicit confirmation per asset.
ContentCape Town photos, family context, private history, personal artifacts
TTLNo expiry. No auto-surface.
FC QueueNO. Never.
No automatic promotion. No public indexing. Design surface requires explicit per-asset confirmation. No cross-wall leakage.
§2 — THE GAP ENGINE · Wiki Coverage Scores
Every silo has a wiki coverage score. Missing tiers = architectural debt. Formula: coverage = T1×0.2 + T2×0.35 + T3×0.35 + MLW×0.1
SiloT1 (×0.2)T2 (×0.35)T3 (×0.35)MLW (×0.1)Coverage
msi01100%
msclo90%
yonepartial72%
forgepartialpartial55%
lilo❌ GAP❌ GAP20%
loungepartial❌ GAP❌ GAP10%
pcdevpartialpartial55%
§3 — THE FC QUEUE PIPELINE
Tier 2 publish is not "save." It is "deploy." Just as code must pass through the build system, crew wiki content must pass through the FC (Fermentation Chamber) queue — reviewable, challengeable, freshness-checked.
1. DRAFT → Tier 1 page created
Concept gets ELI5 page. No gate. Anyone on crew can create Tier 1.
2. TIER 2 SUBMISSION → enters FC queue
Technical runbook submitted. FC queue receives it. Status: pending review.
3. FC REVIEW → source-hash verified, technical claims checked
Required fields checked. Source-hash verified against live implementation. Technical accuracy validated.
4. APPROVED → live in Tier 2 crew wiki
Page goes live. Operational TTL (7d) starts. Source-hash pinned.
5. CLO REVIEW REQUEST → Tier 3 elevation with Latin verdict
Major decision or ARB outcome submitted for CLO bench review. Latin verdict issued.
6. SEALED → Tier 3 lineage record, TTL=never
Decision sealed. Lineage record created. PROBATUM EST or IMPRIMATUR issued. TTL = never.
§4 — MLW BOUNDARY PROTOCOL
🔒 THE HEART IS LOCKED. BUT THE BODY KNOWS THE HEART EXISTS.
The protocol:
1. MLW asset registered with: asset_id, type, owner, locked=true, no_index=true
2. Design surface request: explicit intent required, per-asset, not per-collection
3. Confirmation event: "design surface confirmed: [asset_id] for [purpose] by [authority]"
4. After confirmation: asset may appear in design context ONLY for stated purpose
5. No cascading exposure: one confirmation ≠ open access to all MLW