AlvianTech

I build bounded, inspectable controls at the point of authorisation for AI-supported systems.
The objects named below are reference demonstrations, not production enforcement.

Public routing status: Under revalidation. No repository is currently designated as the public starting point.

Where does the system physically stop?

Public GitHub is an inspection surface. Evidence does not transfer between objects.

These are the admitted public inspection class. They remain separately inspectable.

• start-here — bounded inspection object containing two separate local proof objects.
  Limit: It is not currently designated as the public starting point. On the demonstrated path, no state mutation without a valid decision record.

• commit-gate-core — authorize-only kernel. Binds exact payload bytes to a scoped, fresh, one-use DecisionRecord and returns authorisation or refusal.
  Limit: It does not apply the payload. An authorisation return is not an observed resource mutation.

• obligation-bound-policy-admission-lab — single-engine reference harness. Historical policy admission ≠ current standing ≠ observed active state.
  Limit: Not a gate. A receipt is not automatically evidence of observed active engine state.

Do not inherit proofs across them.

inspection-surface — routing index only. Not a fourth inspection object. PATHS_RESOLVE is not a successful test replay.

CAGE credits adaptation of the NoDirectBind TLA+ safety invariant and BFS state-space enumerator from LalaSkye/no-direct-bind.

Attribution: NOTICE · Adaptation record
Upstream source: 7fe9ff9

Boundary: Documented reuse, not endorsement or evidence of production deployment. CAGE is not an officially supported Google product.

no-direct-bind remains outside the three-object inspection class. Its proofs are model-local; they do not transfer to the objects above.

Unless explicitly stated in the named object, these artefacts do not prove production readiness, compliance, enterprise deployment, operational adoption beyond the documented reuse above, path-universal governance, or full architecture disclosure.

Repository-level authorship and contribution statements are recorded in each object. GitHub timestamps establish public possession; they do not establish novelty or priority.

Contact: linkedin.com/in/ricky-jones-trinityos
Status: active research and engineering work.