Coldstart has not been released. The classifier on this page is a design discipline used with the development build; it is not a command that classifies a change for you.
The export plan assumed the list query contained the right data. Inspection showed something else: display-formatted labels, shortened notes, and no stable customer ID. That contradiction is a divergence: new evidence no longer fits a load-bearing part of the active plan.
Coldstart's discipline is to classify that seam before changing the work, and to ask about human judgment before scope, because silently making the wrong product choice is more expensive than misplacing a technical task. The classifying is done by whoever is steering, reading the two questions below; nothing in the product detects a divergence for you.
The two questions
Does resolving this need human judgment?
yes -> CHECKPOINT
no -> Is it inside this work session?
yes -> ADAPT
no -> QUEUEThe first question covers meaning, risk, public behavior, and other choices only the person steering the project can make. The second separates a technical correction from valid adjacent work.
Asking the two questions does not guarantee the right answer. The coding agent can still miss the seam or describe it badly.
Checkpoint: pause the dependent work
Choosing screen-shaped rows or approved raw fields changes what the CSV means. It can also change authorization and performance. The session records the question and what depends on it, then leaves the answer to the person steering the product.
Independent work can continue. CSV escaping tests do not require the source decision, for example. Building the read route behind a guessed answer is not independent work.
Adapt: correct the route
Once raw approved fields are chosen, replacing the display-row route is a technical correction inside the export outcome. The session updates the plan, makes the change, and records it in the outcome.
“I found it while working” is not enough. A new feature, broader behavior, or different risk boundary must go through the two questions again.
Queue: keep later work reachable
Historical customer IDs need migration, but that is a separate data change. The current endpoint can serve records that already have stable IDs, so the migration gets an owning location in the queue instead of silently joining this session.
Queueing says the work is real and outside the current unit. It does not set priority, approve a solution, or promise automatic completion.
Replace the live plan
After the branch is settled, Coldstart keeps one current route:
- Rewrite the affected plan around the chosen path.
- Update the next action and reading list if they moved.
- Record the change in the session outcome.
- Store a load-bearing reason in its durable decision home.
Version control preserves the previous plan. Keeping both alternatives in the live file would make a fresh session choose between incompatible instructions.
The plan change does not authorize deletion. The rejected display-row adapter moves to the separate deadness and ownership test on safe subtraction.
Next
Follow the branch that protects valid work from disappearing: the open-work queue.