56 lines
1.5 KiB
Markdown
56 lines
1.5 KiB
Markdown
# PBS Agendas
|
|
|
|
This directory contains active PBS discussion agendas.
|
|
|
|
Closed agendas are moved to `docs/pbs/agendas/archive`.
|
|
|
|
## Active Agendas
|
|
|
|
1. `18.0. Backend VM Pipeline - Orchestration Agenda.md`
|
|
2. `18.1. Backend Workshop 1 - IRBackend Input Contract.md`
|
|
3. `18.2. Backend Workshop 2 - LowerToVM and IRVM Contract.md`
|
|
4. `18.3. Backend Workshop 3 - Bytecode Marshaling and Runtime Conformance.md`
|
|
|
|
## Purpose
|
|
|
|
An agenda exists to drive a decision, not to serve as final normative text.
|
|
|
|
Use an agenda when:
|
|
|
|
- the topic is still open,
|
|
- multiple options or tradeoffs must be evaluated,
|
|
- the scope and non-goals need to be made explicit,
|
|
- the order of discussion matters.
|
|
|
|
Move an agenda to `docs/pbs/agendas/archive` once the topic is no longer active.
|
|
|
|
## Expected Format
|
|
|
|
An agenda should usually include:
|
|
|
|
1. Title
|
|
2. Status
|
|
3. Purpose
|
|
4. Context
|
|
5. Decisions to Produce
|
|
6. Core Questions
|
|
7. Expected Spec Material
|
|
8. Non-Goals
|
|
9. Inputs
|
|
|
|
## Writing Rules
|
|
|
|
- Keep the document oriented around unresolved questions.
|
|
- Separate open questions from assumptions already fixed elsewhere.
|
|
- Name the concrete decisions the discussion must produce.
|
|
- Avoid drafting large blocks of final normative spec text here.
|
|
- Prefer explicit non-goals to prevent scope drift.
|
|
|
|
## Exit Rule
|
|
|
|
An agenda should move out of the active set when:
|
|
|
|
- the key questions have been answered,
|
|
- the architectural direction is clear enough to record,
|
|
- and the topic is ready to become a decision record and then a spec update.
|