Product Model
Campaign Truth
Clarify workspace truth, the .bardo root, and the hosted service boundary.
Bardo is strict about where authority lives so your AI client does not confuse hosted account services with campaign truth.
Local source of truthLink to local-source-of-truth
Your workspace is the source of truth. Bardo-managed artifacts live under .bardo/, and your original campaign files stay the primary inputs.
Hosted service boundaryLink to hosted-service-boundary
The hosted side is limited to:
- bridge approvals
- auth and token refresh
- billing and entitlements
- API-key introspection
- protected account logic
The hosted side does not own campaign files, write local state, or decide the campaign for you.
How to think about the splitLink to how-to-think-about-the-split
If something depends on your campaign files, it belongs to the local workspace. If something depends on identity, approval, or billing, it belongs to the hosted side.
Migration noteLink to migration-note
.bardo/ is the canonical managed root. Legacy bardo/ workspaces are migrated one way into .bardo/ and should not be treated as an ongoing dual-layout mode.