Summary
Agents still construct Store("tokenops.db") (or equivalent) and pass it into run scopes / governance paths. That leaks persistence into the integration API and encourages treating the agent as a co-owner of the ledger DB — residual of §4 hybrid local DB when a remote plane is available.
Area: Store constructor on TOKENOPS_DB, scope helpers taking store=, agent examples
Desired behavior
- Context manager / SDK talks to the control plane via APIs (register, resolve run, fetch governance config, record spend / observe — as appropriate).
- SQLite (or any backend) stays behind the plane; agents do not open the DB file for governance.
- Aligns with §4 (no inlined plane): ledger + config only via plane HTTP.
Acceptance sketch
- No
Store(path) in example agent servers for governance.
- Integration code depends on
ControlPlaneClient (or successor), not on SQLite schema.
Reference: docs/notes/2026-07-23-design-fix-notes.md §6 (residual of §4)
Summary
Agents still construct
Store("tokenops.db")(or equivalent) and pass it into run scopes / governance paths. That leaks persistence into the integration API and encourages treating the agent as a co-owner of the ledger DB — residual of §4 hybrid local DB when a remote plane is available.Area:
Storeconstructor onTOKENOPS_DB, scope helpers takingstore=, agent examplesDesired behavior
Acceptance sketch
Store(path)in example agent servers for governance.ControlPlaneClient(or successor), not on SQLite schema.Reference:
docs/notes/2026-07-23-design-fix-notes.md§6 (residual of §4)