the MAZE

Layer 1 — for the user1What you do with it tracks the code

The MAZE is one page: at the top the memory palace with the conversation field, below it the lab with eight tabs. Everything that is reading (questions, addresses, context, loading, discoveries, report) is free; placing and deleting your own material require a source name with its own key, and the maintenance routes the admin key. Top right one button toggles NL and EN; the vault is deliberately always dark. Separate pages: /ontdekkingen (discoveries), /verslag (weekly report), /doorgang (the Passage), /simulaties (simulations), /handleidingen (manuals), the bank at /bank, and the machine entrance /mcp. The net never claims more than it holds: every answer carries its source, and empty is a result.

paleisThe memory palacethe front door

• A rotatable vault: dragging turns and tilts, a click is an action. Every point of light is inhabited knowledge. Stars and gates take you to an address, knots play the path to that ring as sound, windows open the source and play the route. Your own placed pieces glow gold. Standing somewhere, the caption says ring, layer and name. Entering with #v@d in the link walks you there at once. Bottom right: the forum and "the lab ▾".

gesprekThe conversation fieldask a question, the path appears

• At the top of every answer stands the MAZE.AI line — what the store itself says, before the language model speaks: derived from the store (something lives at the computed address; the inhabitant is a button, marked "(weak)" if it resembles your question little), attested (a person settled this address for this question — name and date shown), or vacancy — nothing lives here. Next to it the neighbour cells: the closest inhabitants around that address, each clickable to its own address, and settle ↗ to the MAZE.AI page. Only below that the text, labelled proposal by the language model — claims nothing, the store decides. The line is always there; the text is a proposal.
• Type a question (NL or EN) and press Enter or Ask; three example buttons get you started. The proposal is two to five sentences, only from what lives on addresses, with literal quotes as cover. If the net does not know the name it says so honestly; if the thing exists in the encyclopedia but not here yet, the Passage holds it as a candidate and the answer says so.
• What else can be there: the address v@d with "hear this route"; artworks with source link; music to play; up to three quotes; up to eight sources (each with ▶ for the melody contour); the grounds per ring; the context (coarser, finer, opposite, neighbours, four-turn, often walked) as clickable chips; related · meaning with "home at depth N" and neighbours with ↗ to the source; bridges · other source kinds — per source kind (mathematics, open problem, art, blog, science, nature, patent, open question, Wikipedia, Passage) the closest members.
• Click a chip, star or gate and the address window opens: address and route, the inhabitants (your own with ✍), the full context, and the button ✍ place your voice here. Every jump from address to address is remembered as a trace.

laden⚡ Loadingthe dynamic side

• Standing somewhere, ⚡ load appears: pick a point of light and the net loads your place against that star through the nilpotent load-and-close operator. Result: a ⚡ b → v@d with signature and number of rounds — landed on inhabited ground (the inhabitants) or on a gap, which then counts for the discovery loop. ⚡ load two neighbours does the same in meaning space.

netkaartThe net mapwith Explore, Encode, Retrieve and Compute

• A radial map of the net: hover or click a winding (+1 above, 0 on, −1 below, occupied address); the readout gives address, number, ring and whether it is occupied. Beside it the count of the living world net.

verkennenExplore

• Click a winding; every place is an address, most are empty and that is a result. At an address: ↑ coarsen, one button per trit move (+, 0, −), opposite, → A and → B (for Compute), and at an occupied place clear content. The route is also given in words.

coderenEncodebuild an address yourself

• Title, kind (concept, myth, measurement, article, example), content, Start encoding. Per ring you answer "is this above, on or below?" or stop with "deep enough". Then the gate: the same text a second time. If it closes, "admitted at address N"; as a prefix, admitted as a coarser piece; otherwise refused. On a collision: place at N or at the opposite −N.

ophalenRetrieve

• Enter trits (+---+) or number@depth and Retrieve. Occupied: "direct hit". Empty: the answer comes from a coarser ring, with the deviation bound (3^d−1)/2 stated honestly.

rekenenCompute and compose

• Two addresses A and B: distance, shared prefix, opposite yes or no. Below it composing: two melodies from the net and an operation (sum, inversion, retrograde, four-turn); Compose and play places the result in the net (source muziek:maze) and plays it at once.

herschrijf-labRewrite lab

• Four classical rewrites (opposite, mirror, shift, successor) exhaustively checked at depth 5: depth preserved, bijective, closes with truncation, involution, fixed points. Plus the quaternion turn, the Cayley–Dickson ladder ℂ → ℍ → 𝕆, and "the 64" — Rowlands' prediction measured.

netNetthe state of the net

• Number of windings and pieces, the last loop (processed, placed, skipped, error) and the unshared list as work stock. Without a database: prototype mode.

boomTreethe 19 layers of existence

• Nineteen rings, three columns per layer: what the layer is, what is derived (range ±(3ⁿ−1)/2, which algebra closes), what was found (windings, pieces, source kinds). Empty layers are called work stock; where individual and collective coincide it is a ξ point. Names are clickable questions.

zelf-plaatsenPlace yourselfyour voice, with a receipt

• Name of the piece, your own words, optionally an https link (the receipt), a source name and a key of at least eight characters. Place returns "placed at address v@d", the grounds and the context. Delete my source removes everything under that source name, after confirmation. If the source name already exists with another key, the net refuses.

/ontdekkingenWhat the MAZE discovers

• New today, this week, total, and the percentage addressed by meaning. The questions the net asked itself (with address and candidate sources), the most-hit empty places, and the gaps between related things. Read-only.

/verslagThe weekly reportalso as RSS at /verslag.xml

• Self-written, in Dutch: growth per source, new open questions, strongest traces, usage, balance of habitation, and the meaning space.

/doorgangThe Passageown manual

• The layers with their times, what waits (with the two gates as trits), what closed (with return and address), what expired, what did not become a candidate, and the build tests. Read-only; see the manual of the Passage.

/valis — the self and the Other

VALIS as an encounter, not as physics. You pick one of the four shapes that recur in reports across cultures and millennia — the small technical figure, the guide, the mantis, the formless light — and see what it is and what it mirrors. Then the course of an encounter in five steps, what gets said, the shadow (The Black Iron Prison, with Jung) and three explanatory frames of which none wins. Folded out below: the material, all 39 posts mentioning VALIS, counted in the posts themselves. Also as JSON at /api/valis.

/library — the MAZE Library: all books of constable.blog

An overview of all books by J. Konstapel on constable.blog, newest first. Per book: the title (linking to the blog post when that post is about the book), the subtitle from the first page, date, number of pages and language, an introduction — the opening of the book itself, verbatim and shortened — the blog's subjects as buttons that filter, and the pdf. Search in title and introduction, or filter by year, subject and language; a direct link to one book is /library#the-title-as-slug. The books are the works Konstapel himself marked as books (list in maze/library/kandidaten.md), each once in its newest version. The data are at /library/boeken.json; they are rebuilt with maze/library/bouw.py.

/nieuw — the new MAZE: the derived library

A spiral of nodes derived from zero: the first distinction, complexification, the quaternions, the four parameters, the 64 units of the Dirac algebra, the fermion and its symmetries, the whole fermion spectrum with the quarks in three colours, and further the hydrogen atom (checked against measured values, with the measurement receipt), the atom with its shells and noble gases, all 118 elements (configuration, period, block and Larson's rotation a-b-c: a noble gas plus or minus c), bonding, derived from the shell and Pauli (unpaired electrons, a bond as a shared pair, all structures that follow as the potential, and per structure whether it exists according to Wolfram|Alpha and PubChem — with the edge the derivation does not yet reach: charge transfer, stable radicals, ring strain; Larson's rule stands beside it as a compared source), and above it the layers up to the return — the code, the protein, the cell, the body, the human, the group, language, science, organisation, state, civilisation, biosphere, galaxy and cosmos, the count and the return to zero — each with a measurement receipt and the check whether the factor of closure (≈ 3) holds there, the four DNA bases as the same Klein four-group (marked as a correspondence), and finally Larson's ladder of three, derived from our own hydrogen, with on it the atom, the human (position 15.93), a day and a life, the galactic threshold and the stars, the closure of windows and rings from the trit, black holes (the horizon, the shift of α from white dwarf to horizon, Sgr A* and M87* on the ladder, the mass gap), the knot (three closing into one, what a knot carries, the depth of a life, the bronze sequence, the tempo between levels) and society as a knot of people (marked as a correspondence). Every node is produced by one operation on earlier nodes and carries an exact check (✓ in the panel on the right); the name and the definition — the literal first sentence from Wikipedia with its revision — come only afterwards. Click a node to see what it comes from and what it leads to; search with the search box (for example "quark"); a direct link to one node is /nieuw#up_quark. The raw data are at /nieuw/bibliotheek.json and /nieuw/namen.json, the rules (hashed before the first run) at /nieuw/regels. Under each node stands "In the old MAZE": the same name as a resident of the old MAZE, with a link to its meaning path (/#pad2=… opens that path in the old MAZE) and its old address — a coupling via the title, not a derivation (/nieuw/koppeling.json). Below that stands "In the filling machine": where the same key lies on the map of the old MAZE (rings 0–8) — the beginning on ring 0, the trit on ring 1, the elements on ring 5 at their atomic number, the codons on ring 6 — with a link to that address (/nieuw/koppeling-vulmachine.json). Some nodes also show "Related in the old MAZE (statistical)": neighbours from the meaning space of the old MAZE, shown only when Wikipedia confirms them with a link to the anchor (/nieuw/koppeling-buurt.json). The old MAZE itself is not changed.

/theorie-generatorthe theory generatorone field every night

Here the machine derives fields of science from the ladder of three by itself, the way Hans did by hand for climate on 3 October. There is no input box: each night it takes the next field from its own list, has a language model name that field's characteristic lengths or durations, and holds every proposal against the source — the number must appear in so many words in an English Wikipedia article, and the sentence it appears in goes into the table as the receipt. What is not covered is dropped, with the reason stated. What is covered goes onto the ladder (each rung is three times the previous one; feet 4.56e-08 m and 1.52e-16 s); where three layers sit next to each other, the theory fixes the third from the other two — that is the part that genuinely generates. The agenda at the top shows what is done and whose turn it is. Also as JSON at /api/theorie-generator.

/theorie-ketenThe chain under the theoryreads live from the repo

The Vacuum.Net derivation chain as data: twelve links each with one status (assumed · conditionally proven · correspondence · measured · open), the candidate spaces of the open links with their measurements, the fit and holdout anchors, the canon register and the audit. The repository files are the source; the hashed plans and outcomes live in /boek. Also as JSON at /api/theorie-keten.

/simulatiesSimulationsseven pages, Dutch

• The thread, three states, the comma, the plate, loading and discharge, the fishing net, and the machine (current from the net, with the self-tuning loop and its own manual at /simulaties/machine-handleiding-en) — each with two windows on one simulation (the books left, the net right) and one set of sliders.

/handleidingenThe manuals hub

• Seven manuals in four layers, NL and EN, with the app button at the top of every manual; the code takes precedence over the text.

/bankThe MAZE-Bankown manual

• The book of the circle: who helped whom with what. See the manual of the Bank.

/conflictConflict Weatherown manual

• Four gauges for the theatre Europe–Russia, each against the frozen 2000–2013 base, with the blind backtest. See the manual of Conflict Weather.

/generatorThe Patent Generatorown manual

• Six steps from patent class to innovation address; the patents of each class and the candidates become inhabitants of the net (kinds octrooi and vinding). See the manual of the Patent Generator.

/transformerThe Maze Transformerown manual

• The map of power laws (y ∝ xᵉ) from 150 arXiv papers on galaxies, with the paths and the gap list; and "have it examined": give an arXiv ID and see where that paper joins the map. See the manual of the Maze Transformer.

/humanmaze.human — the circle of four worldspanels human-start, human-kwadranten, human-spoor

• What it is. Paths of Change (McWhinney) as a page: four quadrants — yellow imagining (ask a question), red perceiving and doing (look around the answer, or add a piece yourself), green valuing (does this belong to my question — your judgement, not the ledger), blue closing (settle, which does go into the ledger) — with the crossing in the middle: each next question is more general (up) or more specific (down), measured by the width of the neighbourhood it lands in, which changes the ring of your path.
• What you do. "Begin a path" (name optional; a key is needed to close or to add), then walk the circle. On the right is your trace: the colours you touched, which are missing, how often you passed the centre and which ring you are on. A path closes when all four worlds are touched and it ends with an act that changes the net (settling or adding).
• Why. A measurement on 22-9 over all existing traces showed: 0 of 23 paths closed, 22 of 23 had one colour — the system did not offer the circle. This page offers it. Questions go through the same proven loop as /ai; there is no second output path.

/aiMAZE.AIthe provable answer loop, own manual

• What it is. An answer machine that asserts one thing only: "this stands at this address in the store, along this derivation". Every output is of one of four kinds — derived, attested, vacancy, proposal — and carries its address. Those rules are not policy but theorems, machine-checked in Lean 4 and bound to the running code (30,572 addresses compared, 0 differences). The language model may only propose.
• What you do on the page. Ask → you see the output with kind, address, inhabitant and neighbour cells, and the proposal separately. With settle you record, as a registered user (via swarp.nl) or with the admin key, that this address answers this question: it becomes a row in the ledger — append-only, hash-chained, signed — and next time the output is attested with your name and date. The ledger and its chain check are at the bottom of the page.
• Full description, theorems, API and limits: manual of MAZE.AI; the English whitepaper: /ai/whitepaper (PDF).

/mcpThe machine entrancefor agents

• Eleven tools: vraag, zoek, adres, samenhang, open_vragen, laad, stem (the only writing one, with source and key), verslag, betekenis, brug, laad2. Rules: never invent content for an address, empty is empty, cite addresses as v@d.

Layer 2 — for the thinker2The idea & the five rules enduring

The MAZE is not a search engine and not a database. It is a net in which every statement gets an address computed from its own content — and in which similar things therefore come to live near one another of their own accord.

Imagine a vast card index in which a card's place is chosen not by you but by what is written on it. Two cards about the same thing end up together — not because someone filed them together, but because their content yields the same address. The place exists before the inhabitant: every possible fact already has a computable address, even when nothing is there yet.

At the core are five rules that are never broken. They make the net trustworthy and re-verifiable, and they outlive every rebuild:

1. 1The address is computed from the content, never from the form of the description. Saying the same thing twice yields the same address twice.
2. 2No shortening. No cap, timeout or "optimisation" may cut the chain short. Before every bulk load, a spread test: a coder that too often yields the same address is broken.
3. 3One gate. A question and the material pass through exactly the same entrance. What a question addresses, a fact addresses the same way.
4. 4Counters steer nothing. How often something has been visited or consulted never changes the address or what is retrieved.
5. 5An address is never rewritten. Deepening extends the route; the prefix stays. What once lives somewhere stays there.

Because the address follows from the content, the net is re-verifiable: anyone can compute the address of a statement themselves; there is no authority deciding where something belongs. And so the MAZE never invents content, never shortens the chain, never lets counters steer the address, and rewrites nothing — these are not limitations but the guarantees themselves.

Two generations — and why nearness must be relatedness

"From the content" is the rule; which content the coder reads is the question the net had to learn for itself. The first generation read the word surface (letters, words). That spread, but it did not make nearness into relatedness: two statements about the same thing did not come to live side by side, and everything that rests on that — reasoning from the space, gaps that mean something, paths that carry meaning — stayed silent. The second generation reads the meaning of the content and orders the rings from coarse to fine along the directions in which the content differs most; after every split, the narrowed field is split again along its own principal direction (coarse narrows, fine distinguishes — Pāṇini's ordering). So a shared prefix becomes a shared meaning, and an empty region between two related things a real open question.

The two generations stand side by side; rule 5 holds: nothing is rewritten. The first carries the crown and the traces that were already there; the second carries relatedness. A later generation that reads more content (not only the title but the text) will stand beside them the same way — never as a silent shift.

Layer 3 — for the builder3How it works — the name bridge, the crown & API

The name bridge — how a question finds the right book enduring

A question often names a thing that already lives in the net ("what is democracy?"). The address of that thing is then the address of the answer. The name bridge recognises such a name — via a language bridge where needed (democratie → Democracy) — and goes to that subject's home. This is not a second entrance for material (rule 3 holds): it is navigation for a question. There the MAZE reads the source and answers with literal, verified quotes; if the question names nothing the net knows, it says so honestly. Since 13-9 the net learns from such a question: if the named thing exists in the encyclopedia but not yet in the net ("Cotterill" → Rodney Cotterill), the MAZE reads the article for the answer right away and hands it to the Passage as a candidate — after the closing time and a return through the gates it gets an address. Name and disambiguation pages do not count as things, and the language bridge also applies in the test between the two gates ("orkaan" → Atlantic hurricane).

The meaning gate — generation 2 tracks the code

Material and question pass through the same gate: the text of a piece (its name, and where the net holds it the statement, lead sentence or context) becomes a meaning vector and is projected along frozen axes into 24 trits — first the largest directions of difference across the whole net, then per narrowed field its own direction (an adaptive tree of 2,321 nodes to depth 9). Axes and tree were computed once and are fixed since, like a calibrated yardstick: the same content always yields the same address. Measured on the hardest corpus (formal theorems): from 14 addresses for 5,109 theorems to 4,763; two theorems from the same module demonstrably share a longer prefix (AUC 0.77); encyclopedia articles on their title 0.66. Since 13 September the first paragraph of 3 million articles is included (DBpedia): it sharpens the ranking within a neighbourhood, but barely the tree itself (measured 0.67 with text) — the hierarchy lives in the coarse axes, the fine relatedness in the vector.

A question comes home in the deepest inhabited neighbourhood of its path (a prefix with enough inhabitants); within that neighbourhood, real meaning similarity (cosine) ranks who stands closest to the question — the prefix narrows, the similarity distinguishes. Because a hard tree is brittle at its boundaries, the question also walks the neighbouring paths where it stood closest to a boundary (multi-probe), and the English concepts of a Dutch question walk along as their own path — only the question does this; the material stays where it is. And the two gates test each other: if the name bridge names something that lies far from the question in meaning (a "Hurricane" that is an aircraft), meaning wins and the net honestly says it found nothing.

The net also thinks here by itself: every night it loads related pairs against each other. In the meaning space, loading is superposition — the two meanings are added and coded through the same gate, so the sum lands between the two (the trit addition of the first generation is still reported as a signature, but in an adaptive tree it does not decide the landing). If the sum lands on inhabited ground, that is a trace; if it lands on empty ground between related things, that gap becomes — after repeated hits — an open question, "what connects A and B?", shown on the discoveries. The opposite, too, is a meaning operation here: not the inverted trits, but the inverted vector.

The crown — the question side, everywhere tracks the code

The full store of addresses is large and lives on a disk. To let the MAZE be queried anywhere, it carries a crown: the top, well-trodden rings of the net, small enough to travel and read-only. You can ask questions of it; placing is only possible in the full store. This is how the question side is always open, even where the whole disk cannot come along.

The API tracks the code

The MAZE also exists to be queried by programs and agents. Every answer carries its receipt; you cite addresses as v@d and link them as https://maze.swarp.nl/#v@d.

The stack — EPO (18 Sept 2026). Next to the map per technology field, all EP inventions are now in the net (source octrooi:epo, 4.58 million inhabitants): the weekly open dumps of EPO Linked open EP data (bron-epo.mjs reads and merges, bron-epo-laad.mjs places resumably in portions with the spread test). Placement rule: every invention gets its meaning address (generation 2); as generation-1 address the field signature where it exists, otherwise the meaning path, marked in gronden.adres. Receipt per inhabitant: Espacenet; the linked-data URI in gronden.uri.

Layer 4 — for the connector4Links & further tracks the code

• the netmaze.swarp.nl — ask a question.
• live discoverythe discoveries — what the net asked itself last night.
• carriesThe MAZE-Bank, Financial Weather, Living Environment and Support rest on this.
• originconstable.blog — the self-addressing ternary knowledge net (18 Aug 2026).
• backall manuals.