Architecture › Overview
Overview
The P1Z Platform. Seven reusable layers, read top to bottom the way a client experiences them: conversation, outcome, knowledge, reasoning, their data, and the harness underneath. Built bottom to top; setup starts at layer 7. The Client Plane on the right is the only per-client build. Two sealed loops: the operational loop tunes how the platform runs, the knowledge loop promotes gated telemetry into the Knowledge layer. The sandbox and promotion checklist live in the ADLC page in Environment & Operations; they are lifecycle, not architecture.
How this portal is organized
| Section | What it covers | Read it when |
|---|---|---|
| Architecture | The whole system on one diagram, seven traversal patterns, the coverage proof, and the failure modes. | First day, and any time a design question needs the big picture. |
| Platform Layers | One page per layer, L1 to L7: purpose, components, the boundary test, and the plane parameters it reads. | When working inside a layer, or deciding where something belongs. |
| Environment & Operations | How the platform is built and run: the two disciplines, the cloud overlays, the activity inventory, the ADLC, and the 28-step setup sequence. | When provisioning, operating, or extending the harness. |
| Client Delivery | Everything per-client: the plane and its seven bands of values, daily operation, and the discovery guide that fills the binding. | During an engagement, from the first discovery session to steady state. |
| Playbook | The engagement execution blueprint: four parallel discovery tracks, the build phase, the operating rhythm, and the stage gates between them. | When running an engagement, from kickoff to value review. |
| Implementation (SSRA) | Skills, Scripts, References, Assets: the file grammar, skill anatomy, what belongs in each file, how multi-agent work is authored, and the full repository skeleton. | When writing any file the platform will run. |
| Engineering Standards | The build standards behind the grammar: the project skeleton, evals and LLM-as-judge, observability and logging, token and cost engineering, model customisation, and team standardisation. | When setting up a project or reviewing engineering practice. |
| Governance | The Decision Register, the master glossary, and every source cited. | Before relitigating a decision, and whenever a word is in doubt. |
The reading order
The sections run left to right in onboarding order: what the system is, what each layer does, how it is operated, what varies per client, which files you will touch, and the rules that bind it all. The previous and next links at the bottom of every page walk that exact path, so a new team member can read this portal front to back like a book.
Everything on these pages is durable by design. Anything transient, open questions, deferred scope, pending evaluations, lives in one place only: Governance, Decision Register.