TRU / COIL System

A sovereign offline intelligence (TRU) backed by a content-addressed binary sync protocol (COIL).

---

Status (2026-06-08)

Component	State
COIL Sync	✓ 13 artifacts complete, 6,713 chunks, NO DRIFT
TRU HOLO	✓ Phase 44 + v11 live (TRU_HOLO (11).html)
Status API	✓ https://splashdown.zo.space/api/coil-status
zo.space	✓ 63 routes live, homepage locked

---

What is TRU?

TRU is a chat-based reasoner that runs in a single HTML file, fully offline, no server, no dependencies. It answers questions, looks up scripture, handles math, parses Greek, and remembers what you teach it. Small enough to audit by hand.

• Live landing page with demo: splashdown.zo.space/tru
• Build your own (no code): splashdown.zo.space/tru/build — add your own verses, Greek terms, brain nodes, and download a personalized TRU_PERSONAL.html
• Offline build (recommended): TRU/TRU_PORTABLE.html (44KB, hand-written, 15 brain nodes, 83 KJV verses, 36 Greek terms)
• Spec / behavior: COIL_PROTOCOL.md (knowledge-graph + scoring engine), SPEC.md, TRU/AGENTS.md

The personality is defined in SOUL.md (Dry Truth, Steady Nudge).

What is COIL?

COIL is the binary sync protocol that ships large content-addressed chip artifacts between this workspace and a remote mirror. It is the transport layer; TRU is the mind.

• Protocol spec: COIL_PROTOCOL.md — chunked transfer, hash-based delta, optional compression + encryption, resume via checkpoints
• Reference implementation: COIL_Server.js, COIL_compress.js, COIL_encrypt.js, COIL_deltaCheck.js, COIL_taskQueue.js, COIL_uploadPool.js
• Uploader UIs: COIL_Uploader_v2/v3/v4.html
• Master manifest: COIL_MASTER_CHIP.json (canonical ledger of every chip, its hash, size, and sync state)
• Local mirror: COIL_mirror/ (cached chip files)
• History of failed runs + fixes: coil_extracted/MANIFEST.md

Repo layout

Path	What it is
AGENTS.md	Root workspace guidance for the AI agent
SOUL.md	TRU's persona (tone, behavior, identity)
README.md	This file
SPEC.md, SPEC_005.md	Engineering specs
Manifesto.md, Mission_Log.md	Long-form intent and history
KNOWLEDGE_BANK.md	Curated concepts TRU reasons over
Getting Started.md	Onboarding notes
TRU/	TRU runtime — 30 historical HTML builds + the recommended starter
TRU/TRU_PORTABLE.html	Start here. 44KB single-file reasoner, postMessage bridge, runs anywhere
TRU/TRU_FRESH.html	Earlier 30KB hand-built build (superseded by PORTABLE)
TRU/INDEX.md	Guide to the 30 historical builds — which to use, which to ignore
TRU/AGENTS.md	TRU-specific guidance for the agent (routing rules, decision precedence, dignity invariant)
TRU/*.png	Screenshots of the live /tru and /tru/build pages
tru_core.py, tru_shield.py, tru_control_center.py	Python runtime that powers the trading / mission side
tru_optim/, Knowledge Bank/, Documents/, Images/, Articles/	Source material
COIL_PROTOCOL.md	COIL Sync Protocol v1.0.0 (chunked + content-addressed)
COIL_MASTER_CHIP.json	Canonical ledger of all chip artifacts (size, hash, sync state)
COIL_mirror/	Local mirror of remote chips
COIL_Server.js, COIL_*.js	Reference COIL server and helpers
COIL_Uploader_v*.html	Browser-based uploader UIs (v2/v3/v4)
coil_extracted/	Archived scripts + MANIFEST from TASK 005 sync (provenance chain, hash-verified reconstruction)
DASHBOARD_CONFIG_V/, COIL_DASHBOARD_CONFIG.json	Mission dashboard config
ABSORBED_TRADES_MANIFEST.*	Absorbed trade records
Historical_Market_Solar_Overlay.csv	Market/solar historical data
CNAME	GitHub Pages custom domain
index.html	Landing page (GitHub Pages)

---

How to run TRU offline

# from this repo
open TRU/TRU_PORTABLE.html
# or, with a local server (recommended for any browser quirks):
python3 -m http.server 8000 --directory .
# then visit http://localhost:8000/TRU/TRU_PORTABLE.html

No build step. No npm install. The file is self-contained: brain, KJV snippet, Greek table, routing, chat UI, and a postMessage bridge for embedding.

Quick test queries

Query	Expected behavior
who are you	TRU · IDENTITY · 100%
read john 3:16	Full KJV verse with reference
micah 6 8	Same (no-colon form works)
12 * 7	Math route returns 84
what is mercy	Brain match
agape	Greek term + transliteration + definition
stats	brain / verses / greek / memory counts
remember: my name = Joe	Saves to localStorage; later what is my name recalls it
teach: jazz = 1930s American music	Adds to brain permanently (in this session)
clear	Wipes transcript (not memory)

How to make your own (no code)

The easiest path is the live builder:

1. Go to splashdown.zo.space/tru/build
2. Add your own verses, Greek terms, and brain nodes
3. Hit Download TRU_PERSONAL.html
4. Open the file in any browser. Done. Yours. Local. Private.

It starts with the 83-verse / 36-Greek starter, and you can add as much as you want on top.

How to extend TRU by hand

TRU/TRU_PORTABLE.html is intentionally small so it can be hand-edited.

1. Open the file. Three sections you'll touch:
   • YOUR BRAIN (around line 100) — array of {k, v, t} knowledge nodes
   • YOUR KJV VERSES (around line 200) — array of [ref, text] scripture entries
   • YOUR GREEK TERMS (around line 300) — array of {t, g, G, p, d} Greek entries
2. Add a brain node. Append to the BRAIN array:

   { k: "what is X", v: "the answer", t: ["X"] }

3. Add a verse. Append to the KJV array:

   ["john 3:16", "For God so loved the world..."]

4. Add a Greek term. Append to the GREEK array:

   { t: "agape", g: "agape", G: "ἀγάπη", p: "noun, feminine", d: "self-giving love" }

5. Wire a new route (optional). In buildResponse(q), add a branch above the brain-fallback block. See how findVerse, findGreek, or the math route are structured.
6. Verify. Reload in a browser. Test the new query.

Routing precedence (top wins): system commands → remember: / teach: / clear / stats → math → time/date → verse → Greek → brain → memory → honest GAP.

How to embed TRU in another page

TRU_PORTABLE.html exposes a postMessage bridge. From a parent page:

<iframe src="TRU_PORTABLE.html" id="tru"></iframe>
<script>
  const iframe = document.getElementById('tru');
  iframe.addEventListener('load', () => {
    iframe.contentWindow.postMessage({ type: 'tru_send', text: 'read john 3:16' }, '*');
  });
  window.addEventListener('message', (ev) => {
    if (ev.data?.type === 'tru_reply') {
      console.log(ev.data.tag, ev.data.text);
    }
  });
</script>

See /tru for a working example with copy-paste buttons.

---

How COIL works (TL;DR)

• Files are split into 256-byte chunks; every 20 chunks become a super-chunk.
• Each chunk is addressed by SHA-256 of its uncompressed bytes. The server stores chunks by content hash, not by filename.
• An uploader walks the local mirror, computes hashes, and only sends chunks the server is missing (delta sync).
• A manifest (COIL_MASTER_CHIP.json) lists every artifact, its size, its root hash, and its sync state.
• Resume is automatic: the server returns the chunks it already has; the uploader skips them.
• Integrity is end-to-end: the manifest's root hash must match the reconstructed content's SHA-256. Any drift fails the sync.

Full spec: COIL_PROTOCOL.md.

Reference scripts

# 1. Chunk a master file into 256B chunks + 20-chunk super-chunks
python3 coil_extracted/generate_super_chunks.py

# 2. Upload super-chunks in batches (legacy TASK 005 path)
python3 coil_extracted/task005_batch_uploader.py

# 3. Resume-safe variant (used after the hash-mismatch incident)
python3 coil_extracted/task005_safe_uploader.py

The coil_extracted/MANIFEST.md is the provenance record of TASK 005 — source → chunks → server → reconstruction, all SHA-256 matched, with the failed-run archive alongside it.

---

Relationship to the live site

• splashdown.zo.space/tru is the public chat surface for TRU. Clickable demo with live brain.
• splashdown.zo.space/tru/build is the personal builder.
• splashdown.zo.space/protocol documents the live TRU knowledge graph + scoring engine + Logos framework.
• splashdown.zo.space/ is the landing page.
• This repo is the source of truth for the offline build (TRU/TRU_PORTABLE.html) and the COIL protocol implementation.

If they ever drift, this repo wins for the offline build, and zo.space wins for the live API surface.

The 30 historical builds

TRU/ contains 30 HTML files spanning the project's evolution from a 1KB chat stub to a 10MB reasoning engine. Most of them are obsolete. See TRU/INDEX.md for a guide. The honest summary:

• If you want to use TRU: open TRU_PORTABLE.html
• If you want to understand TRU: read TRU/AGENTS.md + SPEC.md
• If you want to see how TRU grew: skim TRU_v28.html (1MB) → TRU_Phase39.html (the late-stage build, 8MB) → TRU_FINAL.html (6MB consolidated)
• If you want to embed TRU: copy TRU_PORTABLE.html, use the postMessage bridge

The HOLO files (TRU_HOLO_*.html, ~4MB each) are a separate branch with a holographic "face" and voice. They are not maintained.

License & ownership

Personal project, all rights reserved. Operated by joesplashy (Joe) on Zo Computer.