[Modsofthenation]

Summary

Adversarial review found architecture / delivery docs claiming OS keychain, SQLCipher/Rusqlite-first, IPC-only topology, 12-person seed, and desktop CI on every main merge — none of which match the shipped code.

This PR rewrites the honesty layer in:

• docs/architecture/TRUST_MODEL.md
• docs/architecture/LOCAL_STACK.md
• docs/architecture/SYSTEM.md
• docs/DELIVERY.md
• docs/CORE_LOOP_EVAL.md

Shipped vs target is now explicit so a public adversarial review matches the code.

Test plan

• Docs-only change
• Spot-check links from README → TRUST_MODEL after merge

  

Summary by CodeRabbit

• Documentation
  • Clarified the demo-only nature of seed passwords and installer workflow.
  • Updated delivery and architecture guidance to reflect the shipped browser/API stack, optional desktop shell, and Node sidecar.
  • Documented workspace encryption, encrypted AI key storage, authenticated local connections, and encrypted backups.
  • Added warnings for sync-folder usage and clarified portability limitations.
  • Distinguished currently available security features from planned capabilities, including keychain support and signed updates.

[coderabbitai]

Warning

Review limit reached

@Modsofthenation, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 59 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c587fb1a-dc5d-4844-841b-43cb20c23493

📥 Commits

Reviewing files that changed from the base of the PR and between 393cb58 and e3bd53a.

📒 Files selected for processing (5)

• docs/CORE_LOOP_EVAL.md
• docs/DELIVERY.md
• docs/architecture/LOCAL_STACK.md
• docs/architecture/SYSTEM.md
• docs/architecture/TRUST_MODEL.md

📝 Walkthrough

Walkthrough

The documentation now reflects the shipped browser/API and Tauri/Node stack, workspace encryption, encrypted AI keys, backup behavior, delivery workflow, demo data, and shipped versus unshipped security capabilities.

Changes

Local stack documentation

Layer / File(s)	Summary
Local stack and topology docs/architecture/LOCAL_STACK.md, docs/architecture/SYSTEM.md	The architecture now documents optional Tauri, authenticated Hono loopback HTTP, SQLite, sealed storage, app-data files, and launch capability tokens.
Storage and security status docs/architecture/LOCAL_STACK.md, docs/architecture/SYSTEM.md, docs/architecture/TRUST_MODEL.md	The documentation records workspace-secret encryption, encrypted SQLite snapshots, sync-folder warnings, API export redaction, and shipped versus unshipped security features.
Delivery status and operating notes docs/DELIVERY.md, docs/CORE_LOOP_EVAL.md	Delivery notes now describe the shipped vertical slice, current packaging workflow, locked defaults, demo seed handling, and remaining targets.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: cursoragent

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/docs-trust-alignment-9b7f

---

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