Contents
Where this sits
The bridges join Owl Academy’s Engram Mind Eye and Biomesh Mind’s Eye 3D to the two pages here.
What crosses
| Format | From | In | Out | Where |
|---|---|---|---|---|
Saved session (engram_mind_eye_v1) | Engram Mind Eye’s browser storage | verified, with its conversation | byte for byte as Owl Academy saves it | 2D page |
v1 chain (engram_chain_N…) | Engram Mind Eye’s export | verified | byte for byte (Phase 4) | 2D page |
v1 text crystal, 72 or 720 (engram_crystal_S…) | Engram Mind Eye’s export | verified; speakers where the file has them | byte for byte (Phase 4) | 2D page |
| Biochain record | biomesh.js growBiochain | two verdicts, Owl-compatible and strict; its text recreated losslessly | — | 2D page |
Biochain package (biochain-package/1, draft; a Hyperbolic Lexicon package) | a grower that signs: the Hyperbolic Lexicon, Owl Academy | the record’s two verdicts, its kind, where it says it came from, its signer | biochain-package/1 for Owl Academy | 2D page |
| Engram stream (16 hex a word) | a biochain’s engramStream | by its grids | — | 2D page |
| LATTICE-SEED/1 | Biomesh Mind’s Eye 3D | verified (Phase 5) | — | 3D page |
| ENVIRONMENT/1 | Biomesh Mind’s Eye 3D | verified; its pump drives the breath | — | 3D page |
v2 (engram_mind_eye_v2_…), and a backup (engram_mind_eye_backup_…, the same format) | this system | verified | everything exact (Phase 4) | 2D page |
Paste or choose a file in the 2D page’s Owl Academy, in and out panel and press Read and check. The panel says what the file is and what each check found; Load as this session replaces the dialogue with it. Lattice seeds and environments go to the 3D page’s seed panel. The two pages share the loaded session.
Back up this session, under the dialogue, downloads the session as a v2 file. The session itself lives in this browser’s storage, which every page of this site shares and any of them can clear; reading the backup here and loading it brings the session back, checked packet by packet.
Back to Owl Academy
Owl Academy’s Engram Mind Eye has no import button. It keeps its session in its own browser storage, under engram_mind_eye_v1, and restores it every time the page opens. So the way back is to hand it a session in exactly that form.
- Export. Owl Academy session downloads
engram_mind_eye_v1.json: the manifold, the codex parity, every packet with its grid and triangulation, and the conversation, serialized as the page’s ownsaveEngramdoes. - Load it there. Open Owl Academy’s Engram Mind Eye, open its console, and run the loader that Copy the loader puts on your clipboard:
localStorage.setItem('engram_mind_eye_v1', JSON.stringify(…)); location.reload(); - STRIX resumes. The page restores the chain, types its greeting (“The engram persists. 97 tokens crystallized across 0 epochs. We continue.”), logs it, and carries on from the last codex parity.
How we know it works without a browser on Owl Academy. The fixture runs Owl Academy’s own saveEngram, restoreEngram, greeting and reply code. It records the session the page saves after one exchange, and the session after five exchanges by length and SHA-256. For the one-exchange session it also restores it, types the greeting, takes one more exchange, and records every new packet and the session saved after that. This system’s export of the same conversations is byte for byte the same. Its own continuation of the imported session gives the same 49 packets, the same reply and the same final parity, and saves the same bytes Owl Academy saves.
Coming in
Every importer rebuilds what it reads and compares it with the file. It loads the result as a session only after saying what matched.
- A saved session. Its conversation is replayed here, and every packet’s token, body, header, footer, grid, triangulation and chiral key must come out as in the file, along with the final codex parity. If the conversation does not rebuild the packets (an edited conversation, say), the packets’ own tokens are tried. Either way the first packet that differs is named. Replies Owl Academy’s BERT once wrote are just text here: they become STRIX turns with no concept attached.
- A v1 chain. Each packet is rebuilt from its token and compared field by field, then the chain is exported again and compared with the file byte for byte. Speakers come from the packets, and runs of one speaker become turns.
- A v1 text crystal. The tokens are read in slot order. Every slot’s XOR crystal and chiral key, the master crystal on its manifold anchor and the header are rebuilt, and the file is reproduced byte for byte. In 720 sections a slot holds at most one word of a short session, so every speaker is known. In 72 sections a slot can hold words of both speakers, and the file keeps only the counts: those words are marked unknown. Their packets, words, registers and binding do not depend on who said them, and are exact.
- A biochain. Owl Academy’s
verifyIntegrity, step for step: each frame’s parity, the text recreated losslessly by its order-2 rank coder, every leaf hash, the Merkle root, the chiral weave and the engram layer. The reasons are reported in Owl Academy’s own words. The recreated text then comes in as one turn of its words, tokenized asbiomesh.jstokenizes them; this system’s engram stream of that text must equal the record’s. That is the Owl-compatible verdict; the page also gives the strict one (section 5). - A biochain package. A
biochain-package/1(the draft of RFC 07: a kind, the record, what was signed and the attestation) or a Hyperbolic Lexicon package (the record, its LPREP/1 string, the attestation and the corpus manifest). The record gets both verdicts, and the panel shows the package’s claims beside them (section 5). Pass it on writes abiochain-package/1for Owl Academy’s package import, only when the record passes the strict check and what was signed is this record’s. A Tier-P LPREP/1 is not passed on yet: the package format has no field for its salt. - An engram stream alone. Sixteen hex digits a word, with no words: the packets come in by their grids. The chain, words and registers are exact, since none of them needs the word. The count and mean J are checked against the record’s. Each packet is labelled with a word from STRIX’s library whose key it equals, where there is one. engram/1 keeps only letter parity, so that label is a word with the same key, not necessarily the word said.
- ENVIRONMENT/1 (3D page). Its hash is recomputed as the Biomesh page computes it. Its boundary seed is checked as a LATTICE-SEED/1, and its codex must pass Owl Academy’s ABI gate (parity, GEAR first, PRIME entries, HALT last). Its pump then drives the breath of the view: frames, breath and torsion. Its frontier nodes get a teal ring.
- v2, this system’s own export: its turns are replayed, and every packet, address, memory word’s root and link, and the chain quaternion must come out as recorded.
Two verdicts and where a record came from
A biochain record is checked twice, by two different questions, and the page shows both.
- Owl-compatible. Owl Academy’s own
verifyIntegrity, step for step, and this system’s engram layer beside it. It checks that the record agrees with itself: each packet’s parity bit holds, its residuals decode, and the leaves, root, chiral weave and engram layer it carries match the text they recreate; this system’s engram stream, count and mean J of that text must match too. Whether the record is what its bytes grow is the strict verdict’s question. - Strict. Owl Academy’s
verifyIntegrityStrict(RFC 07, section 12), pinned here asbiochain_v2.jsand run with this system’s SHA-256 fromorbital_core.js. It asks whether the record is exactly whatgrowBiochaingrows from its bytes, and names the first check that fails, in this order: parity (the stream’s form, each packet’s parity), canonical (the 720-byte cut, each residual re-encoded byte for byte), crystal (each packet is the chunk’s), leaves (all of them and the root, never optional), weaves (both weaves, the segment cuts and the chain id) and derived (well-formed UTF-8, the engram layer and the size fields).
The labels are the overhaul’s (decision D15): strict ok; legacy for a record without a shdccp/2 stream; failed at <check>; and self-consistent only, failed at <check> when Owl Academy’s verifyIntegrity steps pass and the strict check does not. The labels are Owl Academy’s, so a record reads the same there. The Owl-compatible verdict here also compares this system’s engram count and mean J, so a record whose engram numbers differ from its text reads “Owl-compatible failed” beside “self-consistent only, failed at derived”, and the line that failed is named under it. A line above the checks puts the two together, for example “Owl-compatible ok; strict failed at crystal” for a record whose packets were written with BioChain-AI’s kernel rule (a crystal byte 0x80 written as 0x81). Nothing is refused for a strict failure: the label says what the record is, and it can still be loaded. Owl Academy’s engram layer and this system’s are both computed for the text, each word’s key once, and compared on its own line.
Where a record says it came from. A bare record says nothing about who grew it. A package carries claims, and the panel checks each one it can and says which it cannot:
- its kind, against Owl Academy’s registry of kinds;
- what was signed: for GROWN/1, the commitment rebuilt from the record (chain id, root, both weaves, size); for LPREP/1, that the string has its registered shape and names this record’s Merkle root, and in Tier S its chain id; a Tier-P string withholds the chain id behind a salted root, which is recomputed with the package’s salt when the package carries one (the Hyperbolic Lexicon’s does). The string’s other fields are the Lexicon’s own verifier’s to recompute;
- that the attestation’s content hash is the SHA-256 of what was signed;
- the signer, with Web Crypto: the fingerprint of the public key the attestation carries must be its keyId (or an Owl seal’s sealId), and an ATTEST/1 signature must verify with that key.
A key that signs is not thereby a key that may sign. Whether it was registered to anyone, revoked or retired needs the key registry, which this page does not have; it says so on its own line.
Pinned from Owl Academy’s code
reference/golden/make_bridges_v1.cjs reads three Owl Academy files and runs their code, unchanged, on fixed inputs: biomesh.js, the Engram Mind Eye and the Biomesh Mind’s Eye 3D.
biochain_v1.jsisbiomesh.js’s synchronous code, verbatim: the SHD-CCP stream codec, the lossless rank coder, the chiral weave, the token engram layer and the codex parser.bridges_v1.jsonrecords what that code gives. The session is saved, restored and continued. Five biochains are grown and verified: three texts, from 14 bytes to 2,728 bytes in four chunks with non-ASCII characters, plus two altered copies. Three environments are built and hashed, one altered after hashing, and a good codex and a broken one are parsed.growBiochainandverifyIntegrityhash with Web Crypto. The fixture runs them with SHA-256 over UTF-8 from Node, asseal-crypto.jsdefines it. The engine repeatsverifyIntegritywith the orbital core’s synchronous SHA-256, and must give Owl Academy’s verdict word for word.--checkrecomputes both files from an Owl Academy checkout and says whether they still match, as for the golden corpus, STRIX’s library and the lattice seed.- Version 2 (
reference/golden/make_bridges_v2.cjs <Owl Academy commit>) reads Owl Academy’s Firebase-free core,scripts/biomesh-core.js, at one commit.biochain_v2.jsis its synchronous code, verbatim, under its own MIT licence (NOTICE beside it): v1’s codec and engram layer with each letter’s grid built once,qconjandchainFrames, and the strict verifier.bridges_v2.jsonrecords Owl Academy’s strict verdicts and labels on v1’s biochains, on altered copies and on RFC 07’s tamper vectors.VENDOR.jsonlists every file copied in, by SHA-256, with RFC 07’s contract vectors (public domain) underreference/golden/vendor/. The v1 files stay as they were.
How it is tested
Check (tests/bridges.cjs, 34/34) | Result |
|---|---|
| The session export | Byte for byte Owl Academy’s, after one exchange (41,056 bytes) and after five (100,554 bytes) |
| Owl Academy’s session in, and on | Verified; the same memory as grown here; Owl Academy’s greeting; 49 more packets, the reply and the parity as Owl Academy continues; the session after that saved byte for byte; an altered packet named |
| v1 chain and crystals in | Verified and reproduced byte for byte; 720 sections with every speaker; 72 sections with 25 of 237 speakers unknown and the memory the same; an altered slot caught |
| Biochains | Owl Academy’s verdict word for word on all five; the three good ones recreated exactly, their words’ packets equal to the engram stream |
| An engram stream alone | The same chain as the words it came from; a wrong mean J caught; a bare hex stream read |
| Environments | Owl Academy’s hash and verdict on all three; the codex through the ABI gate, and the broken one refused with Owl Academy’s message |
| v2, the store, the detector | v2 verified and the same memory; a stored session replays with every STRIX reply recognised; every format named, anything else refused |
Strict and the checked import (tests/bridges-v2.cjs) | Owl Academy’s strict verdict on every input of bridges_v2.json, with this system’s SHA-256 and with Owl’s; every RFC 07 tamper vector at its expected check and every honest one passing; every record vector regrown and passing; both engram implementations on every key vector; the Owl-compatible fields exactly importBiochain’s; each word’s key once; packages written, read back and their signer checked; LPREP/1 strings written by the Hyperbolic Lexicon, in both tiers, bound to their record and not to another |
In Chromium at 1440 and 390 px, the page checks pass. The Owl session download equals the engine’s, and the loader is offered when the clipboard is blocked. A saved session, a biochain and an engram stream each read, verify, load and survive a reload, and the 3D page shows the same session. An environment loads with its checks, its pump drives the breath, and an altered environment is caught. A file that is not one of these is refused with a reason. The earlier suites still pass: 829 parity lines, 27 behaviour checks, the 2D engine’s 26 and the 3D engine’s 19.
What does not cross, and what the checks do not prove
- No network. Published biochains live in Owl Academy’s Firestore. A record comes in as the JSON object
growBiochainreturns and Firestore stores. Seals, certification, transfers and the familiar’s binding stay in Owl Academy, outside this system’s core, as the plan set out. - Epochs. Owl Academy’s session has a
biochainlist of epochs that its page never grows; it is exported empty, and its greeting says “0 epochs”. - Words a stream never had. A session that came in as a bare engram stream has labels where the words would be. Its packets and memory are exact, but its v1 exports carry the labels, and those labels cannot rebuild it; importing such an export says so.
- Who said what, in 72 sections. Marked unknown, as above.
- A matching ENVIRONMENT/1 hash is not a signature. The hash is Owl Academy’s
fold32: 32 bits of a checksum over the object’s JSON. It catches a file damaged by accident. Anyone who changes an environment on purpose can compute the new hash, so a match says nothing about who made the file. The same holds for a v1 crystal’s parity and a session’s codex parity: they detect accidents, not changes made to pass. - The Owl-compatible verdict is self-consistency. As section 5 says, a record can agree with itself and still not be what its bytes grow. Only the strict verdict says that, and only a verified signature by a registered key says who grew it.
- The pins run Owl Academy’s code.
make_*_v1.cjs,make_bridges_v2.cjsand their--checktake functions from an Owl Academy checkout by name and run them, in a separate JavaScript context without Node’sprocessorrequire. That context keeps the checkout’s code away from the file system by accident, not by design: it is not a security boundary. Run the pins only against checkouts you trust, as the nightly job does with Owl Academy’s own repository.