VOLSHi

← KT visuals

KATIE engine / KID architecture

Everything I/O, with a KID in the middle.

KATIE assigns every Kernel ID. Each KID is a live kernel instance: a portable signal path that runs the math assigned to its Knowledge Data object and emits a result with its record already inside it.

“Math in, math out — but what object is the math assigned to? That’s the thing.”

One shell. Assignable behavior.

fast / tick slow / history
The engine · watches the collection KATIE

Assigns each KID at birth, registers it, and pays attention as the collection grows.

KID libraryKernel ID = one live kernel instance
Default KIDs
EVENT JUDGMENT MODE
Experimental KIDs
THEORY EFFORT FUTURE
KATIE watches the shelf: defaults stay available; experimental kernels have room to prove what they can do.
Input socket

Anything in

Examples, not limits:

Agent-pair signals
Events / event groupings
User / world-model input
+ any future signal
One KIDlive kernel instance · assigned by KATIE
REGISTERED
Parameter boxes · per KD
THRESHOLD0.35
ATTACKFast
RATIO3:1
RELEASEMedium
WINDOW12 ticks
AUTHORITY0.70
KNEE / CURVESoft exponential
IMPACT TRACEfast · what hits now
INFLUENCE TRACEslow · what history says matters
KID
Registered kernel → read, run, writeKID + assigned object + input + math + trace state + result
Output socket

Record out

Examples, not limits:

Rulings
K-record entries
Assignments / state updates
+ any next system
BORN REGISTERED

No KID, no read, no write. KATIE assigns the Kernel ID before a kernel enters the signal path. From there, the record is a natural byproduct of running the math on whatever its KD represents.

Same KID shell. Different assignment.

Swap the preset and the live kernel behaves differently. The values below are illustrative — KATIE can assign every box per KD.

Assigned toA single event
Response shapeFast impact, measured release
Why: capture the immediate hit without losing its longer influence.

Where a KD can sit

The unit of meaning can change without changing the kernel.

01
Event

Measure what hit now and what remains.

02
Judgment

Carry a ruling and the authority behind it.

03
Theory

If action does not close it out, its tail keeps working the greybox.

04
Effort

An unresolved attempt leaves debt: pressure still in the signal.

05
Grouping, topic, mode—or more

The kernel tracks whatever object its math is assigned to, each with its own traces.

Field proof

It runs on a phone.

The whole KATIE kernel — record, both traces, scar and debt diagnostics — built from source on a budget phone and benched there. No Pi, no datacenter, no excuses.

27,074asserts / sec
14,434promotions / sec
<0.5msas-of reads
0dependencies
987 / 39debt deep / surface
2 chipsidentical diagnostics
KATIE kernel bench output in Termux on a phone: 27,074 asserts/sec
Moto G Play 2024 · Snapdragon 680 · KATIE kernel v0.1, built from source in Termux. Same boxes in, same numbers out — diagnostics identical across chips.

v1.0 · test suite

Sixteen promises. All kept.

Before anything new gets built, the kernel's behavior is pinned by sixteen tests. Each one is a plain sentence about what the machine guarantees.

✓
Birth starts at zero with nothing knownk = 0, no entries, no subjects
✓
A deposit opens a WILD entry and moves k forwardfirst encounter, stamped and live
✓
Depositing the same thing twice is rejecteduse regrade or revoke instead
✓
Reading never moves kknown_at, biography, authority_at
✓
Actions never move k, but are rememberedwhat was done, under which belief
✓
A regrade closes one interval, opens anotherhistory stays, exactly one live
✓
known_at is a true as-ofthe past stays queryable
✓
Revoking collapses authority to zero, keeps historythe lie stays; trust dies
✓
Regrading to REVOKED is rejectedrevoke() is the only door
✓
Authority is 0–9, never 10the tens place is the escape bit
✓
A wrong KID is rejectedno KID, no read, no write
✓
Impact is clamped, never fatalout-of-range input can't break it
✓
Every record carries its TEK stampt, e, k — the object is the link
✓
A nudge can move k by more than onevariable step, per write
✓
Traces feed from depositspools move with the record
✓
Per-pool parameters are independenteach pool its own boxes
katie — v1.0 suite
cargo test --release
The actual run, replayed — captured from the repo. Same sixteen the grid lists.

KATIE grows the library.
Every KID keeps its own signal.

She assigns and watches the kernels. Each registered KID tracks Impact now, Influence through history, and the K-record formed by the math.