Purpose: This guide extends the P3 Beginners Guide for practitioners who are managing — or planning — a Programme: multiple coordinated delivery streams operating under a shared strategic configuration. The Beginners Guide covers the six pillars (Principles, Patterns, Products, Strategy, Governance, Maturity). This guide introduces the portfolio-layer instruments those pillars require at Programme scope: Strategy Dossier, Charter, Saga, Strategic Bundle, and Dossier Closure.

Who this is for: Practitioners who have read the P3 Beginners Guide and are now asking: "Where does the Programme live in P3? What artefact holds it together? How do I set one up and close it down?"

The word "programme" carries four structurally distinct meanings in P3 discourse. Conflating them is the primary source of early-adopter confusion.

Sense 1 — The Operational Instance (the manuscript sense)
A unit of production — a team, a programme, a project — authorised to produce within the Production Sphere. The manuscript is explicit: "A Factory is any unit of production — a team, a programme, a project — that has been authorised to produce." Each delivery stream within a Programme-as-portfolio is a Factory in this sense. This sense is about executional authority: a bounded unit with a Charter and a mandate.

Sense 2 — The Transformation Programme (the discredited sense)
A multi-year initiative with a prescribed end-state — the conventional methodology P3 explicitly replaces. The manuscript: "not a new plan, not a reorganisation, not a transformation programme. A remix." Named here to prevent confusion; it is what P3 does not do.

Sense 3 — The SAFe Coordination Boundary
The Agile Release Train or equivalent from the Scaled Agile Framework. Referenced in the manuscript as an external methodology artefact; not a P3 construct.

Sense 4 — The Strategic Composition (this document's subject)
The set of P3 artefacts — Strategy Dossier, Principle Dossiers, Pattern Dossiers, Factory Charters, Products, Sagas — that share a common strategic origin and cohere as a named sub-portfolio. This is the sense early adopters mean when they ask "where does our Programme live?" The rest of this document addresses Sense 4.

The instinctive response — "a Programme is a Product that holds other Products" — is structurally incorrect in P3.

The P3 value chain terminates at Product: "Principles constrain. Patterns guide. Products ship." There is no fourth term. A Programme is not a value-bearing Product; it cannot be certified as Done by the Product Sentinel; it does not transfer value to a beneficiary in the way a Product does. Creating a meta-Product to hold the Programme corrupts the constitutive rule that defines what a Product is.

The correct P3 answer: a Programme is a Strategic Bundle — a bounded sub-corridor of the portfolio's Governed Random Walk, defined by a single Strategy Dossier and derived by querying all artefacts that reference that Dossier's identifier. The Programme name ("Project Aurora", "Platform Modernisation") is the human-readable label for the Strategy Dossier. The Programme itself is computed on demand — a view over the portfolio, not a stored container.

Two implications follow immediately:

Five instruments are required at Programme scope that the Beginners Guide does not introduce.

Strategy Dossier
The legislative instrument encoding a strategic configuration for one epoch: the Desired Slope (targeted direction and rate of capability improvement), the mixing-desk fader positions (which Principles are foregrounded), and the Maturity Epoch under which production operates. Its unique identifier (e.g., SD-2026-003) is the binding key for every artefact in the Programme. Emitted by the Strategy Sentinel. It is a constraint instrument, not a plan — it sets fader positions, not destinations. It is in force for one epoch, then decommissioned.

Charter (Factory Charter)
Bounded authority granted to one delivery team to produce within the Programme's corridor. Each Charter cites the Strategy Dossier ID, making the team's output attributable to the Programme. One Charter per Factory.

Saga
The append-only record of what a Factory actually did during its Charter — the operational truth of the Programme as it unfolded. Sagas are the upstream signal informing the Strategy Sentinel whether the direction is working. One Saga per Factory.

Strategic Bundle
The structural form of the Programme: the complete set of artefacts (Charters, Products, Sagas, sub-Dossiers) that share a Strategy Dossier as their binding key. Bounded by Principle Dossiers (corridor walls) and scoped by the Maturity Epoch (corridor width). Not stored — derivable on demand.

Dossier Closure
The query mechanism that materialises a Strategic Bundle. It traverses the Traceability Spine — the connective structure linking the Legislative Sphere to the Production Sphere — and collects all artefacts referencing a given Dossier ID. Applied to a Strategy Dossier, the result is the complete Portfolio Integration Map entry for the Programme: which Charters, Products, and Sagas belong to it, and how they cohere architecturally.

No new artefact category is introduced. A Programme decomposes into the following existing P3 artefacts:

The Strategy Sentinel issues the Strategy Dossier. This is the single most consequential act — the Dossier's unique identifier becomes the spine of the entire Programme. Factory Charters are derived; teams receive bounded authority; the Traceability Spine is activated. Write the Strategy Dossier before any Charter is issued or any Product brief is written. An organisation that begins delivering Products without a Dossier has no Programme — it has a set of unanchored deliverables with no queryable boundary.

Steady-state production within the Dossier's corridor. Factories produce Products; Sagas accumulate the operational record. The Dossier Closure is live and queryable throughout: "what artefacts are part of this Programme?" is answered by querying for all artefacts carrying the Dossier ID. Sagas inform the Strategy Sentinel continuously — is the direction working, or does the epoch require a remix?

The Strategy Dossier is decommissioned. Factory Charters are released. In-flight Sagas are resolved: completed, frozen, or transferred to a successor Dossier. Products and completed Sagas are absorbed into the portfolio's institutional memory. Plan the Conclusion phase at Initiation. Before the Dossier is issued, the team should already know: when does this epoch end, and what happens to each artefact type? The Conclusion phase is the most commonly under-planned and most frequently mishandled part of Programme governance.

The Programme-as-Product error
Creating a "Programme product brief" or meta-Product to hold the Programme together. A Programme cannot be certified by the Product Sentinel and does not transfer value to a beneficiary in the Product sense. The correct binding instrument is the Strategy Dossier, not a Product brief.

The Programme-as-container error
Creating a stored "Programme document" or "Programme folder" to hold all constituent artefacts. Any stored container will immediately begin to diverge from the actual derived closure — it must be manually updated with every Charter or Product addition. The Programme is a query, not a container. Trust the binding-key discipline and the Dossier Closure mechanism.

Orphaned artefacts at Conclusion
Failing to formally close Charters and resolve Sagas when the Dossier is decommissioned. These artefacts exist in the portfolio but cannot be traced to active strategic intent — they are ungoverned and untraceable. At Conclusion, the Strategy Sentinel must explicitly decide the fate of every artefact in the closure before decommissioning.

This guide is a companion to the P3 Beginners Guide and the six Minimum Viable filter guides. It does not replace them — it extends them for Programme scope. The Beginners Guide provides the six-pillar framework; this guide provides the portfolio-layer instruments required when multiple delivery streams must cohere under a shared strategic configuration.