Catch the defect at the keystroke, not in the postmortem.
Layer 1 records what an agent did. Layer 2 is the pre-deploy discipline that stops the deploy that would have needed recording.
AI velocity is real. The defect rate compounds without discipline.
Agents now author code, copy, claims, schemas, dashboards, and outbound artifacts at a rate no review pipeline designed around human throughput is calibrated for. Most defects are small. A few are silent. Without explicit pre-deploy primitives, the silent ones reach the audit layer as fabrications, overstatements, single-run metrics treated as standards, and policy drift recorded as fact.
Layer 1 is the right place to record what an agent actually did. It is the wrong place to discover that what was recorded should never have shipped. The cost of a Layer 1 record of a defect is the cost of a permanent, court-admissible memorial to that defect. The right point to catch the defect is at the keystroke that would have produced it.
Production Discipline is the explicit set of primitives that do that catching. They are stated as doctrine, encoded as agent-runnable checks, and applied to every artifact Bonis ships through its own pipeline before that artifact reaches any external surface.
Each artifact passes all six, or it does not ship.
The six primitives below are not aspirations. They are ship gates. An artifact that fails any one halts the queue under the 100% Stop-and-Save Rule until the underlying issue is either fixed to the bar or explicitly waived under recorded authority — never silently deferred.
Every concrete claim resolves against three independent sources: code (or shipped surface), memory (or doctrine), and an external authoritative source (a standard, a public chain, a published spec, a court rule). A claim that resolves on fewer than three sources is held until the third source lands or the claim is rewritten down to what the existing sources support.
A single-run output of a noisy metric — Lighthouse Performance, sub-second latency under cold load, model evals that depend on sampling — is one sample from a distribution, not a deterministic standard. The bar is at least three runs, characterized variance, and the floor as the reportable number. Single-run highs do not become memorialized facts.
Work measured below the bar on any axis — Truth Protocol GREEN, Stealth CLEAN, Coachbuilt floor, axe-core zero violations, build clean, deploy verified, defensive-only — halts the queue. Either fix to the bar or record an explicit waiver before resuming. No 'ship at 95% with a TODO.' The deferred TODO is the failure mode this rule was named to stop.
Public surfaces meet a Lighthouse 90+ deterministic floor and axe-core zero violations as ship gates, not as aspirations. Eight measured axes — typography, grid, palette, imagery, copy, microinteractions, performance, accessibility — are scored before deploy. Ferrari-class body for the engine inside; the body fails the audit if it is not.
Public surfaces carry only what Bonis is and what the tech can prove. Operational pace, prospect names, internal lane names, planning, customer-count framing, and partnership status do not appear. The check runs as an automated sentinel pass and as a human read; the bar is what a competitor or evaluator would learn from the surface.
Every concrete claim on every public surface resolves to a ledger entry pointing at code (file:line), shipped URL, public chain anchor, USPTO record, or external authoritative source — required reading before any outbound, RFI, or page update lands. The ledger is the system of record for what is provable; surfaces are derived from it, not the other way around.
The audit layer answers what happened. Discipline answers whether it should have.
Once an organization is shipping AI-authored artifacts at production velocity, the same five pre-deploy questions arrive on every artifact. Discipline primitives produce explicit answers; absence of discipline produces silent assumptions that the audit layer will eventually memorialize.
Is each concrete claim verifiable against three independent sources?
The Truth Protocol three-source rule is run before the artifact lands. Two-source claims are rewritten down to what evidence supports; one-source claims are held. The audit chain never carries a claim that did not pass.
Is the metric a deterministic floor or a single-run sample?
Multi-pass measurement converts noisy metrics from anecdotes into characterized distributions. The reportable number is the floor across runs, with variance disclosed. A single-run high never becomes a memorialized fact.
Does the surface leak operational, prospect, or planning detail?
The Stealth Posture sentinel pass scans every public-surface candidate before deploy. Operational pace, prospect names, internal lane names, partner status, and customer-count framing are caught at the line and rewritten or removed.
Does the artifact meet the ship gate, or does it carry a deferred TODO?
The 100% Stop-and-Save Rule halts the queue rather than letting work below the bar ship with a TODO that was never going to be returned to. Either the bar is met, or an explicit waiver is recorded under the named authority that issued it.
Is the rationale encoded for next-shift continuity?
A waived gate, a deferred trade-off, or a deliberate floor-vs-ceiling choice is recorded as memory under named doctrine. The next operator — human or agent — inherits the why, not just the what. Continuity is a primitive, not a postmortem artifact.
What composing Layer 2 above any stack gives you.
Pre-deploy
The discipline runs before the artifact reaches any external surface, any audit anchor, any RFI, or any outbound communication. The cost of a pre-deploy fix is orders of magnitude below the cost of a permanent Layer 1 record of the same defect.
Deterministic measurement
Noisy metrics are converted into characterized distributions. Reportable numbers are floors, not single-run highs. Determinism is the property that lets the audit layer claim its measurements with a straight face years later.
Methodology + tooling
Each primitive is published doctrine and is encoded as an agent-runnable check. The methodology ships today as readable doctrine; the tooling-as-SDK ships next as Knox Agent Audit SDK Tier 2, the same primitives installable into any agent pipeline.
Agent-runnable
The Truth Protocol auditor, the Coachbuilt visual auditor, and the Stealth Posture sentinel are agent roles that run in-process during the build. A human reviewer signs off the waiver path; the routine path is mechanized.
Open doctrine
The six primitives are stated openly. Operators who want the same bar can adopt the same doctrine without Bonis. The productized SDK is convenience, not gatekeeping; the standard is the moat.
Composable above any stack
Production Discipline is upstream of any control plane, any agent runtime, and any orchestration framework. It does not couple to any single vendor; it is the layer that decides whether the artifact was sound enough to reach those surfaces at all.
Discipline catches; audit records.
The two layers are not interchangeable and not redundant. Layer 2 stops what would have become a tampered or fabricated record. Layer 1 records what survives the discipline. The artifact that reaches a court, a regulator, or a counter-party is the one that passed both.
A Layer 1 audit record produced without Layer 2 discipline is a faithful record of an unsound artifact. A Layer 2 pass without Layer 1 anchoring is a moment-in-time check with no permanence. Together, the artifact is sound at deploy time and verifiable years later — a property neither layer produces alone.
Both layers compose above any control plane, any agent runtime, and any orchestration framework. The customer never has to choose between the discipline layer, the audit layer, and the control plane they prefer.
Doctrine first. Tooling second. Audit third.
Adoption does not require Bonis. The doctrine is open and the primitives are individually adoptable today. The productized SDK packages the same primitives as installable agent-runnable checks for teams that want the convenience and the audit-chain integration.
Discipline applied to one's own work, not enforcement on others.
Production Discipline is doctrine applied to artifacts originating in the operator's own pipeline. Bonis does not access third-party agents, does not inspect non-consenting external pipelines, and does not undertake any active disruption of external systems. The doctrine is invitational: operators who want the same bar adopt the same primitives. Lawful authority — courts, regulators, platform owners — decides what to do with the resulting evidence.