Date: 2026-09-09. Scope: the live Oracle OS route, memory retention, retrieval,
learning feedback, conversation continuity, and language composition.
Keep KAI running. No shutdown, restart, forced termination, deployment over the
running executable, or live pruning is authorized in this session. A later stop
must begin with a successful clean flush. All Rust repairs below are SOURCE
changes, pending a later owner-authorized deployment. Tests use a separate build
directory and small temporary universes, not the live brain files.
The earlier Claude notes and audits were read, then checked against current code
and live endpoints. Historical diagnoses are not assumed to remain current.
does not measure better retention, reasoning, or answer quality.
[internal endpoint] reports cognition_live=false; predictor, dreams, amygdala, andtheory_of_mind=false on this headless path. These are runtime status flags,
not proof that no cognition of any kind occurs.
BitNet/dense experts not mounted. A mounted flag alone does not prove a working
language generator; these counters are specific to their instrumented paths.
word_calculus::Operator::carry() still returns constants. Some lattice andsynapse weights change at runtime; the calculus carries are not learned yet.
it has no callers is no longer correct.
Raw retrieval evidence: reports/kai-path-audit-2026-09-09T15-32-00-347Z.json.
Six distinct Oracle probes were sent as CodexProbe, without teaching answers or
applying rewards. Manual review: **0/6 correct, five gap responses and one wrong
answer**. This is a small selected diagnostic set, not an intelligence score or
an LLM comparison. The vowel question was repeated during response-parser
diagnosis; repeats are not counted as additional cases.
These outputs did not contain word salad, but refusing to answer these cases
does not establish better understanding. Grammar and factual correctness must
be scored separately.
Speech probes can modify the session and trigger input-calculus learning. Later
retrieval returned the probe questions themselves as word-calculus memories,
including repeated copies of the arithmetic question. Correct arithmetic text
also existed among lower-ranked hits. This demonstrates that storing and
finding related words does not ensure that the right evidence reaches speech.
Seven new failure tests were run before implementation; all seven failed.
1. Successive deltas renamed old changes into backups that normal loading never
replayed. A pending delta now forces a full checkpoint before another delta.
This deliberately trades some extra full-save I/O for a loadable history.
2. A first save with few dirty cells could write only a delta, without a base.
Delta saves now require an existing base snapshot.
3. HashSet iteration could write appended cells out of order; the loader counted
out-of-order appends as applied even when it discarded them. Writes are
ordered; legacy deltas are parsed and validated in full, then ordered before
application. Missing/truncated entries fail instead of partially applying.
4. Failed saves could clear dirty flags. Flags now clear only after reported
success, so failed cell/metadata/synapse writes remain pending for retry.
5. Delta writes and synapse/metadata writes could fail while returning success.
Errors now propagate into SaveResult. Files are synced before rename.
6. Streamed saves ignored rename failure and removed the pending delta anyway.
A failed cell replacement now returns failure and preserves the delta.
7. Confidence rewards, confidence reductions, and cell retirement did not mark
cells dirty. These mutations now participate in incremental persistence.
8. The boot guard only recognized uncompressed metadata, so compressed/partial
snapshots could appear to be an empty first boot after a load failure. It now
recognizes both repository-root and direct-data layouts and partial state.
9. Failed compact loads could fall back to stale legacy JSON. Legacy fallback
now occurs only when compact state is absent. Both boot defects were
reproduced in additional failing tests before the source fixes.
_(implementation details omitted)_
successive saves, legacy append order, failure injection, boot guard detection,
incomplete delta rejection, and save/reload of reward/correction/retirement.
This does not prove past live learning was lost, nor recover historical deltas.
keywords. Several query functions previously replaced these with zero/empty
values. All those constructors use the shared conversion now.
ordinary indexed retrieval, before truncation can evict useful evidence.
sources, and check cellular ownership. Oracle passes its request user_id to
the initial full scan, multi-hop fallback, and training query. This is not a
complete audit of session isolation or downstream decoder ownership.
consumes, preserving other speakers as other speakers. Previously existing
repetition and follow-up checks could not recognize Oracle's own KAI turns.
_(implementation details omitted)_
[internal module]. Three focused retrieval tests pass. The wider core
run also exposed an old test that simulated a clock jump as ordinary idleness;
its fixture now tests continuous sweeps, with a separate clock-jump guard test.
The production LTD clock behavior was not changed.
Verified locally after the relevant repairs: 199 selected tests passed.
git diff --check passed for the four changed Rust modules. The audit script
passed node --check; its default plan made no requests, and its read-only
live run completed all six retrieval cases and wrote the evidence report above.
Tests do not demonstrate live post-deployment improvement or LLM-level behavior.
Release verification also passed: `cargo build --release --bin kai --target-dir
[local path]` produced v9.10.1003 in the alternate build directory.
That executable was not launched or copied over the live one. Final health check:
PID 13784 still running and [internal endpoint] reports alive. Applying the build remains
pending a later owner-authorized clean flush and restart.
node benchmarks/kai_path_audit.mjs prints the plan without requests.
node benchmarks/kai_path_audit.mjs --run --save reads live status/retrieval and
saves a compact report. It does not call ingestion, reward, save, pruning,
shutdown, or restart endpoints. --replies additionally sends Oracle turns;
those can be learned by the running engine. Do not treat previously probed
questions as withheld evaluation data.
Offline verification uses `cargo test --lib <filter> --target-dir [local path]
--jobs 2 -- --test-threads=1. Filters include persistence::tests, core::`,
bridge::oracle_server::, cognition::rerank::, and cognition::voice::tests.
The next substantive implementation is turn-scoped Oracle outcome credit and
question/fact separation, followed by contextual propositions and composition.
Nothing here establishes LLM-level capability or a timetable for reaching it.