Ļéàŕñ ķàþî › Explore the engine

Bundle anatomy

One content bundle, read part by part, then round-tripped through the engine.

The content bundle is the interchange document of the toolchain: one deterministic JSON file that carries a document's blocks as runs, its editions per language, and the provenance of every string, so extraction, translation, checking and write-back can be separate steps. The first chapters read one realistic bundle part by part; the last ones edit a bundle and watch the engine canonicalize, preview and validate it.

1. The envelopeA bundle starts with what produced it and for which project. Select a line on the left or a term on the right to see what that part of the document is for.
2. The documentOne source file, with its format and its path. A bundle may carry several.
3. A block and its keyThe unit everything else hangs on: a stable key, and the content as editions.
4. EditionsThe source language and each translation are peers on the block, keyed by locale. One is already Norwegian; the plural still awaits a translation.
5. Runs: text and codesAn edition's content is a sequence of runs: text, paired codes for inline markup, placeholders for variables. The markup never sits inside the text.
6. A pluralA plural is one run whose branches each hold their own runs, so a translation cannot drop a category unnoticed.
7. ProvenanceWhere each string came from and when: the fields a reviewer and a gate read.
8. Round-trip through the engineNow the real engine: edit the bundle on the left and the canonical Go implementation, compiled to WebAssembly, parses it, canonicalizes the bytes, renders each block's preview, validates the run structure and resolves the companion overlay anchor by anchor.
9. What validation refusesA bundle with an unbalanced pair: the engine names the block, the run and the rule it broke. Fix it in the editor and the preview returns.