packer base structure
This commit is contained in:
@@ -0,0 +1,47 @@
|
||||
# Packer Agendas
|
||||
|
||||
This directory contains active packer discussion agendas.
|
||||
|
||||
## Purpose
|
||||
|
||||
An agenda exists to drive a decision.
|
||||
|
||||
Use an agenda when:
|
||||
|
||||
- the packer topic is still open,
|
||||
- multiple options or tradeoffs must be evaluated,
|
||||
- scope and non-goals need to be made explicit,
|
||||
- the order of discussion matters,
|
||||
- the team still needs a recommendation before committing direction.
|
||||
|
||||
An agenda should help the reader converge, not just accumulate notes.
|
||||
|
||||
## Expected Format
|
||||
|
||||
A packer agenda should usually include:
|
||||
|
||||
1. Title
|
||||
2. Status
|
||||
3. Purpose
|
||||
4. Context
|
||||
5. Options
|
||||
6. Tradeoffs
|
||||
7. Recommendation
|
||||
8. Open Questions
|
||||
9. Expected Follow-up
|
||||
|
||||
## Writing Rules
|
||||
|
||||
- Keep the document centered on unresolved questions.
|
||||
- State the concrete decision the discussion is trying to produce.
|
||||
- Prefer explicit tradeoffs over vague option lists.
|
||||
- Avoid drafting large blocks of final normative spec text here.
|
||||
- Be specific about packer scope: asset workspace, build artifacts, diagnostics, registry, builder boundary, and related contracts.
|
||||
|
||||
## Exit Rule
|
||||
|
||||
An agenda should leave the active set when:
|
||||
|
||||
- the main tradeoffs are understood,
|
||||
- a recommendation is clear enough to adopt,
|
||||
- and the topic is ready to become a decision record.
|
||||
Reference in New Issue
Block a user