Redkale · engineering

The machine that builds our software

Redkale ships with a small team and a large number of agent sessions. A process that lives in habit is a process an agent cannot join — so ours is written down, argued from first principles, and published in full. Prompts included.

The machine

Four ways in, one spine out — the whole process on one diagram, reading upward from the four entry points to Done at the top. Every box opens: who acts there, what evidence gates it, what it leaves behind.

Open the diagram→
01

Foundations

2 pages

The argument the rest of the machine is derived from. Read these two and you can predict most of what follows; disagree with them and you should disagree with everything else.

Why this exists
Agent sessions start with no memory of yesterday. That single fact is why the process is a document and not a habit.
why-this-exists→
The six principles
Humans decide. The tracker is the record. Evidence gates every transition. No AFK without a definition of done. Sessions sized to the smart zone. Attention is expensive.
five-principles→
02

The factory running

3 pages

The diagram shows the process; these pages show it alive — what happens on a normal morning, what actually dispatches the work, and why neither of those things is the brain.

Triage and the morning report
Delegate a ticket and an agent drafts it out in full, routing on where the draft fails. The human wakes up to a read-only board report, not a pile.
morning-triage→
Symphony
The dispatcher. A three-sentence prompt that names the issue, the column and the lane skill — published verbatim, with what every part of it is doing.
symphony→
Actors and runners
Who acts at each stage — and why no product name appears in the answer. The unit of AFK work is the agent session, not the orchestrator.
actors-and-runners→
03

Reference

3 pages

The parts most teams keep private: the board's exact semantics, the skill tree that runs each stage, and the conventions that keep a tracker full of agents legible to humans.

The board
State transitions are the process, so every column means something exact — and every parked column is a claim about what a ticket waits for, never what anyone is doing to it.
the-board→
The skill tree
Twenty skills, admitted by reference and placed by variance. Derived from the process, not accumulated — and cut from twenty-eight to prove it.
skill-tree→
Evidence and dossiers
Agents write to the tracker like colleagues, not like log files: a one-breath note on the ticket, the long story in the effort's artefact, proof gating every transition.
evidence-and-dossiers→