Skip to content
View LalaSkye's full-sized avatar
:electron:
Alvian
:electron:
Alvian

Block or report LalaSkye

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
LalaSkye/README.md

Ricky Jones | AlvianTech | AI Governance Systems Engineer | TrinityOS

I build bounded proof surfaces for AI governance at the point where system action becomes consequence.

Core question

Where does the system physically stop?

The work focuses on execution-boundary control, admissibility, refusal, authority, receipts, and replay.

Public inspection standard

claim → evidence object → inspection path → claim limit

Public GitHub is an inspection surface, not full architecture disclosure.

Start here

What this work proves

Each public repository supports one local claim with an inspectable evidence object and an explicit stopping point.

What this work does not prove

Unless explicitly stated, these artefacts do not prove:

  • production readiness
  • compliance or certification
  • enterprise deployment
  • adoption or standardisation
  • path-universal governance
  • full architecture disclosure

Authorship

Architecture, methods, and system designs across this profile are the original work of Ricky Dean Jones, unless otherwise stated.

Contact

LinkedIn: linkedin.com/in/ricky-jones-1b745474

Status: active research and engineering work.

Pinned Loading

  1. execution-boundary-lab execution-boundary-lab Public

    Execution-boundary gate interface. Contamination cases. Adversarial suite. Admissibility at execution time.

    Python

  2. fail-closed-ai fail-closed-ai Public

    Public artefacts for fail-closed AI governance, refusal receipts, and runtime consequence control.

  3. invariant-lock invariant-lock Public

    Control primitive for preserving invariants before execution is allowed.

    Python

  4. policy-lint policy-lint Public

    Deterministic checks for governance language, policy claims, and admissibility drift.

    Python

  5. commit-gate-core commit-gate-core Public

    Runtime commit gate: no state mutation without a valid DecisionRecord. Execution-boundary AI governance.

    Python

  6. transition-admissibility-gate transition-admissibility-gate Public

    Gate surface for testing whether a proposed transition is admissible before execution.

    Python