Meeting lifecycle

The live lifecycle is implemented in the CLI and terminal, with deterministic installed tests. Plan 02 still awaits its real-account qualification campaign. The recorded example illustrates the same shape without calling a model.

The phases

1. Framing. A question and its context are enough; an existing plan is optional. The Product Owner proposes a framing, and work waits for your approval of that exact version.
2. Independent analysis. Advisers receive the same factual baseline without seeing each other’s first conclusions.
3. Confrontation. Objections target a specific claim or part of the proposal, say why it matters, and suggest a correction or a way to resolve the uncertainty.
4. Revision. The Product Owner publishes a new proposal version. Earlier views stay attached to the version they judged.
5. Final views. Each adviser states a verdict on the same immutable version. You then accept, reject, modify, defer or ask for more investigation.

In the recorded example

Proposal v1 plans five integrations in four weeks. The Lead Developer cites context.md line 4 — two engineers — and the Marketing Manager cites line 6. Proposal v2 narrows to one integration and five design partners. Two advisers approve; the Marketing Manager keeps INSUFFICIENT_EVIDENCE. The human decision stays pending.

Read it yourself in the recorded example guide.

For the implemented commands and qualification limits, see your first real meeting. Contributions during running phases, pause/resume and scoped context revisions belong to Plan 03.