lay the keel. we fair the lines.

◉ 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.

1. 01
   ChatMode

   You state the goal in plain language — “solve the cut-list and stage the build sheet.” 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.

2. 02
   SmartModelRouter

   Each step is routed to a model that fits it — a fast model to sort orders and stock, a long-context model to read a long order history or spec, a strong reasoner to judge a reorder, a quote, or a schedule conflict — across the providers you register. Bring your own models and run them on your own infrastructure; your customer data, your pricing, and your supplier terms stays inside your network.

3. 03
   MCP tools · OBO credentials

   Agents reach your inventory system, your POS or order book, your supplier accounts, and your schedule 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.

4. 04
   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 inventory or cut-list tool, run it sandboxed, and discard it — credentials injected at runtime, run in a hardened sandbox, then discarded. No tool is registered, nothing persists.

5. 05
   AgenticWorkflows

   The orders-and-inventory flow becomes a flow of named agents — repeatable, auditable, on rails. And there’s more behind sign-up: reorder automation, scheduling and quoting flows, and the supplier-and-invoice reconciliation — the many ways the platform runs this, with more revealed after you sign in.

6. 06
   HITL approval

   Nothing acts until you say so. The human-in-the-loop gate is real architecture, not a setting — any step that would place an order or charge a customer 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.

7. 07
   Stay in the yard · agents handle the rest

   The build stays yours. Materials lists, supplier orders, the build documentation, the client updates — the agents run the periphery while you stay on the hull. You keep the long focus the boat demands instead of context-switching into admin, and nothing that goes to the owner leaves without your sign-off.

8. 08
   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. Reorder automation, scheduling and quoting flows, and the supplier-and-invoice reconciliation are waiting behind sign-up.