prometeu-studio/docs/compiler/pbs/agendas

PBS Agendas

This directory contains active PBS discussion agendas.

Closed agendas are moved to docs/compiler/pbs/agendas/archive.

Active Agendas

1. 18.4. Asset References in Game Code - Names vs Compile-Time Lowering Agenda.md
2. 18.5. Ignored Call Results in Executable Lowering Agenda.md
3. 19. Globals, Synthetic Module Init, and FRAME_RET Agenda.md
4. 19.1. PBS Globals Surface, Identity, and Module Boundaries Agenda.md
5. 19.2. PBS Lifecycle Markers, Program Init, and Frame Root Semantics Agenda.md
6. 19.3. Published Entrypoint, Synthetic Wrapper, and FRAME_RET Ownership Agenda.md
7. 19.4. Globals and Lifecycle Lowering to IRBackend-IRVM Agenda.md
8. 19.5. Diagnostics, Manifest Propagation, and Conformance Coverage Agenda.md

Consolidated Agenda 18 Material

Agenda 18 backend-orchestration material (18.0 through 18.3) is no longer part of the active agenda set.

That slice has already been propagated into:

1. the backend execution plan in docs/compiler/pbs/pull-requests/INDEX.md under Backend VM Pipeline PR Sequence (Agenda 18),
2. decision material such as docs/compiler/pbs/decisions/IRVM Optimization Stage Placement Decision.md,
3. normative backend specs:
   • docs/compiler/general/specs/19. Verification and Safety Checks Specification.md,
   • docs/compiler/general/specs/20. IRBackend to IRVM Lowering Specification.md,
   • docs/compiler/general/specs/21. IRVM Optimization Pipeline Specification.md,
   • docs/compiler/general/specs/22. Backend Spec-to-Test Conformance Matrix.md,
4. and implemented/tested backend pipeline stages in prometeu-compiler/prometeu-build-pipeline.

Only 18.4 and 18.5 remain open from the 18.* family.

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/compiler/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.