Point One Zero Platform architecturev11 · generated viewSign in to edit
Platform Layers › L7 Environment
L7 Environment
Where this layer sits on the architecture; the client plane band to its right shows the values it reads.
L7 Environment (the Harness) BUSINESS-BLIND · SELF-OPTIMIZING
The machinery every engagement runs on: the agent harness (everything that executes during a run) and the platform infrastructure (everything provisioned around runs). This card places it in the stack; the Environment & Operations section covers it in full, including the cloud overlays and the greenfield setup sequence.
Agent loop and run-contract enforcement, guardrail mechanics, session and memory machinery, observability and eval infrastructure
Identity and tenancy, CI/CD and the SSRA skeleton, secrets and keys, SRE and incident operations, disaster recovery
Operates the machinery of both MCP boundaries: the north platform gateway and the south tool servers
Self-optimizing through the operational loop: every tuning lands as a versioned config change through CI
Boundary test: if the person operating this layer has to ask what a PE term means, the layering has failed.
Client-specific configuration for this layer is specified band by band in Client Delivery, C7 spec: every input with its binding key, generated artifact, and verifying check.
Component reference
Agent Loop & Run Contracts
The machinery that executes every agentic run and enforces each run's declared end state and token budget.
ImplementationOver-budget or over-iteration runs are killed and raised as incidents; long runs summarize completed phases to external memory and resume from checkpoints rather than restarting.
Guardrail Mechanics
Deterministic enforcement: pre and post checks, gate blocking, PII redaction.
ImplementationThe hooks engine plus the policy engine of the chosen cloud; a gate cannot be bypassed by any code path, and a hook never calls a model.
Session & Memory Machinery
Context assembly, compaction, and short and long-term memory stores.
ImplementationDelivers context packs whose contents come from Knowledge and the binding; persistence is deliberate, never accumulation, which is what prevents the Groundhog Session antipattern.
Observability & Eval Infrastructure
Content-blind tracing, cost and token metering, latency tracking, gate metrics, and the eval runner.
ImplementationOTEL traces into the overlay's monitor; the audit trail is append-only; every generated deliverable is logged with its template version; eval suites run scheduled and pre-deploy.
Identity & Tenancy
Service identities and per-tenant isolation across stores, keys and networks.
ImplementationOne service identity per agent; the automated cross-tenant read-path test runs in CI and a red result blocks deploys.
CI/CD, ADLC & SSRA Skeleton
Pipelines, promotion gates, and the templates every engagement is stamped from.
ImplementationFive CI gates including the business-blindness linter; registry-only deploys mean an unregistered agent cannot obtain credentials; the skeleton makes a new engagement start from template, never blank.
Secrets & KMS
Per-tenant keys and secrets with rotation.
ImplementationConfiguration files carry vault references only; a literal secret in any file fails review; rotation is scheduled, not remembered.
SRE & Incident Operations
Runbooks, disaster recovery, on-call, and safe deployment mechanics.
ImplementationRainbow deployments shift traffic gradually so running agents are never disrupted; restores are rehearsed, not assumed.