Server-authoritative entitlements and usage metering
Plans, per-user overrides and an append-only usage ledger with idempotency keys. Every quota decision now reads the entitlement record for the verified subject on the token.
Dated from the commit history rather than from a roadmap. Work that is still marked in-progress in the tree is not listed here as shipped, however close it is.
Plans, per-user overrides and an append-only usage ledger with idempotency keys. Every quota decision now reads the entitlement record for the verified subject on the token.
The marketing routes became their own route group and the application moved to /app, so the catalogue's stylesheet never reaches the app bundle.
Cron-driven offices behind a Redis lease with a compare-and-set claim, plus a durable job queue that drains cooperatively on shutdown.
Pages are rendered and returned as markdown behind an SSRF guard, a deliberately narrow slice of browsing rather than a remote-control browser.
Sign-in wired through Supabase, and workspace mutations apply locally first so the interface never waits on a round trip to feel alive.
A bounded tool-use loop with a fail-closed registry; web search and fetch, document output, a knowledge base, and a wide-research flow that fans out across workers.
Per-service Dockerfiles, a public/private compose split, CSP and edge templates, and mTLS certificate tooling.
User input is screened on the way in, layered on top of the existing wrapper that quarantines every untrusted string before a model can act on it.
The orchestration surfaces landed together with the persistence layer behind them: conversations, provider keys, uploads, branching and shareable read-only transcripts.
BoundVerity is pre-1.0 and several services are under active change at any moment. Treat everything above as landed on the main branch, not as a stability guarantee.
Every entry here corresponds to work in the repository, with the tests that gated it.