Roadmap ideas: what's next for TokenOps

[tishachawla-jg]

TokenOps is early (0.x). This is a running list of near-term directions we're considering, moved here from the README so it has room for actual discussion instead of sitting as a static bullet list nobody can comment on.

Under consideration

• User/tag segment-scoped budgets. The machinery for this already exists in the ledger; the default seed is run-only today. Would you want budgets scoped by user_id, a custom tag, or something else?
• Optional fail-closed integrity. Refuse a call outright when a run has no registration, or when a budget is missing/exceeded, instead of the current fail-open behavior in ambiguous cases.
• Remote observe/decide (a "fatter" plane). Move more of the governance decision loop into the control plane itself, for multi-host stacks where the SDK-side Governor can't see the whole picture.
• A documentation site, instead of everything living in the README + docs/.

How to weigh in

• Comment below on any of these, or reply with a different direction entirely.
• If you want to pick one up, check good first issue / help wanted first — a few of these already have open issues tracking the concrete next step.
• Bigger feature sketches or RFCs are exactly what this category is for; feel free to open a new Ideas thread rather than piling everything into one.

Status of each control-plane job: docs/control-plane-status.md.