The Cleanup Plan

Every take gets its own plan: the steps Post will take on it, in the order it will attempt them, and what each step is waiting on. The plan is built from that take's diagnosis and the options you set, so two takes never get the same one.

It is the same list at three moments — a forecast before the run, lit up during it, and a record afterwards. It fills in; it is never replaced by a second, different list.

Before the run

Open Run, choose Assisted, and tick a take. The third column, headed Cleanup Plan, says:

What we will do to this take, in order. Derived from its diagnosis, so every take is different.

Each row is one kind of work — "Fill small gaps", "Cut impulsive jitter" — with:

• how much of it there is, in the noun that work is counted in: 62 gaps on 18 markers, 8 joins, 4 checks. Where the number of steps differs from the number of gaps, the row names both: 6 gaps in 4 steps on LT10.
• what it sets out to close: 2 regions · 34 frames.
• why it runs here, written by the cleaner in plain words.
• after: Fill small gaps — the steps that have to be attempted first. Rows are indented and connected, so what waits on what is visible without reading.

Some rows say counted as it runs instead of a forecast. That is the plan being straight with you: those steps count their own work as they do it and cannot know the number in advance.

Changing a file or an option re-asks for the plan; Updating the plan… appears in the column header while that happens. A plan can also be unavailable, and the column says which case it is — for example Diagnose first to see the plan, This take will be re-diagnosed first, Nothing to plan, The plan is taking longer than usual, or The planner could not be reached. You can still launch the run: the launch does not wait for the preview.

During the run

The column keeps the plan the run was launched with and lights it up as work finishes:

Waiting its turn — the plan lights up as steps finish.

Cleaning… the plan lights up as steps finish.

After the run

The same column — and the Cleanup Plan block on the After screen — now reads:

What the run did to this take, step by step.

Every row gains what it actually did (1 of 2 regions · 9 of 13 frames) and a state badge. A folded row rolls its steps up in one line: 58 done · 4 not needed.

Above the rows, one line counts what the run left behind — and only one, so you never have to reconcile two tallies:

• 4 frames ship open · 1 step waiting for another run
• Finished inside its 3 iterations — nothing left waiting
• Nothing needed — no step had work to do
• Another run would improve this take
• plan ran — open frames not recorded — nothing counted the open frames, so no number is stated.

Underneath it, what to do about it: Run again to try it — Smooth joins goes first, or Another run would not change this — hand these frames to an artist when a second run would schedule the same work and decline it the same way.

Each performer's row carries a one-word verdict: Complete, Nothing needed, Nothing open, Still waiting, Did not land, or No result yet.

Step states

Four words for how a planned step ended. None of them is an error.

Badge	What it means
Done	The step ran and put something in the delivered file. Less than it forecast is a normal result — and a Done step can still leave frames open, with the count beside it.
Not needed	There was nothing to do: an earlier step had already closed the region, the option that would have run it was off, or the step looked at its windows and handed every one of them back with nothing left open.
Still waiting	Its prerequisites were still not met when the last pass ended, so it ships undone. This is the state that says another run would buy you something — and a re-run attempts it first.
Did not land	Post attempted it and shipped nothing. What it stood for is in the delivered file as holes, for an artist to finish.

Two more words show up in a folded row's rollup:

• left open — units a step stood for and did not close. They are counted separately so Done never claims work that is not in the file.
• Reported — a state this build of the app does not recognise. The counts are kept and nothing is claimed about them.

"Did it land?" and "is anything still open?" are two different questions. The badge answers the first; the count beside it answers the second.

The steps

Eight kinds of work. The plan uses only the ones a take needs.

Step	What it does	Counted in
Fill small gaps	Closes a gap from its own two anchors. Needs nothing else to be true first, so it usually goes early.	gaps
Fill medium gaps	Closes a longer gap using the trajectory around it.	gaps
Fill long gaps	Solves against the neighbouring markers, so it is planned after the neighbours it reads are clean.	gaps
Cut impulsive jitter	Cuts an impulsive acceleration peak out — peak plus a small pad — and refills the hole, the way you would replace a spike rather than average it into its neighbours. Only planned when the cut option is on.	cuts
Fix swapped markers	Resolves a swap or a merge across both markers of the pair.	swaps
Smooth jitter	Smooths jitter that was not cut.	jitter windows
Smooth joins	Conditions the boundaries between what the run wrote and what it did not.	joins
Check our own fills	Re-measures the result and decides whether another pass is worth running.	checks

The order is not a fixed recipe. It is worked out per take from what the diagnosis found and what each step needs to be true first, then grouped into passes — everything in pass 2 may assume pass 1 was attempted. The after: line on a row names what it waits on.

Why the jitter cut comes after the fills

A cut takes frames out and has to rejoin the trajectory on both sides. Next to a hole there is nothing to rejoin to, so the cut is planned after the fills of its own pass, once the surrounding data exists.

That is also why there are two cut passes. The first reads the take as captured; the second reads the bytes the fills produced, because filling a gap can expose a peak that was not visible before. A region card on After says which one a cut came from: Pass 1 — before the gap fill or Pass 2 — over the filled result.

What the plan does not do

• It is not a quote. The forecast on a step is what it sets out to close, not a promise.
• It does not say what the delivered file still has open. That is a separate, measured number — see the line above the rows, and Holes left open.
• It is not shown in Auto mode. Auto cleans every scheduled take with the standard fix order and no per-take column.
• A Clean made before plans existed has none, and the column says so rather than pretending the run did nothing.

What to do next

Read a plan that came back with Still waiting steps and run the take again — those steps go first. Read one that came back Did not land with frames open and hand those frames to an artist; another run will decline them the same way.

Ask us

Something looks wrong on a take? Write to support@kapnetix.ai and send the take id, or the take's name and the project it sits in.