Skip to content
C.W.K.
Stream
Lesson 03 of 05 · published

Four Pipelines, Four Promises

~13 min · pipelines, contracts, curation, quotes

Level 0Trace
0 XP0/36 lessons0/12 achievements
0/100 XP to next level100 XP to go0% complete

Curate owns disposition

Curate runs survey, plan-gate, apply, and index-sweep. It reads living documents and candidates, then decides keep, correct, merge, or retier with Dad. Refine is not separate because reading dominates cost and verdict plus correction belong to one reading.

Merges can move quote blocks, so sanctuary judgment lives in the plan gate rather than a per-file byte gate. Never-delete remains structural at land through move pairing.

Ko-rewrite distinguishes voice from record

Diagnosis, plan-gate, ledger, rewrite, and reconcile rebuild living Korean from Korean thought. Dated moment records and library are not default rewrite targets because awkwardness may be authentic residue.

Dad's blockquotes remain byte-identical, and a ledger pins facts, names, and links before prose moves. A default brain is a hint, never an eligibility gate.

Optimize targets the boot bill

Weigh, plan-gate, ledger, apply, and reconcile improve token economy of the active boot set. Shortness is not the goal; facts, decisions, quotes, and links are pinned before prose moves, under a structural quality floor.

Shrinking a library may not change prompt cost, so default scope is the actual boot set. Token delta is evidence while Dad owns the quality verdict.

Reconcile-radar reads candidates only

Scan, plan-gate, apply, and index-sweep operate on the current Radar and Drift candidate set. A full-vault read belongs to curate, and similarity is a reason to read rather than a merge verdict.

All four share queue, claim, seal, and land. Templates, required stages, default scope, and quote policy vary as registry data instead of engine forks.

A pipeline is not a named prompt; it is a promise of inputs, prohibitions, stages, and landing gates. Keep lifecycle in one engine and promote repeated craft into registry data only at reuse.

Code

Declare pipelines as data·python
pipelines = {
    "curate": ["survey", "plan-gate", "apply", "index-sweep"],
    "ko-rewrite": ["diag", "plan-gate", "ledger", "rewrite", "reconcile"],
    "optimize": ["weigh", "plan-gate", "ledger", "apply", "reconcile"],
    "reconcile-radar": ["scan", "plan-gate", "apply", "index-sweep"],
}
assert all("plan-gate" in stages for stages in pipelines.values())
assert len(pipelines) == 4

External links

Exercise

Find a long-task craft used at least twice and split common lifecycle from pipeline-specific stages. Leave one-off craft as a template instead of premature abstraction.
Hint
Before adding engine conditionals, try representing inputs, stages, and gates as a data row.

Progress

Progress is local-only — sign in to sync across devices.
Spotted a bug or have feedback on this page?Report an Issue

Comments 0

🔔 Reply notifications (sign in)
Sign inPlease sign in to comment.

No comments yet — be the first.