Version 1.0 (Master)
P0 is a rulebook for carrying out professional projects responsibly, from first idea to delivery. It applies whether the work is done alone, with human collaborators, with AI systems, or with a mix of them.
P0 governs how chosen work is done. It never decides which work is chosen: priorities, opportunities, and resource allocation stay with the user.
The authoritative protocol is P0_Version_1.0_Master.md.
This README is an introduction and quick-start guide. If it conflicts with the Master file, the Master file governs. Read the Master file before starting work under P0.
Earlier drafts (P0_Version_1.0.md and P0_Version_1.0_REFINED.md) are superseded. Keep them in version control for history, but do not use them as the working protocol.
- Clear authority. Every decision is classified before action: prohibited, emergency, user-reserved, material, or routine. Silence is never approval (§4).
- Defined roles. Responsibilities for the user, primary and secondary LLMs, main agent, sub-agents, security agent, and human reviewers, plus levels of review independence (§5).
- A shared lifecycle. Seven layers with gates, and a standard way to record gate outcomes (§6).
- Proportionate rigor. Exploratory, Standard, and High-assurance profiles chosen by risk, not project size (§7).
- A continuity record. One
P<project-number>.mdper project, so work can be resumed without relying on memory or chat history (§8). - Evidence discipline. Handoffs, evidence, disagreement handling, and a finding lifecycle (§9).
- Controlled change. Bounded exceptions and a formal amendment procedure (§11, §12).
P0 supports four equally legitimate missions. It does not rank them or require equal time for each.
| Pillar | Mission |
|---|---|
| P1 — Creation and Innovation | Build useful, meaningful projects and valuable improvements. |
| P2 — Vulnerability Discovery | Find credible flaws within authorized scope, support responsible disclosure, and seek appropriate recognition. |
| P3 — Theoretical Research and Invention | Develop original theories and mechanisms, supported by rigorous reasoning and evidence. |
| P4 — Applied Research and Intellectual Property | Turn new technologies into practice and assess suitable IP protection, including patents where appropriate. |
A project may serve more than one pillar. Its record names a primary pillar and any secondary ones.
flowchart LR
L1["1. Idea and planning"] --> L2["2. Architecture or methodology"]
L2 --> L3["3. Design, where applicable"]
L3 --> L4["4. Development and execution"]
L4 --> L5["5. Testing and adversarial evaluation"]
L5 --> L6["6. Production readiness"]
L6 --> L7["7. Release and delivery"]
L5 -.->|"Evidence sends work back"| L4
The lifecycle is iterative. Evidence can send work back to an earlier layer, and a project can be paused, redirected, or cancelled at any point. Layers may be combined or omitted as separate phases only if their responsibilities are still met. The full gate procedure and a complete flow diagram are in §6 of the Master file.
Every project MUST have a Markdown continuity record named:
P<project-number>.md
For example, project 12 uses P12.md. Project numbers are unique, are never reused, and are unrelated to the pillar labels P1–P4. The record's header states the pillar in words.
The record covers objective and scope, acceptance criteria, plan, decisions and approvals, progress, verification and findings, handoffs, and final outcome. Link to detailed artifacts rather than copying them. Do not store secrets in it.
A ready-to-use template is in §8.4 of the Master file.
For each new project:
- Read P0. Know the approval boundaries that apply to the work.
- Create the record. Assign a unique number and create
P<project-number>.mdfrom the §8.4 template. - Define the work. Record the objective, pillar(s), scope, constraints, success criteria, and major risks.
- Choose rigor. Pick Exploratory, Standard, or High-assurance based on impact, uncertainty, reversibility, and exposure (§7.2).
- Assign responsibility. Name the owner, executors, reviewers where needed, and who approves consequential decisions. State the independence level for key reviews.
- Set controls. List the technical or manual controls that apply to consequential work (§10.1).
- Work through the lifecycle. Classify material decisions before acting (§4.6), record gate outcomes (§6.1), and keep the record current.
- Verify before completion or release. Confirm criteria, reviews, approvals, and finding dispositions (§13). Never claim verification that was not performed.
- Close out. Record the actual outcome, remaining limitations, and handover details, or why the project was paused or cancelled.
- The user owns P0 and decides priorities, project selection, and resource allocation.
- Contributors may make routine, reversible decisions only within delegated scope.
- Reserved decisions need explicit user approval. Silence is not approval.
- A prohibited action cannot be approved into legitimacy. User approval does not override law, binding obligations, third-party rights, or authorization limits.
- P0 grants no permission to access, test, modify, or disclose anything. Work must stay within actual authorization.
- Mandatory rules cannot be silently waived. Exceptions exist only for the rules listed in §11.2, with user approval, compensating controls, and an expiry or review condition.
- Claims of completion, correctness, security, originality, or success require evidence proportionate to the claim.
Roles are functions, not necessarily separate people or systems. One contributor may fill several roles, but independent review must be genuine where required.
| Role | Function |
|---|---|
| User | Owner and final decision-maker |
| Primary LLM | Strategist and coordinator |
| Secondary LLM | Independent critic |
| Main agent | Primary executor |
| Sub-agents | Temporary specialists |
| Security agent | Authorized adversarial evaluator |
| Human team | Reviewers and advisers |
Only the user, or someone explicitly assigned that authority, can grant required approvals. The role table and collaboration map are in §5.9.
| If you need to… | Go to |
|---|---|
| Get a one-screen summary | §0 |
| Understand the rules of interpretation (MUST, SHOULD, MAY) | §2.1 |
| Look up a defined term | §2.2 |
| Decide whether you need approval | §4.2, §4.4, §4.6 |
| Run a layer gate | §6.1 |
| Pick a rigor profile | §7.2 |
| Create or update a project record | §8 |
| Handle a finding, disagreement, or handoff | §9 |
| Set up security and external-conduct controls | §10 |
| Request an exception | §11.2 |
| Propose a change to P0 | §12.1 |
| Check completion before release | §13 |
| Use the operational checklist | §14 |
P0 Version 1.0 (Master) is the current baseline. Changes follow the amendment procedure in §12.1 of the Master file: a documented proposal, user authorization, a new version identifier, and a preserved prior version. Project-specific needs must not be used to rewrite P0 silently.
Record useful but non-essential improvements for a future revision rather than delaying work. Revise P0 when real use reveals a meaningful gap, contradiction, or impractical rule.
Note on assurance. The Master file's consistency audit (§15.2) is a self-audit by document read-through, not an independent review. For High-assurance use of P0 itself, obtain an independent review first.