◉ how our platform solves this · knowledge/edu
plan the city. we run the grid.
The plan is the point. But it rides on a tide of process — datasets gathered and reconciled, zoning and code checks, public-comment intake, the same figures re-pulled for every memo, the staff report assembled before any meeting. It is the work around the work, and the queue never empties.
◉ the answer
Agentic workflows run gather → verify → assemble on your own infrastructure — against your own models — with a human on the gate for anything that acts, and the record written as it goes.
◉ how we solve it · our process
- Chat — you state the goal in plain language; we shape the work with you.
- Flows — it becomes a repeatable workflow, on rails and fully auditable.
- Missions & Fleets — coordinated across as many instances as the job needs.
- Synth · Brainbow · Code Mode · Exec — the right tool spun up for each step: a throwaway utility, a driven browser, code run against your real systems.
- your ground, your gate — every step on your infrastructure, a human approving anything that acts.
◉ the mechanism · what actually happens
One request, walked end to end — every step on your infrastructure, against your own models, with a human on the gate.
- ChatMode
You state the goal in plain language — “check a parcel against zoning and file the submission.” ChatMode plans the work and dispatches its built-in agents — planning, data-query, validation, synthesis — to decompose it into pull, analyze, act, assemble. No prompt engineering, no scripts.
- SmartModelRouter
Each step is routed to a model that fits it — a fast model to sort and tag records, a long-context model to read long source documents, a strong reasoner to judge whether an answer is well-sourced — across the providers you register. Bring your own models and run them on your own infrastructure; your records, your patron data, and your unpublished material stays inside your network.
- MCP tools · OBO credentials
Agents reach your catalog, your document store, your LMS, and your reference databases as MCP tools, each call running under your own identity. The platform forwards your scoped credentials per call — no shared token, no pooled service account, no secret pasted into a prompt. Every call is logged.
- Tool Synthesis · Code Execution
Sources never agree on format. Code Execution writes a one-shot Python tool on the fly to write a one-shot ingest or cross-reference tool, run it sandboxed, and discard it — credentials injected at runtime, run in a hardened sandbox, then discarded. No tool is registered, nothing persists.
- AgenticWorkflows
The gather → verify → assemble flow becomes a flow of named agents — repeatable, auditable, on rails. And there’s more behind sign-up: collection-ingest automation, citation-and-source verification, and the research-digest flows — the many ways the platform runs this, with more revealed after you sign in.
- HITL approval
Nothing acts until you say so. The human-in-the-loop gate is real architecture, not a setting — any step that would publish or share the result stops and waits for a person; if no one approves, it times out and is denied. You review the plan and the scope, and approve before anything happens.
- Tool synthesis · the recurring work, off your plate
The repetitive planning toil — normalizing a parcel dataset, generating a summary table, reconciling two records — the platform turns it into a one-shot tool the moment you ask, runs it once under your approval, then discards it. Nothing persists. You spend your hours on the calls that need a planner, not the data wrangling around them.
- Audit trail · DLP · RBAC
Every model call, every tool call, every approval is written to an append-only audit log — once a decision is recorded it’s frozen, so the trail is tamper-evident. DLP keeps sensitive material inside your network, and role-based access scopes who can do what. It’s a record you can stand behind.
The toil ran itself, it acted only on your nod, and the record is already written — and that’s one flow. Collection-ingest automation, citation-and-source verification, and the research-digest flows are waiting behind sign-up.
◉ go deeper
Run it on your own infrastructure — or with us.
Talk to us to see the platform on your stack — governance, fleet, support, and the enterprise capabilities. Or self-host the platform in your own environment and run the whole thing today.
The platform self-hosts in your own environment — chat, flows, and the ops MCPs. Fleet, Mission, CodeMode, governance and support come with the enterprise platform. Designed for FedRAMP-High deployment.