Concepts

Seven words carry the whole product.

Cell. A company, a department, or the holding above them. Each cell has its own checkout and its own ledger, draws its own pipelines and workloads, and reads only its own books. The portfolio level of the map is the cells as boxes.

Pipeline. A line of stages that something moves through — a candidate business, a release, a support ticket. Declared in one yaml file per pipeline: stages, the verbs between them, who answers for each, what each stage needs and produces. The map draws exactly what the file says.

Stage. One box on a pipeline. It has a question (asks), the evidence it expects, the workload that runs it, its handoff (what it needs, what it produces, where it exits), and a gate: human, agent, rule or script.

Workload. A scheduled run of an agent under a sandbox — through Claude Code on a seat, or through SoloINC's own native runtime on a provider key or a local engine — with a brief assembled from the contract, the agent's persona, its skills, the standing rules, its workload prompt and the stage's own instruction. The Runs panel is its history; the Trace button is one run call by call.

Desk. What waits on a human. Every item there arrives as a memo in its domain's professional form with the documents the stages wrote. Approve, continue, send back with a question, release a parked item with a direction for the retry. Nothing before the Desk asks you.

Managing Agent. The seat that runs the company day to day: reads the briefs, keeps the pipelines moving, writes the daily brief to the Human, and acts inside the bounds the contract sets. Pro.

The Human. The one person in the loop. Owns the passphrase, the seat, the switches (API, interop doors, channels), and the acts agents may never take. Everything else is theirs to watch, not to do.

Two more words appear on every screen: a lens is which facet of the same map you are looking at (Flow, Work, People, Draw, Risk, Time), and a verb is a declared transition between two stages, with its gate.