Rat Stack systems
Each shipped system has a page with its behavior, standard, and checks.
- Hosted agent interfaces6 — Discovery documents, HTTP, MCP, A2A, and bounded code mode21 expose the public reference to agents.
- Analytics18 — One event per HTTP request, stored unchanged for queries to select and interpret later.
- Auth16 — Email and password sign-in through Better Auth16, with the signed-in person provided to each RPC call.
- Capabilities21 — Named application actions exposed through generated interfaces share one definition and one server-side implementation.
- Database7 — One interface records action runs and their outcomes in either Cloudflare D1 or Postgres through Hyperdrive.
- Devtools7 — Development-only capabilities inspect calls and lifecycle transitions without entering production bundles.
- Fence5 — The lint rules, compiler diagnostics, hooks, and gate that make a bad shortcut fail instead of asking an agent to avoid it.
- Feature flags5 — Typed feature flags with owners, removal dates, and stable subject rollouts.
- Interest signup12 — Agent-only applications start email confirmation11 through interfaces owned by core and delivery implemented in a separate package.
- Learn mode presents concepts at useful depths10 — An agent presents source-derived concepts during real work and keeps learning events in a private local log.
- One prompt serves people and agents5 — Source-owned agent prompts with typed discovery and copyable browser pages.
The interest signup12 page separates submission, confirmation, and delivery. Devtools7 stays development-only. The hosted agent front door6 records discovery, MCP27 versions, API, A2A, and sandbox limits; extracting it into a generic cartridge36 remains future work.