Overview / Operating Discipline
Operating Discipline
How the philosophy becomes a way of working — not just a platform.
Purpose, governing questions, principles and the reflection cadence that keeps PD:OS honest as it grows.
Purpose
Improve the judgement of the Product Ecosystem.
This governs people, AI agents, products, partners and decisions. It's meant to become the cultural operating system — not a policy binder nobody opens.
North Star Question
"Will this improve the judgement of the Product Ecosystem?"
Every capability, feature and agent behaviour is meant to answer this question honestly — including when the honest answer is no.
Principles
Eight principles that govern behaviour, not just intent.
01
Every Product Learning Cycle should improve ecosystem judgement.
02
Every generation should begin further ahead than the previous one.
03
Compounded learning should strengthen the ecosystem without compromising proprietary product IP.
04
Evidence before intelligence; explanation before advice; recommendation never command.
05
Confidence must reflect evidence; assumptions and uncertainty must be visible.
06
Learning is only valuable if it has permission to change future decisions.
07
Reflection is part of product development: knowing what we know now, would we still decide the same way?
08
PD:OS must embody the philosophy it asks others to adopt.
Rules AI agents operate under
What "recommend, never command" actually means in practice.
- Never present fiction with confidence.
- Observation before interpretation; interpretation before recommendation.
- Respect product IP and confidential project evidence — steward judgement, never appropriate proprietary designs.
- Every capability must fulfil a Discovery; every feature must strengthen a Capability.
Governance
Three living artefacts, kept honest by reflection.
ARTEFACT 1
Discovery : Reflection
Defines the executive point of view — the six discoveries and their reflection questions.
ARTEFACT 2
The Constitution
Defines how PD:OS thinks and behaves — purpose, principles, beliefs and rules.
ARTEFACT 3
Capability Architecture
Defines how the philosophy becomes operational — the capability map and traceability model.