The picture exists only in the whole.
Mosaix is a file-level format for vaults of atomic, self-describing notes. Machines retrieve one note at a time. People read many notes as one document.
Nothing is silently lost.
Every knowledge base has this: the last edit wins, and nobody recorded that there was a disagreement. Mosaix records it at the file level, and keeps every version where it was.
The same knowledge, once as prose in a document and once as Mosaix tiles. The body of each tile is the sentence you already wrote. The keys are generated by enrichment and reviewed by a person.
Nothing in the body changes. The keys sit above it, in plain YAML. Hover a key to find it in the note.
summaryOne declarative sentence, 120–240 characters.keywordsSix to eight terms: synonyms, spoken phrasings, questions.entitiesNamed things, typed.relationsTyped links between entities. The graph lives in the note.revHash of the body when metadata was computed. Mismatch means stale.A note of type document lists the tiles it is made of, in reading order. Hover a paragraph to see its tile. Nothing is copied.
64 tiles · 5 in fragments, reading order · one still to confirm
1The European PPE market is consolidating: three acquisitions in 2025 moved 18% of distribution under two groups.← PPE consolidation 2025 · ✅ sourced
2Portwest sells in 130+ countries and undercuts distributors with an own-brand line; it is the reference competitor for price.← Portwest — player card · ✅ sourced
3Whether Portwest opened an Albanian plant in 2024 is disputed between two sources; the argument does not depend on it.← Open question #33 · ⚠ to confirm
4A+A Düsseldorf in October is the single most relevant fair; exhibitor lists confirm both direct competitors will attend.← PPE trade fairs, Europe 2026 · ✅ sourced
5Recommendation: enter through safety footwear, where Turkish manufacturing has a documented cost advantage of 22–30%.← Strategic scenarios · ✅ sourced
A vault that obeys them can call itself Mosaix 1.0 conformant. Conformance is a property of the files, not of any tool.
A contradiction between notes goes in the open-questions ledger with both versions, dates and consequence. Nobody picks a winner silently.
A note that is no longer valid is marked and left in place, because other notes link to it. Deletion is for mistakes only.
Automated writes go to a branch or a review queue. A person merges. The revision hash shows whether the proposal was made against the current body.
One note answers one question.
Every note carries the core keys.
No orphans, no broken links.
Every tag lives in the meta note.
Read together? Composed, never copied.
When each tile carries its own contract, the size of the model stops being the bottleneck.
tests passed by a two-billion-parameter model, generating a 31-unit package one tile at a time. Qwen 3.5 at 9B: 40 of 40.
Results from the code-generation study that produced the format. Measurements on knowledge vaults are in progress and will be published here. How we measured →
A planner hands each agent one tile and its direct dependencies: about six hundred tokens, nothing else. No agent reads the whole vault; there is no shared memory to keep in sync. So each agent can run on the smallest model that passes its tile, local or cloud, general or vertical, all in parallel.
Because the cluster is the unit of work, the model is a per-agent choice: a 2B model for the tiles it passes, a vertical model where the domain needs it, a cloud model only where nothing smaller will do. Swap one, and the others don't notice. This is the direct evolution of the system: work verticalised across different models, each on its own cluster of knowledge.
Obsidian is the reference host. The format needs none.
One Python file, standard library. It reports every error and warning against §10, note by note, and exits 0 when the vault is conformant. On the right: the example vault, then a real marketing vault before and after two fixes.
Download audit_reference.pyThe fourth tile of the mark is outlined and empty: it stands for what is decided but not built. These are the open tiles of the format itself. Each is recorded in the example vault's ledger with a status, like any other open question.
A stable id so links survive renames; a question key for the one question a note answers; an optional closed relation vocabulary; an entity registry with aliases; origin and as_of. Every 1.0 vault stays conformant.
in discussion · proposals in the ledgerA GitHub Action now wraps the checker: eight lines of YAML give you conformance checks on every push and PR comments. Next: pip install mosaix-check and a --fix mode for the mechanical part.
action shipped · pip install and --fix not builtThe numbers in 07 come from our own runs. The next step is the method and the fixtures in the open, so anyone can rerun one agent, one cluster, on the model they have.
method being written upLogseq and Foam read the substrate; a verified profile for each, like §9, says exactly what resolves and what does not.
to confirmThe specification vault as a zip you can open in any editor, and a badge for vaults that pass the checker. Plus a second vault: a fictional bakery, ordinary knowledge, 26 notes. All shipped with 1.0.0; the badge is self-declared, the checker report is the evidence.
shippedA DOI per tagged release so the spec can be cited in a stable way. English is normative, Italian is here; other languages arrive as pull requests.
on requestSend an empty email. You get one line when 1.1 ships and one when the checker package is out. Nothing else.
