Operator manual
Production State Layout
Separate immutable source/release material from mutable sovereign state so upgrades and recovery do not blur evidence boundaries.
Recommended separation
| Area | Contents |
|---|---|
| Release checkout | Immutable/pinned v3.4.2 source and protocol files. |
| ENTITY state | Identity manifests/keys, registries and mutable protocol state. |
| BTDU state | ADAM atomic state and btdu_index.sqlite. |
| Evidence/content | Content-addressed evidence/artifacts where deployment uses them. |
| Backups/exports | Encrypted recovery material and manifests, separate from live state. |
| Qualification evidence | Test reports, roots, source hashes and campaign metadata. |
Source control boundary
Do not place live keys, runtime databases or backups inside the repository. The public repo intentionally excludes production state.