Purpose: This document is the orientation guide to the P3 framework. It is designed to be loaded into your AI system alongside the six Minimum Viable filter guides. Where each filter guide provides operational detail for one pillar, this guide provides the structural map: what P3 is, how its six pillars relate to one another, and how to use the six guides together as a coherent system.

P3 is a framework for making the invisible visible.

Every organisation generates three types of structured knowledge, whether it knows it or not:

In P3 terminology, these are: Principles, Patterns, and Products — the three P's that give the framework its name.

Most organisations generate all three implicitly — through habits, decisions, and accumulated experience. The problem is that they are rarely made visible, categorised, or connected to one another. Principles blur into preferences. Patterns get confused with procedures. Products get conflated with features. When these categories are not distinguished, the organisation cannot reason clearly about what it is doing, why, or whether it is working.

P3 addresses this by pairing the three P's with a second triplet — Strategy, Governance, and Maturity (the SGM) — that determines how well an organisation can sustain and direct its P3 knowledge. Strategy is the directional force that activates Principles and allocates resources between Product opportunities. Governance is the integrity function that ensures the organisation remains true to its commitments. Maturity is the honest inventory of what the organisation can do reliably right now.

Together, the six pillars form a complete operating model. The P3 triplet describes what the organisation makes — its institutional knowledge architecture. The SGM triplet describes what enables the organisation to make it reliably, direct it intelligently, and sustain it over time.

The framework's central claim: most organisational dysfunction arises from conflating these six categories. An organisation that cannot distinguish its Principles from its Patterns, or its Strategy from its Governance, cannot reason clearly about what it is doing or why. These seven documents — this guide and the six filter guides — give you the vocabulary and the minimum structures to begin making that distinction.

The three P's define what is structurally true about the organisation's knowledge output. They flow downstream — from abstract constraint (Principle) through reusable form (Pattern) to concrete realised value (Product).

Principles are governing constraints — commitments that define what solutions are permissible and what they are not. A principle operates at the level of function: it says what must be true, not how to achieve it. Principles come in four types: Absolute (physics and logic you cannot negotiate), Regulatory (law and compliance you cannot ignore), Institutional (choices your organisation has made and could revisit), and Heuristic (accumulated wisdom that guides without mandating). At minimum viable maturity, a small, active, enforceable set is far more valuable than an inflated catalogue of aspirations.
See: P3 Filter Guide - Minimum Viable Principles

Patterns are the knowledge architecture — reusable, named responses to recurring classes of problem, encoding both the form of the solution and the reasoning behind it. Patterns translate Principle-level constraints into specific, repeatable capabilities. Critically, every pattern has an Expression Gradient (how the pattern manifests as the organisation's capability develops from Level 1 to Level 5) and a Plasticity Status (Proto, Emerging, or Canonical) that signals how much governance authority the pattern carries.
See: P3 Filter Guide - Minimum Viable Patterns

Products are the vehicles for value transfer — not artefacts, but the mechanisms through which specific capabilities move from the organisation to specific beneficiaries. Every product is a hypothesis made testable: shipping is the moment the claim becomes verifiable, not the moment it is concluded. Products come in three types — Theory (knowledge transfer), Instrument (capability transfer), and Service (outcome transfer) — each with its own success criteria and failure modes.
See: P3 Filter Guide - Minimum Viable Products

The SGM defines what is required of the organisation given its current environment, ambitions, and capacity. It operates in a cycle — market signals inform strategic adjustment, which feeds forward into governance and maturity investment, which shapes the next cycle.

Strategy is the directional force — the intentional slope that determines where the organisation is pointed and at what pace it is moving. Strategy is not a plan or a destination: it is a direction of travel calibrated to what the organisation can sustainably do. Strategy activates Principles (choosing which governing constraints to foreground in this epoch), calibrates Products (deciding which value transfers to pursue), and must be checked against the Maturity terrain before any commitment is made.
See: P3 Filter Guide - Minimum Viable Strategy

Governance is the integrity function — the mechanism that ensures the organisation does what it claims to do. Its central distinction is between Done (stakeholder acceptance of the work) and Valid (structural integrity of the work against the commitments that shaped it). At minimum viable maturity, governance requires three things for each critical commitment: a named commitment, a named sentinel with authority to act, and a friction point where work pauses for a check before proceeding.
See: P3 Filter Guide - Minimum Viable Governance

Maturity is the capability terrain — the honest, multi-dimensional inventory of what the organisation can reliably sustain right now. Maturity is not a single number; it is a surface with peaks and valleys across different practice domains. The Ratchet mechanism (Documentation → Tooling → Governance → Culture) converts capability gains into permanent features. The Strategy Sieve (Now / Grow / Recalibrate) uses the maturity terrain to calibrate strategic ambition to what the organisation can actually execute.
See: P3 Filter Guide - Minimum Viable Maturity

The six pillars are not independent silos. They are orthogonal forces that constrain, enable, and check one another. Understanding the key relationships is what converts six separate filter guides into a unified framework.

The framework's most important interactions occur at three defined intersections — points where one P3 pillar meets one SGM pillar in productive tension. Each intersection produces a synthesis that neither pillar could reach alone.

The Legislative Nexus — Principles ↔ Strategy

Principles define the boundary of what is permissible. Strategy decides which permissible directions to actually pursue. The tension is between stability (the Principle's demand for consistent constraint) and velocity (Strategy's demand for decisive movement). The synthesis is risk-adjusted compliance: Strategy does not override Principles — it weights and activates them, foregrounding those most relevant to the current strategic epoch without violating any. An organisation without this distinction is either paralysed (too many Principles with no strategic direction) or reckless (strategic velocity without principled constraint).

In practice: Always extract your Principles before formulating your Strategy. The Strategy brief's "Principle Activation" field (item 5 in the six-part template) is where this nexus is made explicit.

The Architectural Nexus — Patterns ↔ Maturity

Patterns describe ideal form — what good looks like in a given class of problem. Maturity describes current reality — what the organisation can actually sustain. The tension is between aspiration (the Pattern's ideal) and physics (the Maturity frontier). The synthesis is appropriate engineering: deploying the pattern expression that offers maximum fitness for the current capability level — neither over-engineering for a low-maturity organisation nor under-engineering for a high-maturity one.

In practice: The Expression Gradient in each pattern must be read against the Maturity profile. A Canonical pattern designed for Level 3 capability cannot be safely deployed by an organisation at Level 1, regardless of its authority. The Maturity terrain sets the ceiling for safe pattern selection.

The Value Nexus — Products ↔ Governance

Products define what is desired — the value transfer the beneficiary needs. Governance defines what is verifiable — whether that value transfer is structurally sound. The tension is between outcome (the Product's demand to ship) and integrity (Governance's demand to validate). The synthesis is Done vs. Valid: a product must satisfy both stakeholder-facing Done criteria and system-facing Valid criteria. Governance is not the enemy of product delivery — it is the mechanism that ensures delivery is what it claims to be.

In practice: The Product brief's "Validity Marker" field (item 6 in the six-part template) is where this nexus is operationalised. Can the product's key design choices be traced to a governing commitment? If not, the product is Done but not yet Valid.

Beyond the three nexus points, the framework operates through two circulation flows that keep the pillars connected over time.

The Downstream Current flows from Principle → Pattern → Product: the construction flow, driven by constraint. Principles bound the space of valid patterns. Patterns shape the structure of valid products. When this current is healthy, every product is traceable back to the commitments that governed its design. When it breaks, products drift away from governing commitments invisibly — the organisation builds things that satisfy no principle anyone can remember articulating.

The Upstream Current flows from Product feedback → Strategy → Principle: the correction flow, driven by learning. Market signals from delivered products inform strategic adjustment. Strategic adjustment, over time, may prompt revision of Institutional Principles. When this current is healthy, the organisation learns from what it ships. When it breaks, the organisation ships and discards what the shipping reveals — every deployment is an experiment that produces no learning.

The six filter guides can be loaded simultaneously or applied sequentially. For an early-stage organisation beginning to make these distinctions explicit for the first time, the following sequence minimises the risk of building on assumptions that earlier steps would have corrected.

Step 1 — Maturity first.
Before any other work, build an honest practice-level capability profile. Identify which domains are Ad-hoc (L1), Repeatable (L2), Standardised (L3), or Measured (L4). This prevents strategy, product, and governance work from being built on capabilities the organisation does not yet have. Use: P3 Filter Guide - Minimum Viable Maturity

Step 2 — Extract Principles.
Identify the governing constraints that bound your solution space. Separate what you cannot change (Absolute, Regulatory) from what you have chosen (Institutional, Heuristic). Principles must be established before strategy or product work begins — they define the space within which strategy and products must operate. Use: P3 Filter Guide - Minimum Viable Principles

Step 3 — Formulate Strategy.
With a capability inventory and governing constraints in hand, formulate your directional slope. Apply the Strategy Sieve to each major element: Now, Grow, or Recalibrate. Ensure the strategy activates your Principles (the six-part brief's "Principle Activation" field), acknowledges the Maturity reality (the "Capability Assessment" field), and names what it explicitly will not pursue (the "Sacrifice List"). Use: P3 Filter Guide - Minimum Viable Strategy

Step 4 — Design Products.
Translate the strategic direction into specific value transfers. For each product idea, apply the Transfer Test (what specifically moves to the beneficiary?), the Tripartite Classification (Theory, Instrument, or Service?), and the Validity Marker (can design choices be traced to a governing Principle?). Use: P3 Filter Guide - Minimum Viable Products

Step 5 — Surface Patterns.
As product design proceeds, scan materials for recurring problem-solution pairs. Apply the Repeatability, Drift, and Patternitis checks. Document validated patterns with the six-element brief and classify each by Plasticity Status. Check each pattern's Expression Gradient against your Maturity profile before applying it. Use: P3 Filter Guide - Minimum Viable Patterns

Step 6 — Build Governance.
Identify your three most critical commitments and apply the minimum governance structure to each. Calibrate governance intensity to maturity level. Apply Subsidiarity to everything below the top three: embed governance locally, at the team level, reserving central oversight for escalations and cross-boundary decisions. Use: P3 Filter Guide - Minimum Viable Governance

This is a bootstrap sequence, not a permanent operational order. Once all six pillars are active, they operate in parallel and constrain one another continuously.

A complete P3 implementation is not required to begin benefiting from the framework. The minimum viable footprint — the smallest configuration that provides meaningful structure — requires five elements:

This footprint is achievable in a single working session. It requires no existing P3 infrastructure. It requires only that the organisation is willing to answer honestly: What constrains us? Where are we going? What are we building? What can we actually do? And who is watching to make sure we do what we say?

Patterns are deliberately absent from this minimum footprint. Not because they are unimportant — they are central to the framework — but because genuine patterns emerge from repeated practice and should be documented once they have demonstrated fitness across multiple contexts. Forcing pattern documentation before the work has generated repeatable instances creates premature institutionalisation.

The Ratchet is on your side. Every distinction you make explicit is a permanent gain. Every category you clarify reduces interpretive noise in future decisions. The goal of this bootstrap toolkit is not to install a governance system overnight — it is to give the organisation the minimum vocabulary to stop conflating these six domains and start building deliberately, one tooth at a time.

Begin with what you can defend today. The framework will meet you where you are.

This guide is a companion reference to the six Minimum Viable filter guides. It does not replace them — it connects them. Each filter guide provides the operational detail for one pillar; this guide provides the architecture of their relationships and the sequence in which to apply them.