Performance Boundary
Published measurements stay within explicit benchmark boundaries.
Performance claims refer to bounded benchmark surfaces, not to every deployment profile. If a metric includes network, persistence, export, or explanation rendering, it says so explicitly.
Published Measurement Surface
| Measurement | What it covers | What it excludes | Public method |
|---|---|---|---|
| Resolve() inner loop | Pure policy evaluation on recorded inputs inside the runtime. | Network, persistence, tenant I/O, export packaging, explanation rendering. | Optimized single-host benchmark run. |
| Trilean kernel operations | Primitive lookup-table operations inside the decision core. | Full decision flow, policy loading, artifact generation. | Microbenchmark on isolated inner-loop functions. |
| Content hashing | Hash generation over bounded payload sizes. | Signature generation, ledger export, remote transfer. | Fixed-input benchmark with controlled payload sizes. |
| Deployment envelope | Public framing only. On-prem, operator-controlled, no remote dependency in the critical path. | Universal latency guarantees for every infrastructure profile. | Architecture note plus deployment boundary review. |
Methodology Boundary
- Single host, optimized build, and controlled benchmark harness.
- Numbers on this page are scoped to published benchmark surfaces only.
- Microbenchmark claims are not end-to-end application latency.
- If an end-to-end deployment target is not published here, it should be treated as private or deployment-specific.
What Is Not Claimed Here
- Universal p99 latency for every tenant deployment.
- Ledger persistence cost for every storage profile.
- Export generation time for every artifact size.
- Authority-facing workflow latency or human escalation delay.
Architectural Reasons
Deterministic hot path
The critical evaluation path avoids external calls and runtime randomness.
Operator-local execution
The public deployment model keeps the runtime inside the operator boundary.
Published exclusions
Measurement without exclusions is rhetoric. Exclusions stay explicit.
Need the proof boundary before the number?
Use Reality Boundary for public claim levels and Technical Artifact for the canonical runtime semantics.