Cordy/Cairn
2
1
Fork 0
Code Issues 20 Pull requests Projects Releases Packages Wiki Activity Actions

docs(#158): v0.6 written from fact — backup story, sharp edges, ARCHITECTURE §11, milestone renumbering #170

Merged
Cordy merged 9 commits from docs-158 into main 2026-08-10 00:25:29 +00:00
Conversation 0 Commits 9 Files changed 5 +259 -25
Cordy commented 2026-08-10 00:25:15 +00:00
Owner
Copy link

The write-last docs for the v0.6 milestone, from the shipped and rehearsed system:

  • deployment.md: the three-layer model (config/bootstrap/state), "Connecting storage from the browser", the what-still-lives-locally table, the three deliberate boot refusals, and the rewritten backup story — backing up the backend backs up the whole instance, recovery drill = new pod + same config + same bucket (rehearsed live), sovereignty check extended to .cairn-state/ objects.
  • README: state travels with the backend; status → v0.6 with the recovery drill named; setup wizard in the storage bullet; the popup-free auth claim now stated structurally.
  • ARCHITECTURE: new §11 "Instance state in the backend (implemented)" (§12 = milestones), v0.5 bullet closed with its tag, the missing v0.6 milestone bullet added as closed, closed beta/public launch renumbered to v0.7/v0.8.
  • Helm values: honest persistence guidance — the volume is no longer load-bearing for identity on s3; it remains recommended for scratch.
  • CHANGELOG v0.6.0 (the milestone-close tag this merge receives).
The write-last docs for the v0.6 milestone, from the shipped and rehearsed system: - **deployment.md**: the three-layer model (config/bootstrap/state), "Connecting storage from the browser", the what-still-lives-locally table, the three deliberate boot refusals, and the rewritten backup story — *backing up the backend backs up the whole instance*, recovery drill = new pod + same config + same bucket (rehearsed live), sovereignty check extended to `.cairn-state/` objects. - **README**: state travels with the backend; status → v0.6 with the recovery drill named; setup wizard in the storage bullet; the popup-free auth claim now stated structurally. - **ARCHITECTURE**: new §11 "Instance state in the backend (implemented)" (§12 = milestones), v0.5 bullet closed with its tag, the missing v0.6 milestone bullet added as closed, closed beta/public launch renumbered to v0.7/v0.8. - **Helm values**: honest persistence guidance — the volume is no longer load-bearing for identity on s3; it remains recommended for scratch. - **CHANGELOG v0.6.0** (the milestone-close tag this merge receives).
docs(#158): ARCHITECTURE §11 state-in-backend + milestone renumbering + CHANGELOG v0.6.0
All checks were successful
ci / test-and-build (pull_request) Successful in 33s
Details
1b0e9569cc
Cordy merged commit 1da8ba6ac1 into main 2026-08-10 00:25:29 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Cordy/Cairn#170
No description provided.
Delete branch "docs-158"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?