Global Store Consolidation — Vision
Mirrored from
docs/design/global-store-consolidation/3_vision.md. Edit the source document in the repository, not this generated page.
Future work should build on the workspace-scoped tables without making cross-workspace behavior implicit.
1. Open Questions
Section titled “1. Open Questions”- Should job-run archive state become an explicit SQLite column before Release N+1 removes legacy directories?
- Which admin command should own cross-workspace audit and run queries?
- Should high-volume v2 audit inserts be batched once real-world concurrent write pressure is measured?
2. Prior Work
Section titled “2. Prior Work”SQLite Audit
Section titled “SQLite Audit”The existing audit_events table established ~/.orbit/orbit.db as the global append-oriented store for CLI invocation audit data.
Workspace Registry
Section titled “Workspace Registry”The task registry established .orbit/config.yaml workspace_id as the stable workspace identity.
3. What May Be Distinctive
Section titled “3. What May Be Distinctive”The design deliberately keeps file-backed blobs and human-edited friction reports outside the global DB while still consolidating machine-only row data.
4. References
Section titled “4. References”- ADR-0183 — accepted consolidation decision.
- ORB-00276 — implementation task.
Task References
Section titled “Task References”- ORB-00276 — identified Release N+1 cleanup as future work.
Resolve any task above with orbit task show <ID> or git log --grep=<ID>.