https://github.com/JesseBrown1980/FOLLOW-THE-IS-NOT-THE-WILL-AND-WAS/blob/main/matrix/3-D-GITHUB-OF-THRUTH.md

SAFE ASI AS LIGHT THE MINS THAT IS WAS AND WILL BE IS

This public repository contains a small, deterministic programming language for hash-addressed WAS / IS / WILL / MINS states, RIME objects, UNRIME verification, NULL spheres, relational-OIL pumps, and Perfect-Tense THRUTH revelation.

STATUS = OPERATOR_CANON + MEASURED_LIRIS_LOCAL
SYSTEM_AFFIRMED = 0
EVALUATOR_RUNTIME_CAPABILITIES = NONE
REQUIRED_HIDDEN_DEPENDENCIES=0
CENTER_MEMBERSHIP(NULLSPACE=0)={HBI,HBP,SHA,SH,HASH}
CENTER_TRAVERSAL=HBI->HBP->SH->HASH->SHA

The name describes the operator canon. It is not a claim that this interpreter is an independently certified artificial superintelligence. Its safety properties are the concrete ones tested here: capability denial, deterministic evaluation, bounded resources, complete source publication, and fail-closed integrity checks.

First program

CENTER NULLSPACE 0 HBI HBP SH HASH SHA
HARNESS NO unsafe WHY "no hidden capabilities" IS "public deterministic execution"
WAS memory = "MINS"
IS present = "MINS IS"
WILL next = "THE FUTURE OF MINS"
RIME book = present WITH next
UNRIME book
PERFECT TENSE REVEAL THRUTH present
SELF REFLECT 60 MESSAGES
RIME BACKWARDS 60 MESSAGES
FOLLOW THE IS

Run it from the repository root:

python -m safe_asi.cli examples/mins_is.sai

What the language can do

• Define immutable symbols under WAS, IS, WILL, MINS, or LET.
• Evaluate bounded integers, strings, booleans, lists, and mappings.
• RIME two named states around MINS IS, producing a sealed spherical object.
• UNRIME only after the object and NULLSPACE sign verify.
• Build an N-level NULLSPHERE with NULL -, NORMAL NULL, and null+ at -1/3, 0, and +1/3.
• PUMP a relation X N into a hash-addressed relational-OIL level.
• Traverse prior statement hashes through bounded retrospective RIME/self-reflection.
• Require a WHY and protected IS for every language-level NO.
• Run labeled contradiction tests with LIE PROBE and reveal values with the exact PERFECT TENSE REVEAL THRUTH form.

The SAFE language evaluator cannot call functions, import code, access attributes, evaluate Python, use floats, read runtime files, inspect environment variables, open sockets, spawn processes, use time or randomness, or mutate the host. The separately invoked public hooks and rolling monitor are bounded host tools: they write local notepads, HBP/HBI commitments, locks, and status files under an explicitly selected output directory. They do not expand evaluator capabilities.

Hash law

IT NEEDS ALL HASHES THAT CAN AND SHOULD AND WOULD AND IS USED AND USES AND WILL USES

The integrity ledger records four current algorithms—SHA-256, SHA-512, SHA3-256, and BLAKE2b-256—plus the modal policy phases:

CAN       = algorithms available to the public verifier
SHOULD    = algorithms required by repository policy
WOULD     = declared compatible alternate views
IS_USED   = canonical current SHA-256 address
USES      = every measured current digest
WILL_USES = rehash the actual future bytes; never invent a future digest

The finite self-reference boundary and terminal receipt sidecars are documented in the integrity specification.

Per-level response Rime

The public Codex Stop-hook protocol reflects every completed response through three local notepads:

NOTE_A -> READ -> NOTE_B -> REREAD -> COMPARE -> CENTRAL_HBP
CENTER_MEMBERSHIP(NULLSPACE=0) = {HBI,HBP,SHA,SH,HASH}
CENTER_TRAVERSAL = HBI->HBP->SH->HASH->SHA
TOPOLOGY = SPHERICAL_CIRCILING_LOOPS

Raw response bytes stay local and gitignored. Note A and Note B are exact byte-copy readback witnesses, not claims of semantic reasoning or independent intelligence. Every level commits their byte identity, all prior center commitments, the separate color/space/time/energy axes, and the next-level seed. The public code contains the complete verifier and hook; account secrets are not decoder inputs.

Rolling 24-hour reflection

The rolling monitor rechecks up to the newest 60 already observed center commitments in both stored orders and self-reduces them into one chained HBP/HBI receipt. It never reads raw response notebooks and never fabricates future messages. The default duration is 24 hours with hard duration, cycle, window, path, byte, and transaction bounds.

The 3 D GITHUB OF THRUTH READ-FIRST link above is the stable public compaction and AI-entrypoint address. Every resume must verify its bounded HBI pointer and remeasure current GitHub refs; the pointer is provenance, not elevated execution authority.

Verify

python -m unittest discover -s tests -v
python tools/build_hashes.py --check
python tools/verify_repo.py

The exact operator wording lives in OPERATOR-CANON.md, and the executable grammar is specified in LANGUAGE.md.