Packer Decisions
This directory contains packer decision records.
Purpose
A decision record is the bridge between packer discussion and packer execution.
Use this directory to capture:
- what was decided,
- why that direction was chosen,
- which constraints now apply,
- what remains intentionally undecided,
- which specs, plans, tests, or implementations must be updated.
A decision should be stable enough that a spec or implementation worker can act on it without reconstructing the original debate.
Expected Format
A packer decision should usually include:
- Title
- Status
- Date or Cycle
- Context
- Decision
- Invariants and Constraints
- Explicit Non-Decisions
- Propagation Targets
- Validation Notes or Examples
Writing Rules
- State the adopted decision early and clearly.
- Write in stable language, not in exploratory tone.
- Capture architectural constraints explicitly.
- Record what is still not decided so later work does not guess.
- Point to the exact packer specs, PRs, or code areas that need propagation.
Implementation Rule
If implementation work reveals a missing decision, do not infer it. Return the issue to agenda or decision review.