Development

Streams

About the pictures on this page. They are rendered from the built console over a demonstration data set, not from a live fleet — a screenshot of somebody's real record would publish their work. What the pictures are evidence of is the layout, the chips and the acts; every number in them is sample data.

A stream is one unit of work with its own worktree and branch; a train is a set of streams — wagons — under one order.

Active shows the trains running now. Pick one in the left rail, with its wagons done over total on the right, and the table lists that train's wagons: id, what it proves, review state, and state (done · in review · development · queued) with the commit or the elapsed time. The head carries the train's facts — backend, seat, counts — and the acts to open the train's order and to stop it.

Backlog lists what is designed and not yet dispatched. Done lists closed streams, newest first.

Runners (Advanced)

The legs running right now and the plan for the next ones: which machine, which seat, which backend, how long, at what cost so far — and the exact saphan run … line the engine composed for each, with Copy. A leg that stopped shows why, in the engine's own words.

Bug Harvester (Advanced)

Defects the fleet filed about itself, in a queue by class. The tiles count the queue; the table shows each class with its instances, the flag that admitted it, and the repair train it rides.

Nothing here is written by a human's opinion — a defect enters with a measurement and leaves with a merged repair.

Reports

One dashboard, one picker. The select beside the title chooses the report: Dashboard · Delivery · Gates · Cost · Trains · Flow · Capacity · Tests · Defects · Laws · Compliance audit · Metrics.

Each report is one plate: a row of tiles — a number, what it counts, and one line of context, never a bare figure — then a chart, then tables. Filters for period and train sit above the plate, and Export gives you the plate as a document.

Charts are bars and lines with labels on the marks. There are no donuts, and colour carries state or series only, never decoration.

• Cost shows spend by day and billing class, quote against actual against cap, and cost by backend and by role — in USD, always with the unit.
• Delivery shows burndown and burnup per train, and cumulative flow of wagon states.

Prompt Library (Advanced)

The prompts the roles use, as documents. Built-in prompts ship with the product and are replaced in place by an upgrade; yours are forks or new documents, and an upgrade never deletes your words.

The left list filters by role, tag, scope and language. The editor shows title, tags, which roles it is for, its inputs — the holes the caller fills — a Markdown check, and Send to verification: a dry run on a seat of your choice, with its estimated cost. Copy as new forks a built-in.

Docs (Advanced)

Process documentation the fleet generates from the record: one chapter per train. The title is a sentence; four facts stand above the fold — delivered, released, cost with its class, document digest — then seven sections in a fixed order: what it delivers and refuses, the decisions it stood on, the wagons, how it was checked, how it landed, what it left behind, and the ledger. Then exhibits.

The same chapter comes in three profiles — internal, public, audit. What a profile withholds is stated at the foot of the document, never hidden.