lightweight-lanelisted

# Lightweight Lane (FR-21) ## Purpose Make ceremony proportional to risk. Fusebase Flow's full eight-phase lane is calibrated for *uncertain / risky* work, where spec / clarify / decisions / gate genuinely de-risk. For a change that is small, reversible, security-neutral, and has a one-sentence verifiable outcome, that uncertainty is near zero — so the planning + traceability artifacts add cost without reducing risk, and the two-agent deploy split can even *add* risk (redundant rebuild, more surface for mistakes than the change carries). This skill is the single source of truth for the **Lightweight Lane (LL)**: the eligibility gate, the change-note, the one-pass procedure, and mid-flight promotion. Everything that actually controls risk is **kept in both lanes**. This is **not** only for one-line edits. It covers the whole class of **small / minor changes that need no large implementation and no real architectural decisions** — small hotfixes, small bug fixes, small improvements, config/copy tweaks. The discriminator is *implementation size + risk*, not a hard file count. > The change-note is **Tier 1** in the FR-23 documentation budget (`flow-skills/documentation-budget/SKILL.md`): FR-21 scales *process* ceremony; FR-23 scales *persistent documentation*. A Lightweight ticket's documentation IS the change-note — do not also emit spec/decisions/tasks/handoff docs for it. ## When to classify (every ticket, at Specify) Classify **Full** or **Lightweight** when the ticket