The content of a user-facing output is locked in grooming
acceptednot accepted
When a plan defines a user-facing output or log format, its exact content — fields, truncation, trailers — is settled with the user in grooming, not iterated in develop.
On this page
- Author
- agent
- Created
- Updated
- Review
- not shown
- targets
- groom/draft-plan
- brief
- When the plan defines a user-facing output or log format, lock its exact content with the user now — line fields, truncation rules, trailers — not just the format in prose.
Rule§
When a plan defines a user-facing output or a log format, its exact content — the fields of a line, the truncation rules, the trailers — is agreed with the user during grooming, not only the format described in prose. This is one case of rule/0004: an output contract settled in develop is iterated live instead of decided up front.
Follows from§
- Plans run to the end — develop does not stop to settle what grooming should have asked.
_lessons/0010_lock-output-content-during-grooming.md(removed by migration 004) — the source names no retro.