55 lines
1.6 KiB
Markdown
55 lines
1.6 KiB
Markdown
# Packer Agendas
|
|
|
|
This directory contains active packer discussion agendas.
|
|
|
|
## Active Agendas
|
|
|
|
1. [`Tilemap and Metatile Runtime Binary Layout Agenda.md`](./Tilemap%20and%20Metatile%20Runtime%20Binary%20Layout%20Agenda.md)
|
|
2. [`Variable Tile Bank Palette Serialization Agenda.md`](./Variable%20Tile%20Bank%20Palette%20Serialization%20Agenda.md)
|
|
|
|
Closed packer agenda waves must be absorbed into [`../specs/`](../specs/) and [`../learn/`](../learn/) instead of remaining here as historical residue.
|
|
|
|
## 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, shipper 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.
|