About — Verifiable Proof Systems

Most systems thinking in this space starts in theory or code. Mine started in service environments where the gap between what was claimed and what actually happened had immediate, visible consequences.

Current status: This site documents the framework and examples. Runtime enforcement components are under development and are not presented here as production infrastructure.

Early Service & Kitchen Discipline

Le Cordon Bleu training led into high-end kitchen management — environments where execution gaps are visible immediately. A ticket says medium-rare and the plate goes out well-done — the boundary failed. There is no ambiguity, no retrospective reinterpretation.

The discipline of mise en place — everything in its place, prepared before service — maps directly to operational boundary control. A line cook’s station is an execution envelope: tools ready, ingredients prepped, timing precise, handoff clean. The same pattern appears in agent execution: authorized tools, prepared context, bounded action, evidence of handoff.

Compliance Auditing — Procedure vs. Ground Truth

Working as a compliance auditor at Shell and BP service stations revealed a different gap: the difference between the binder on the shelf and what actually happens at the pump. Documented procedures that nobody follows. Audit theater that creates false confidence. The cycle: procedure written → nobody follows → incident happens → new procedure added → repeat.

The pattern is the same one that appears in AI-mediated systems: documented safety policies, no enforcement at the point of execution.

A procedure that isn’t enforced at the point of execution is not a control. It’s a wish.

Command Clarity & Delegation

Growing up in a military family made the structure of authority obvious: chain of command, delegation, orders vs. intent. The difference between “I authorized this” and “this was within my standing orders.” Mission-type orders that communicate intent and constraints, not micromotion — exactly the shape of an authorization envelope.

Authority without evidence is just rank. Evidence without authority is just noise. You need both, and you need to know which is which.

The Through-Line — Collapsed Layers

These three environments — kitchens, compliance audits, military structure — revealed the same recurring pattern: layers that should remain separate get collapsed.

In kitchens: the recipe says ≠ the cook did ≠ the plate proves. In audits: the policy says ≠ the operator did ≠ the log shows. In AI: the prompt asked ≠ the model inferred ≠ the tool executed ≠ the log proves.

The 7-layer framework is a practical translation of that lived insight — a way to keep the layers separate, inspectable, and claim-bound.

Connection to the Framework

Philosophy

• Human-centric: People decide; code and agents assist.
• Evidence over hype: Claim discipline is respect for operators and reviewers.
• Boundaries strengthen trust: Clear “not claimed” statements are features, not weaknesses.

Explore the framework → · See rough examples → · Request a Claim Boundary Review →

Structured Facts