I build bounded, inspectable controls at the point of authorisation for AI-supported systems. The objects named below are reference demonstrations, not production enforcement.
Where does the system physically stop?
The work focuses on execution-boundary control, admissibility, refusal, authority, receipts, and replay.
claim → evidence object → inspection path → claim limit
Public GitHub is an inspection surface, not full architecture disclosure.
These three names are the admitted public inspection class. They are the objects this profile asks a reader to inspect.
- start-here — entry demo: on its demonstrated path, no state mutation without a valid decision record
- commit-gate-core — authorize-only kernel: binds exact payload bytes to a DecisionRecord and returns authorisation or refusal; it does not apply the payload
- obligation-bound-policy-admission-lab — single-engine reference harness: historical admission ≠ current standing ≠ observed active state; not a gate
These are separate objects. Do not inherit proofs across them.
Routing index (not a fourth object): inspection-surface
The account also contains other public repositories — labs, scaffolds, indexes, and earlier experiments. A public name is not admission to the inspection class above. Those repositories do not inherit proofs from the three objects, and the three objects do not inherit proofs from them.
The Repositories tab is GitHub's inventory. It is not the inspection class.
Each of the three inspection objects supports one local claim with an inspectable evidence object and an explicit stopping point.
Unless explicitly stated, these artefacts do not prove:
- production readiness
- compliance or certification
- enterprise deployment
- adoption or standardisation
- path-universal governance
- full architecture disclosure
Repository-level authorship and contribution statements are recorded in each object. GitHub timestamps establish public possession at the recorded dates; they do not by themselves establish novelty, category priority or copying.
LinkedIn: linkedin.com/in/ricky-jones-trinityos
Status: active research and engineering work.