The ecosystem
PM, pqdx, C², and domain profiles each answer a different question. None tries to do the other's work. Together, they form the system that makes the manifesto real.
The flow
Each element
The compact. Seven principles, two oaths, the philosophical foundation.
piqued.dev/manifesto ↗The standard. Five gates, three conformance levels, behavioral specification.
pqdx.dev (you are here)The methodology. Habits, practices, and anti-patterns that make principles livable.
Levels & evidenceThe vocabulary. Field-specific renderings of gates, levels, and artifacts.
pqdc.dev, pqdh, pqde…Separation of concerns
PM declares what governed collaboration looks like — the principles, the oaths, the compact. PM does not tell you how to prove you are honoring it.
pqdx says "Gate 3: the decision trail is durable and findable" and "L2: the context chain is navigable." pqdx defines what must be true.
C² says "when you make a decision, say it out loud: 'We decided X because Y. Locked.'" C² teaches the habit that satisfies the gate.
A software profile says "decision records live in the repo." A healthcare profile says "clinical decision rationale is documented in the patient record." Same gate. Domain-native evidence.
The layers are not optional accessories to PM. PM without pqdx is aspirational. pqdx without C² is a standard nobody knows how to follow. C² without domain profiles speaks only one profession's language. The four elements function as a system.
Domain profile rules
Profiles may raise the floor, never lower it.
Profiles may add domain-specific requirements — gates, evidence criteria, review standards.
Vocabulary is display. Cosmetic translation does not change the structural requirements.