Changes

A change is the unit Compass exists to produce: something worth trying. Sometimes that's an AI build; just as often it's a simpler fix — a process tweak, a different tool, a step removed. It reads like "auto-classify inbound tickets by queue and urgency," not "use AI in support." The difference is that a change is anchored to real work, so it's something you can actually go test.

Grounded in the map

A change can attach to a Workflow page — down to a particular step — and link to any other pages it touches: the pain point it addresses, the systems it uses, the value or priority it serves, the people it involves. That grounding is the whole point: an idea floating in a backlog doc ages out and loses its context, while a change tied to the map carries everything around it. When you go to run it, the brief is already there.

You don't have to spot every one yourself. On any Workflow page, Suggest changes reads the workflow — its body plus the connected people, systems, and pain points — and proposes some. They arrive marked proposed and wait in the Inbox under Proposed changes until you accept or dismiss them; nothing zv1 suggests becomes real without your say.

The board

The Changes tab is a board. Drag a card to move it between statuses. Every workspace starts with these:

• New — surfaced, undecided.
• Looking into it — someone is working out whether it's worth doing.
• Later — yes eventually; not now.
• Underway — you're doing it.
• Settled — it concluded, and the outcome is on the record.
• Dropped — set aside without trying it. Kept, not deleted: where you chose not to act is a result too.

The statuses are yours to change. Open Statuses and settings from the ⋯ menu above the board to rename one, add your own ("In review", "Waiting on the client"), reorder them, or retire one you don't use. Each status sits in a group — Undecided, Not started, In progress, Done, Dropped — so the counts above the board and zv1's answers keep working whatever you call things. When you retire a status, you choose where its changes go.

A table view sits behind a toggle for sorting and filtering.

Scores are something you add later

A new change is a label, a description, and the workflow it belongs to. The three 1–5 scores — Value, Feasibility, Risk — start empty, and each one can carry a sentence saying why you landed on that number, which is the part that's worth reading six weeks later.

Once a change moves past Looking into it without any score, its card says Unscored. That's a nudge, not a gate — you can leave it that way.

Say what you expect — before the evidence

Some changes are experiments: you want to know whether they worked. Turn on Measure as an experiment when you create the change, or later on its page. Fixes and chores can leave it off and move across the board without any of what follows.

Moving an experiment into an in-progress status asks one question: what do you expect this to change? That sentence is written down before the evidence exists, as an entry in Ledger — the workspace's decision memory. You can skip it, but the skip shows: an experiment that never registered an expectation wears Unregistered when it concludes.

When it ends, you settle the entry: did the expectation hold? The card carries the answer from then on — Confirmed or Missed — and the lesson lives in Ledger. Moving the card to a done status doesn't claim success on its own; the verdict comes from the settlement.

Over time this makes the board something a backlog never is: a record of what was tried, what was expected, and what actually happened.

From change to built

When it calls for an AI build, Draft in Workbench — right on the change — generates a runnable first-draft flow in Workbench to start from, which you then prove out in Caliper. What that measurement exposes points back at the next change. The map keeps turning.