Carolverse builds and fixes its own software on an autonomous build pipeline — a team of agents that design, build, test, and ship changes without a human driving each step. Like any machine that runs on its own, the useful question is not how it is wired but what it is doing right now, and whether that is healthy. This page explains how to read it.

Two questions, not one

Watching an autonomous system, you are really asking two separate things:

• Is it making progress? — its status.
• What kind of work is it doing? — its mode.

These are different, and confusing them is the most common way the pipeline gets misread. A car dashboard keeps them apart the same way: one light tells you the engine is running, another tells you whether you are in drive or reverse.

What the status tells you

At any moment the pipeline is in one plain state: it is moving, it is deliberately paused, it is switched off, it is stuck, or it has rightfully stopped. The last two matter most, because they look alike and mean opposite things:

• Stuck — the pipeline should be working, but nothing is happening. Something is wrong and

needs looking into.

• Rightfully stopped — the pipeline has done everything it can on its own and is deliberately

waiting for a human. Nothing is wrong; it is asking for a hand.

A system that cannot tell these two apart either cries wolf or quietly hides real trouble. Telling them apart is the whole point of a status.

Building versus healing

While it runs, the pipeline is doing one of two kinds of work:

• Building — carrying the next piece of work forward: design, build, test, ship.
• Healing — when something breaks, the pipeline stops taking on new work and turns to

repairing itself: it works out what went wrong and sets the failed work up to run cleanly the next time.

The switch is automatic. A safety catch trips the moment a piece of work gets blocked, and the pipeline flips from building to healing. This is the idea worth remembering: a tripped safety catch is not a breakdown — it is self-repair. The pipeline that looks stopped is often the pipeline fixing itself.

One thing at a time

The pipeline deliberately works on a single job at a time. One lane keeps it legible — there is always one thing to watch and one thing to reason about, instead of a scramble of half-finished work competing for attention. It is slower, and far easier to trust and to debug.

Where to look

The live picture is the pipeline card on the Build Initiatives Monitor tab: it shows whether the pipeline is moving, what kind of work it is doing, and lets the operator start, pause, or stop it. This page is the why; that card is the what is happening now.

What this page leaves out

The exact thresholds, limits, and switch settings — how many blocks it takes to trip the safety catch, how large the budget is, which model does the thinking — are deliberately not here. Those are configuration, and configuration changes. The ideas above do not.