Ricky Dean Jones / AlvianTech / TrinityOS
AI Governance Systems Engineer.
Research Surface Map (canonical): lalaskye.github.io/inspection-surface — full index of repos, papers, terminology, provenance, and inspection levels.
An engineering archive and governance inspection surface.
It is not a personal homepage, marketing funnel, or authority claim.
It exists to show:
- bounded public claims
- inspectable evidence objects
- explicit claim limits
- attribution-stable provenance
Public inspection standard:
claim → evidence object → inspection path → claim limit
| Repository | What it is |
|---|---|
| start-here | Canonical entry point. Minimal runnable governance demo. Start here. |
| commit-gate-core | Execution-boundary commit gate. No valid DecisionRecord → no mutation. |
| fail-closed-ai | Documentation surface. Fail-closed governance pattern. |
| execution-boundary-lab | Gate interface contract. Contamination cases. Adversarial suite. |
| interrupt-ledger | Public inspection artefact. Receipt schema, replay, and stop evidence. |
| inspection-surface | Research Surface Map. Full repo index, system map, terminology, provenance. |
Where does the system physically stop?
The work focuses on systems where AI moves beyond advice and participates in actions that affect money, access, legal state, infrastructure, records, workflows, or downstream commitments.
The claim is narrow: governance is only real if interruption remains reachable under pressure.
These terms are used consistently across all repositories, papers, and public surfaces:
- execution-boundary AI governance
- runtime governance
- admissibility at execution time
- refusal receipts
- fail-closed AI governance
- consequence control
Synonym drift is avoided unless technically necessary. The terms are reused deliberately to keep the research surface semantically coherent, not to claim ownership over the language.
Research artefacts are timestamped, attributed, and cross-linked to canonical repositories.
Papers include explicit claim boundaries, canonical repo links, and DOI or preprint references where available.
See the Research Surface Map for current paper provenance.
Public artefacts are intentionally narrow. They do not claim, unless explicitly stated:
- production readiness
- compliance or certification
- enterprise deployment
- adoption or standardisation
- path-universal governance
- full architecture disclosure
Each repository reads as one node in a coherent governance research surface. No single repo is a complete system.
All architecture, methods, and system designs across this profile and its repositories are the original work of Ricky Dean Jones unless otherwise stated.
Repository licences govern code use. Broader architecture and authorship claims require explicit permission where not otherwise licensed.
Attribution is stable. Provenance is traceable. Timestamps are GitHub-recorded and independently verifiable.
Email: ricky.mcjones@gmail.com
LinkedIn: linkedin.com/in/ricky-jones-1b745474
Status: active research and engineering work.