Factory floor
Cell 00 · CommandLive view of every autonomous line. Loops run unattended; the tape below tracks spend against budget in real time.
Portfolio
Machine cells queue 0
Factory log
Agent loops
Cell 01 · Line designA loop is a production line: ordered stages, each staffed by an agent role bound to a model tier. Tier routing is where cost optimization happens — cheap models for mechanical stages, strong models where judgment matters.
Builds
Cell 02 · Greenfield lineDefine the scope of an enterprise application, get a deterministic cost estimate before any model is called, then release it to a loop. The factory halts automatically if a run threatens its budget cap.
New build order
Build orders
| Order | Loop | Status | Est. | Actual |
|---|
No build orders yet. Estimates are computed locally from your scope numbers — no tokens spent until release.
Run
Legacy bay
Cell 03 · Maintenance lineRegister the systems you keep alive. Confidence is scored from a transparent rubric — coverage, docs, dependency freshness, churn, staffing — and every maintenance loop must raise it, never lower it.
Confidence rubric
| Factor | Weight | What raises it |
|---|---|---|
| Test coverage | 30% | Regression suite present and green; every patch ships with a test |
| Documentation | 20% | Runbooks, architecture notes, and this factory's auto-generated system docs |
| Dependency freshness | 20% | Runtime and libraries inside vendor support windows |
| Change safety | 15% | Small, reviewed, reversible patches; hash-logged history |
| Knowledge redundancy | 15% | More than one person (or documented agent loop) able to operate it |
Cost control
Cell 04 · LedgerEvery model call is metered against an editable price sheet. Set a monthly budget, watch the burn, and let the optimizer recommend cheaper tier routing where quality allows.
Monthly budget
No budget set
0Metered calls
$0.0000Avg cost / call
Price sheet editable · $/MTok
| Model | Tier | In | Out |
|---|
Every column is editable — model string, tier routing, and rates. Rates seed from published list prices; changes flow into estimates, routing, and metering immediately.
Optimizer
Run at least one build or maintenance loop and the optimizer will analyze the ledger for cheaper routing with equivalent output quality gates.
Ledger
| When | Run | Stage | Model | Tokens | Cost |
|---|
No metered calls yet.
Revenue
Cell 05 · Front officeTurn factory output into engagements. Quotes are cost-plus with the formula in the open: your delivery cost comes from the estimator, your price covers risk and value. Margin is tracked live against actual metered spend.
| Engagement | Order | Status | Price | Cost | Margin |
|---|
No engagements yet. Create one, link it to a build order, and the margin column tracks itself.
Documentation
Cell 06 · RecordsThe embedded operator guide, plus live system documentation generated from the factory's actual state — loops, price sheet, budgets, registered systems.
Settings
Cell 07 · Power roomProvider keys are encrypted with AES-256-GCM under a passphrase you choose and never leave this device. The factory tries providers in the order below and falls through on failure.
Key vault locked
First unlock with a new passphrase creates the vault. Keys are encrypted at rest (AES-256-GCM, PBKDF2-SHA-256 · 310k iterations) and decrypted only in memory for this session.
Local engines
not loaded · $0 marginal cost when active
FORGE verification backend
FORGE executes generated code and tests in isolated processes so builds earn a real VERIFIED status. Start it with FORGE_TOKEN=… node forge-server.mjs. It is process isolation, not a security sandbox — containerize for untrusted bundles.
Provider order
Anthropic → OpenAI → Gemini → Groq → Ollama → LM Studio → WebLLM. A stage uses the first available provider offering its tier; local engines meter at $0.
Data
storage: detecting…
Audit trail
| When | Event | Detail |
|---|