Packer Agendas
This directory contains active packer discussion agendas.
Active Agendas
01.0. Packer Scope, Boundaries, and Golden Pipeline Agenda.md01.1. Asset Workspace, Registry, and Stable Identity Agenda.md01.2. Asset Specification, Raw Assets, and Virtual Asset Contract Agenda.md01.3. Build Artifacts and Deterministic Packing Agenda.md01.4. Diagnostics, Doctor, Quarantine, and Workspace Hygiene Agenda.md01.5. Incremental Build, Cache, and Watch Model Agenda.md01.6. CLI Surface and Mutating Operations Agenda.md01.7. Builder Integration, Versioning, and Trust Model Agenda.md
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:
- Title
- Status
- Purpose
- Context
- Options
- Tradeoffs
- Recommendation
- Open Questions
- 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.