docs: rebuild canonical LifeOS baseline from current main

[seonghobae]

Why

PR #126 captured valuable canonical product/architecture documentation but its long-lived branch materially diverged while protected main integrated readiness governance, trusted-source provenance, authentication-age/recent-auth hardening, the durable data-rights request ledger, and later the durable Today synchronization slice. Resolved historical review threads are not sufficient proof that the old branch is code-current.

PR #140 is the clean successor integration path. It was created from protected main and is continuously reconciled when protected main advances; the current canonical baseline is f4cae6d83eadb00019d2962a650c55c59a3349ae.

Canonical baseline

• docs/PRD.md and docs/TRD.md
• root ARCHITECTURE.md
• normalized ADR 0001/0002 plus ADR 0003-0009 and docs/adr/README.md
• docs/DATA_MODEL.md logical service-owned ERD
• docs/UML.md component/sequence/deployment/failure views
• docs/API_CONTRACTS.md
• SECURITY.md + docs/THREAT_MODEL.md
• docs/PRIVACY_DATA_LIFECYCLE.md
• docs/TEST_STRATEGY.md
• docs/OPERABILITY.md
• docs/RELEASE_AND_MIGRATION.md
• docs/STANDARDS_TRACEABILITY.md
• docs/TRACEABILITY.md
• docs/DOCUMENTATION_ASSESSMENT.md
• README/AGENTS/CLAUDE/CHANGELOG alignment
• deterministic documentation-contract.test.mjs

Current-state reconciliation

The baseline explicitly distinguishes protected-main, active-PR, Partial, Planned and Superseded behavior. It now records:

• browser-only local-first/private/single-app/UUIDv7 historical options as Superseded by the current multi-user server-backed modular MSA + UUIDv4 architecture
• fix(readiness): separate canonical buyer gaps from capability maturity #131 buyer-gap accounting on protected main
• feat(identity): preserve authentication age across session rotation #134-feat(identity): persist data-rights request receipts #138 authentication-age, recent-authentication and durable data-rights request/receipt foundations on protected main
• PR feat(planning): add durable Today synchronization #127 merged as protected main f4cae6d83eadb00019d2962a650c55c59a3349ae; issue Add durable Today workspace synchronization with optimistic concurrency #121 is closed completed and current readiness reports three unresolved canonical buyer gaps instead of four
• Add encrypted per-user calendar credential lifecycle and provider selection #129 / PR feat(calendar): require trusted workspace context #139 trusted calendar workspace context as active-PR prerequisite while the full per-user credential lifecycle remains Partial
• Add complete tenant export and deletion orchestration #55 complete export/erasure orchestration as Partial
• Complete plugin installation, secrets, and outbound delivery trust boundary #130 plugin runtime as Planned
• Bind required PR source verification to exact contributor heads without losing merge-tree compatibility evidence #132 exact contributor-head vs merge-tree verification attribution as Planned

Documentation contract

Canonical status fields are restricted to:

Implemented on protected main, Implemented on active PR, Partial, Accepted architecture, Planned, Research only, Superseded, Out of scope.

The documentation test checks canonical paths, README local link targets, balanced fenced blocks, exact status vocabulary, exact ADR index targets/required sections, selected source/migration claims, and buyer-gap traceability against product/buyer-gaps.json.

Recovery discipline

The temporary read-only formatter workflow used to materialize exact repository Prettier output was removed after applying its artifact. PR #126 remains open until this successor proves current exact-head/live-base checks/review and preservation of unique durable canonical content; only then should #126 close as superseded.

This PR remains Draft until the current exact head completes the applicable repository checks/review after the latest reconciliation. Documentation completion is not a product-completion condition; after integration the autonomous loop continues the highest-value executable buyer gap.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a8e31c8b-9eb1-435f-bacc-de527474e9fe

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[seonghobae]

Superseded by #144. The complete reconciled canonical documentation tree from this branch was materialized byte-for-byte onto a new one-commit branch whose parent is current protected main f4cae6d83eadb00019d2962a650c55c59a3349ae; the temporary PR140 repair workflow was intentionally omitted. Keeping #140 open would duplicate checks and preserve stale branch ancestry without adding unique current product evidence.