Skip to content
Charles Jones
Documentation menu

Open source

Ingenium

A sovereign agent runtime: identity sealed at genesis, state that only appends, and a turn cycle with a refusal built into it.

On this page

Ingenium is Latin for the inborn thing — what is begotten in a thing as the thing it is, before any cultivation. It is also the root English took to make engine.

The runtime gives an agent a cryptographically sealed identity, state it cannot quietly rewrite, and a turn cycle that can refuse. Built solo, from contract documents down.

The machine

Ingenium regulated turn cycle An agent sealed at genesis runs a seven-hook turn. A vitality gate at hook two, before generation, can decline the turn on the agent's own recorded condition. Consequence is written to an append-only ledger at finality. ARCHITECTURE INGENIUM INNATE — SEALED ONCE GENESIS SEAL SHA-256 over seed.json 3c51fa88a1afa47cba… sealed 2026-05-10, unchanged If the seal changes the agent is not the same agent — and the runtime says so at boot WRITTEN BEFORE IT RAN 31 contracts · 28 ADRs written before the runtime was trusted with a turn THE REGULATED TURN SEVEN HOOKS one turn, in order 1 Intake pre-generation 2 Vitality Check inhibition gate 3 Inference generation 4 Validation post-generation 5 Execution action dispatch 6 Synthesis delta computation 7 Finality four-way paired commit APPEND-ONLY VITALITY 1.00 — integrity, stability, resilience all 1.0 CHRONOS epoch 6 last state 2026-05-13 KARMA LEDGER 179 entries · covenant marker the marker's absence is fatal at boot boots commits TURN DECLINED on the agent's own recorded condition, before generation is attempted The gate sits BEFORE generation — so the runtime declines a turn rather than attempting it and failing. A declined turn writes nothing.

What it is

Sealed at genesis

An agent is sealed once, at genesis, with a SHA-256 over its seed. The seal is the identity: if it changes, the agent is not the same agent, and the runtime says so at boot rather than carrying on.

3c51fa88a1afa47cba81cb20929994b3e096a8eb325969c965d6e3ec477505f5

Sealed 2026-05-10 17:31 UTC; unchanged since, and verifiable against the published artifact.

Append-only karma

Consequence is written to an append-only ledger under a covenant marker. The marker’s absence is fatal at boot — irreversibility is enforced at startup, not promised in a document.

A turn that can refuse

Every turn passes seven named hooks. A vitality gate sits at hook 2, before generation, so the runtime can decline a turn on its own recorded condition rather than attempting it and failing.

A correction worth keeping, because the record carries it. Earlier material — including the hosted walkthrough — says eight hooks. The contracts later ruled that preprocessing is a pre-hook outside the cycle (ADR 0020), and that the timing rule once called “hook 8” is not a hook. Seven is the corrected count, and the older number stays visible in the walkthrough rather than being quietly edited out.

The numbers

source
31 Contracts contracts/, README excluded; snapshot 2026-06-27
28 Decision records decisions/, numbered ADRs 0001–0028
179 Karma entries append-only ledger, last state 2026-05-13
6 Epoch chronos epochs record, 2026-05-13T14:50:24Z
1.00 Vitality integrity, stability and resilience all 1.0

Instruments verified 2026-08-08 against the 2026-06-27 snapshot.

Why it matters

Agent identity and governance is the industry’s current hard problem: how you know which agent acted, on what authority, and whether its account of itself can be checked.

Ingenium answers it structurally rather than procedurally — a seal that breaks loudly, a ledger that only grows, and a lifecycle with a refusal built into it. Thirty-one contract documents and twenty-eight decision records were written before the runtime was trusted with a consequential turn.

Status

Laid up. Development suspended 2026-06. Recommissioning planned.
Sealed 2026-05-10 — genesis seal set, unchanged since
Last turn 2026-05-13 — last recorded runtime state
Suspended 2026-06 — development stopped, nothing abandoned

The walkthroughs

Three exhibits trace the runtime from NO_SEED to a first consequential turn: genesis, activation and identity port.

They are served in Ingenium’s own visual identity, not this one. That is deliberate: the runtime has a documented visual vocabulary of its own, anchored to the four senses of the word, and it outranks this site’s palette on its own subject. The walkthroughs are the vessel’s interior; this page is the engine room.

The pairing

The Model Context Protocol (MCP) server verifies outputs. Ingenium governs the agent that produces them. Together they are the same argument from both ends: governed agency.

↑↓ navigate↵ openesc close