Belt64 is a 64-bit address belt topology for encoding the adelic ocean state. Each of 64 segments maps to an adelic layer or silo address space. The belt is continuous — it has no start or end, like a Möbius strip with 64 faces. This mirrors the baobab trunk's circular addressing: L0 pressure connects back to L13, and the adelic spine loops through all layers without a terminal state.
The belt64 encoding compresses an arbitrary-depth adelic state into a 64-segment address that any silo can read. A silo with belt64 capability can decode any belt64-encoded item and restore the full adelic pressure profile. This is the key to cross-silo retrieval: belt64 items written by one silo can be read by any other silo without protocol negotiation.
The belt orbits the baobab trunk. The trunk (L0) provides the γ₁-pressure that drives the belt's rotation. Segments glow in γ₁ harmonic sequence: the glow period of segment i is γ₁/(i+1) seconds. This is the same formula as the adelic spine pressure — belt64 and the adelic spine are dual representations of the same underlying structure.
The 64 segments are divided into system segments (L0–L13, segments 0–13) and silo-specific segments (segments 14–63). System segments are fixed — they map to the 14 adelic layers and cannot be reassigned. Silo-specific segments are assigned at fleet initialization and can be reconfigured during belt64 chaos recovery.
| SEGMENT | ADELIC LAYER | PRESSURE rₐ | CONTENT TYPE | SILO |
|---|---|---|---|---|
| 0 | L0 TRUNK | 14.1347 | Main reservoir | msi01 |
| 1 | L1 UPPER TRUNK | 7.0673 | Active distribution | msi01 |
| 2 | L2 BRANCH JUNCTION | 4.7115 | Splitting point | msclo |
| 3 | L3 LOWER BRANCH | 3.5336 | Secondary distrib. | msclo |
| 4 | L4 LEAF PETIOLE | 2.8268 | Episodic deployment | yone |
| 5 | L5 STOMATAL | 2.3557 | Gate pressure | yone |
| 6 | L6 MESOPHYLL | 2.0196 | Active processing | forge |
| 7 | L7 EPIDERMIS | 1.7668 | Surface expression | forge |
| 8 | L8 CUTICLE | 1.5706 | Outer boundary | pcdev |
| 9 | L9 | 1.4138 | Near-surface | pcdev |
| 10 | L10 | 1.2850 | Deep surface | lilo |
| 11 | L11 | 1.1779 | Near cold | lilo |
| 12 | L12 | 1.0872 | Cold zone | NAS |
| 13 | L13 COLD FLOOR | 1.0096 | Cold storage floor | NAS |
| 14–63 | SILO-SPECIFIC | — | Custom addressing | Fleet-assigned |
Draining the adelic ocean onto belt64 storage: the drain protocol reads the adelic pressure at each layer and encodes it into the corresponding belt64 segment. Which silos are belt64-capable: msi01, msclo, yone, forge (all system-segment capable). lilo and pcdev are partially belt64-capable (segments 10–13 only).
The γ₁ pressure determines drain order: highest pressure = first drained = L0 (segment 0). This ensures the most loaded layer is always emptied first. Drain command: pemos belt64 drain --layer all --pressure-order desc. The drain fills segments in order 0→13 first, then 14→63 by silo priority.
Drain metrics: compression ratio = adelic_pressure × segment_efficiency. Typical ratio for L0: 14.1347 × 0.85 = 12.01. For L13: 1.0096 × 0.92 = 0.929. The belt64 encoding is more efficient at high pressures (trunk) than at low pressures (cold floor).
Storing compressed adelic state in belt64 format: after drain, each segment holds a compressed snapshot of its layer's state. The Methanogen school optimizes belt64 storage by applying deep compression (no byproducts, no enrichment debt) at the cost of retrieval speed.
Store command: pemos belt64 store --segment all --school methanogen. Output: a 64-segment belt64 bundle (JSONL format) with each segment containing: layer_id, pressure, compressed_state, fc3_seal, gamma1_anchor, methanogen_hash. The bundle is written to NAS at /eose/belt64/bundles/YYYY-MM-DD/.
Compression ratio: adelic_pressure × storage_efficiency (Methanogen = 0.97). Bundle size: typically 4–12MB for a full fleet snapshot. Retrieval time from NAS cold storage: 2–8 seconds depending on NAS load.
Belt64 chaos mode occurs when the belt topology becomes inconsistent — segments out of order, pressure mismatches between adjacent segments, or the belt's circular addressing breaks (segment 63 cannot link back to segment 0). Chaos is triggered by: (1) silo crash mid-drain, (2) NAS disconnection during store, (3) concurrent write conflicts from multiple silos, or (4) belt geometry corruption from a failed recovery.
Chaos indicators: segments glowing out of γ₁ harmonic sequence, water particles reversing direction, pressure values outside expected bounds (e.g., segment 0 pressure < 14.0 or > 14.3). The /belt64-chaos route shows the current chaos state and recovery steps.
Recovery path: (1) halt all belt64 write operations, (2) drain all items to the Boabixer Basin (basin acts as the safe recovery buffer), (3) reset the belt geometry to the known-good segment map, (4) re-drain from basin to belt64 in strict order. The basin → belt64 path is the standard chaos recovery. The basin never goes chaotic — it is the chaos recovery anchor.
The belt64 is the baobab's external root storage. When the trunk (L0) is full (adelic pressure approaching saturation), overflow drains to belt64. Belt64 then routes to NAS cold storage. The full archival chain: Trunk (L0) → Belt64 (segments 0–13) → NAS cold storage (/eose/belt64/).
The Boabixer (bonixer) is the routing intelligence layer above the belt. The belt64 is the storage geometry below. Together: Boabixer decides where to route, belt64 decides how to store. The basin sits below both — it catches what the boabixer couldn't route and what the belt64 couldn't store.
Boabixer-belt64 interface: the boabixer writes a routing intent record to the belt64's segment 0 buffer. The belt64 storage engine reads the routing intent and places the item in the correct segment. If placement fails (segment full), the item flows to the basin. The basin → belt64 → NAS cold storage is the full archival chain, and it is guaranteed to complete as long as the NAS has available space.
Retrieval: (1) address lookup — provide the belt64 address (segment number + item ID). (2) Segment decode — read the compressed state from the segment's NAS bundle. (3) Adelic pressure restore — decompress and restore the item's adelic pressure profile to its origin layer.
Retrieval command: pemos belt64 retrieve --address SEG:ID --restore-pressure. The --restore-pressure flag re-injects the item into the adelic spine at its original layer with the original pressure. Without this flag, the item is returned as raw compressed data without re-injection.
Retrieval from belt64 chaos state: use the --chaos-mode flag which reads segment data by content hash rather than address order, bypassing the broken circular addressing. Hash-based retrieval is slower (O(n) scan) but works during chaos.