andon-looplisted

# Andon Loop A value stream is the ordered chain of stages a project's work passes through (for example: ingest -> transform -> validate -> publish). A wire is the data contract at the boundary between two adjacent stages: what one stage promises to hand the next. The andon rule: never advance past a wire that has not been proven to hold. If the current stage's outgoing wire is broken or unverified, stop there and report it instead of moving on. A pass is one traversal of the value stream from its first stage to wherever the andon rule stops it (or to the end, if nothing stops it). A cycle is a converged run of one or more passes: it ends when a full pass finds no more gaps to fix. ## Running one pass 1. **Find the value stream.** Identify the project's stages and the wire between each adjacent pair. Look for existing documentation of this (architecture docs, a pipeline config, a stage list) before inferring it from the code's own module/package boundaries. 2. **Scan the current stage for gaps.** A gap is anything about the current stage or its outgoing wire that falls short of what the next stage requires: a missing field, an unhandled case, absent error handling, a contract violation. List every gap you find in this stage before picking one. 3. **Fix exactly one gap.** Pick the highest-priority gap in the current stage and fix it. Do not fix multiple gaps in the same stage before the wire is re-checked — one fix, then verify. 4. **Verify t