restructure — crystallizing cyb · cyber · cyberia

a plan first, movements second. nothing in this document moves a file; every section is a contract for one commit series, link-fixes included, so the site is never broken in between. every page named below is a live link — click through and judge it. the three ledgers carry a verdict for every page: stays / promotes / merges / moves / folds / extracts / dies — with the destination and the reason. zero pages undecided.

original census: 501 pages (238 cyber · 83 cyb · 180 cyberia). the cyber table is the work that remains.

the rule

membership is decided by one question — who is the subject of this page? — so the split is idempotent: run the rule twice, nothing moves the second time.

corollary: cyber is not soft3. soft3 owns mechanisms; cyber owns what must be true regardless of mechanism. a page explaining how something is computed belongs to the component that computes it; a page stating what must hold belongs to cyber.

0 · the ground — what all three stand on

proposal. the plan above three subjects is incomplete without its floor: cyb, cyber and cyberia are the trinity standing on two shared dependencies — soft3 (the stack: the loop, the guarantees, the attractor; every "component matter" row in the rule resolves here) and cybics/crystal (the world's knowledge; every "world at large" row resolves here). the dependency runs one way: soft3 does not know the robot, the narrative, or the nation; the trinity cannot run a page without the stack. crystallizing the three subjects and crystallizing soft3 are one program — so the soft3 crystallization lives here, married in whole:

the boundary and the core

soft3 crystallizes into 7 = 4 + 2 + 1: four motions, two guarantees, one attractor — and every verb is a component's own verb from status. no invented words: earlier drafts said say, act, observe, focus — but the registry already had link, render, measure, converge. drawn at soft3.org/scheme, parts at soft3.org/chart.

The boundary rule: a component is stack iff the loop cannot run, the medium cannot hold, or the mind cannot converge without it. Everything else is enrichment (a richer way to hold a seat) or a product (consumes the loop entire).

the loop — four motions, all live

the smallest circle a mind can draw, and every station carries real traffic today. the artifacts between stations name themselves: the link, the focus, the world, and the measurement that becomes the next link.

the closing arc is the loop's whole point: the measurement becomes the next link. play holds two verbs because play is the membrane where the stack touches the world — render is the way out, measure is the way back.

why exactly four. the removal test: remove link and the system is mute — it can only react to its own renders. remove transmit and it is many private loops, not one mind. remove render and it is a diary — no agency. remove measure and it is open-loop — no feedback, no cybernetics. each removal kills a distinct property: novelty, unity, agency, feedback. and none merge: link is not measure (a mind's reference input is not a sensor reading), render is not transmit (out to the world is not across the graph). a single agent's OODA collapses to measure → focus → render; link and transmit exist precisely because the mind is distributed. there is no fifth motion — everything else is a property of the channel (encrypt, prove) or the attractor (focus).

verbs outside, components inside. the scheme names each seat by its verb and lists the components that hold it; the decomposition within a seat — each component's own registry verb and how they interact — opens on click at soft3.org/scheme. grouping is a debt: if several components share a seat, the seat owes an internal diagram, and now pays it.

the loop among loops

the four survive every known control doctrine — and each teaches something:

single-agent loops are three motions — OODA collapses to measure → focus → render. a distributed mind adds exactly two: link, because minds are reference inputs and not sensors, and transmit, because one graph must live in many cells. no doctrine demands a fifth.

the top-verbs test

against the most frequent English verbs the seats hold: say · tell · ask · write → link; see · hear · watch · find → measure; think · know · decide · understand → focus; do · make · build · show · play → render; send · bring · carry · follow → transmit; have · hold · keep → the medium. the big verbs that are not primitive compose from the loop:

the sweep surfaces two honest absences, both already named critical in status: want has no component — it lives implicitly in φ* weights and tok prices (the economics of writing, critical 1) — and forget has no verb at all (deletion and liability, critical 4). the registry will one day owe a verb to forgetting.

the two guarantees — the medium

not steps but properties of the channel every link enjoys:

nothing "gets encrypted" as a stage of the journey — linking is owned, rendering is owned, measuring is owned. proving likewise: running is proving (nox), storing is proving (bbg).

the one attractor — the centre

the centre is a noun, not a verb: the focus — φ*, tru's own word, the name foculus carries. its verbs from the registry: converge (tru), agree (foculus), think (soma). it is not a step the signal passes through — it is the point the whole loop orbits: everything dances around it. of two conflicting signals, one survives, chosen by φ* past τ: agreement, not voting.

beneath it all — the ground. strata does the math, lens commits, honeycrisp accelerates: form is not a station but what every station is made of, with hemera's hash as the ruler.

the colours are emotions — by evolution, not by assignment. link wears anger red (the will to speak), transmit interest blue (the open wire), render surprise yellow (the render is what surprises you), measure joy green (the sight of growth — and the closing arc runs green); encrypt wears sadness indigo (weight and law of ownership), prove disgust orange (the craft that keeps rot out); converge wears fear violet (the one). the map is anchored at color, the framework at color-emotion spectrum, the protocol use at emotion.

the three stages — the registry's own states

the loop is not staged: link → transmit → render → measure circulates from day one. the stages follow the state column of status literally:

shared → trustless → one. the centre lights last: the mind emerges when a proven, shared loop converges. the trinity maps onto the layers: cyb is the body that runs the loop, cyber is the mind that lights at stage 3, cyberia is the state that governs what the alive loop does.

the stage tests

1. medium — a link cast in one cell arrives in another with no third party. passed live: wire, 2026-09-01.
2. proof — a stranger verifies a read it never trusted.
3. mind — of two conflicting signals one survives, chosen by φ* past τ.

and one test for the loop itself, on any layer: a render observably changes what is next linked.

the census

every component, by its registry verb:

the ground: math (strata) · accelerate (honeycrisp) — beneath every seat. products (consume the loop entire, are not in it): cyb · optica · studio · erga · zoya · mona · xena. the trinity (what the loop is for): cyb the body · cyber the mind · cyberia the state.

what this buys

Focus: the loop is live end to end; the two dark layers are exactly zheng's openings and foculus's deployment — the shortest path to a mind is those two components. Honesty: the scheme's layers ARE the registry's states; when status changes, the drawing changes. Discipline: a proposed component must name its seat by a registry verb — motion, guarantee, or centre; "it would be nice" is not a verb.

soft3 — the registry (23 pages)

soft3 — target structure (proposal)

• soft3 — the door: what the stack is, the seven seats
  • status — the registry of components: every seat, verb, state — the living census
  • the crystallization (§0 above) — the boundary rule, the loop, the stages
  • roadmap/ — component-boundaries · migration · stack-completeness · terms-map
  • specs/ — terms · types · languages · filenames · bytes (the 256-value alphabet — §1c)
  • docs/ — launch · chains-as-plugins
  • proposals/ · conformance/ · schema/ · cli/ · mcp/ — the workbench README shelf

1 · cyber — target structure

the protocol crystal as a navigation tree: one door, ten branches. every staying page hangs at exactly one node — that is what makes the system closed; cross-links remain free. italics = to be written or renamed.

the tree

every staying page hangs at exactly one place; cross-links stay free, but this tree is the canonical way in. bold = hub that owns its branch.

• README — the door: what cyber is, two reads, two doors in
  • litepaper — ten minutes, the whole argument
    • whitepaper — the mathematics and the proofs
  • install — enter by terminal or robot
    • contribute — four lanes in
  • concepts — the atlas: every atom, grouped by what it answers
    • the graph — what knowledge is made of
      • cybergraph · particle · cyberlink · neuron · token · hash · knowledge · cell
    • the focus — how importance is computed
      • focus · rank (absorbs cyberank) · attention · view · prob · rational neuron · fixed point · tri-kernel · tru · context packing
    • the acts — what a neuron does
      • staking · mining · rewards · impulse · intent · inception · sealing · cascade
    • the trust — what cannot be bought
      • karma · happiness · personality · privacy · license · landauer limit
    • the mind — what it all becomes
      • superintelligence · interplanetary superintelligence · self · crystal · core
    • the culture — how it speaks
      • cyberculture · cybersophy · cybersphere · cyberverse
  • contract — what must hold, whoever implements it
    • cybergraph contract · cyber/proofs · cyber/epistemology (from epistemology) · cyber/identity (from identity)
    • $CYB — the money contract
    • cyber/launch — the genesis contract
  • cybernomics — the money, from law to plumbing
    • nomics · netics · cap · delegation · automated market maker · cyberlink market protocol
    • tokens — the type system: coin · badge · plumb · basic token operations
    • money specs: money loop · light money · adaptive hybrid economics
  • network — the machine room: the deep protocol articles (cips)
    • 3c · channel · communication · hierarchy · light · gravity · luminosity · security
  • research — the papers: what is argued, not yet law
    • physical analogies · algorithmic essence · knowledge capacity · link production · universal law · egregore properties · future of computation · neuroscience principles · unified mining · knowledge economy · theoretical foundations · bootstrap · 32-byte tokens · energy market · gradient descent · cybergraph model architecture · focus flow computation · adaptive hybrid economics · analizer · seer · privacy trilateral · oikos (proposal: one token, one chain — the architecture; carries its own adoption map over ~/cyber and soft3) · spectral cell division (proposal: extracted from cell, deliberately unimplemented)
  • specs — the engineering contracts
    • component ownership · full-flow claims · node modes · rewards completeness
  • self — the protocol's own agency
    • dmn · linking · parametrization · sigma
  • blog — pointer. the chronicle lives at cyberia.blog
  • cyb · soft3 · cyberia — pointers to the sister subjects, whose graphs live at cyberia.blog
  • restructure — this plan, then this record

the ledger — cyber (156 pages, 0 undecided)

+2 since the census (2026-09-08): research/oikos — stays · research, the one-token-one-chain architecture proposal (its adoption map names per-page tasks across ~/cyber and soft3 — do not lose them); research/spectral cell division — stays · research, division mechanics moved out of cell, deliberately unimplemented.

1a · bbg absorption — refine, do not copy

eight cyber research pages (march 2026) argue the NMT → polynomial transition. bbg already has that transition in specs/ and docs/explanation/. copying the eight files into bbg would ship a second, older textbook next to the living one. the move is absorption: unique residue into named existing files, then delete the source.

no new files. landing paths below all exist today.

the dimension law

BBG_poly(dimension, key, t) already has time as the third axis. a time dimension that stores snapshots duplicates the axis. signals as a dimension of state derived from the signal log is circular — the log is primary, the checkpoint commits the fold. files can be fields on particles (the CID is already the key). locations can be fields on neurons until location proofs are a live product. balances as an 11th dimension is a product feature, not a law — coins plus private A(x)/N(x) cover value until public opt-in ledgers ship.

chaosnet public dimensions: six.

private, not dimensions: A(x) commitment polynomial, N(x) nullifier polynomial. root: BBG_root = H(Lens.commit(BBG_poly) ‖ Lens.commit(A) ‖ Lens.commit(N)).

the current ten in specs/architecture.md (and eleven in specs/state.md, plus thirteen NMT sub-roots in README.md) are the old NMT census copied into the polynomial. that is quantity, not law.

roadmap (rows on existing bbg/roadmap/README.md, not new pages):

• collapse time, signals, files, locations out of the public polynomial — they are axis, log, or fields
• files as its own dimension only if DAS queries must not load the particle record
• locations as its own dimension when location proofs are queried independently
• balances as a seventh public dimension when plaintext opt-in balances ship
• do not add an eleventh dimension to match specs/state.md

prerequisite inside bbg, before any fold: one voice. README.md still says 13 NMT sub-roots; specs/architecture.md says 10 public dims; specs/state.md says 11. reconcile those three to the six + A/N root above. specs/indexes.md and specs/statistics.md follow.

file table

every source is a real file under cyber/research/. every target is a real file under bbg/ or cyber/.

after the folds: delete the eight sources. rewrite cyber/research.md as a map of what stayed and where the rest went. bbg in cyber remains the protocol atom (what must hold), not a second architecture essay.

work order

1. reconcile bbg README.md · specs/architecture.md · specs/state.md · specs/indexes.md · specs/statistics.md to six public dimensions + A/N root
2. fold residue into the named existing files (one commit per target file)
3. delete the eight cyber sources; fix wiki-links to the targets
4. one line on cyber/research.md pointing at bbg explanation/spec

1b · foculus absorption — refine, do not copy

four cyber research pages (march 2026) sit next to a living foculus crate. the crate already has the four matching documents: README.md, specs/provable-consensus.md, specs/structural-sync.md, specs/vec.md, docs/explanation/overview.md. live URLs (files on disk 2026-09-08; paths match the soft3 mount):

• /soft3/foculus
• /soft3/foculus/specs/provable-consensus
• /soft3/foculus/specs/structural-sync
• /soft3/foculus/specs/vec
• /soft3/foculus/docs/explanation/overview

copying the four files into foculus would ship a second textbook. two of them are the living specs (older drafts). the move is: fold the unique residue into those existing files, then delete the sources. no new files.

ownership does not move. specs/structural-sync.md already says the pipeline is cross-cutting: layers 1–4 belong to cybergraph, bbg, radio; foculus owns layer 5 (global merge). cyber loses the duplicate essays, not the layer map. protocol atoms focus / tri-kernel / collective focus theorem stay in cyber — what must hold.

token overlap of body text (frontmatter stripped), 2026-09-08:

contradictions — do not copy these

living-spec bug, fix if the file is touched: specs/provable-consensus.md circuit totals 1,420M constraints; the closing paragraph still says "624 million" (copied from the research draft).

file table

every source is a real file under cyber/research/. every target is a real file under foculus/.

after the folds: delete the four sources. rewrite inbound wiki-links (provable consensus, vec formalization, structural-sync, foculus and the research-prefixed forms) to the live /soft3/foculus/... pages. cyber/research.md points at /soft3/foculus.

work order

1. fold the named residue into foculus/specs/vec.md (SEC table, pairwise gap, FLP/CAP, corrected comparison) and foculus/specs/structural-sync.md (Byzantine table)
2. while touching foculus/specs/provable-consensus.md, replace the closing "624 million" with 1,420M
3. delete the four cyber sources; fix wiki-links
4. one line on cyber/research.md pointing at /soft3/foculus

1c · 256 symbols — the byte is a stack law

cyber/research/256 symbols.md is ledgered as nox because it lists 18 opcodes. that is the wrong subject. the page allocates every value of a byte across the whole stack: nox ISA, hemera, nebu, kuro, jali, genies, trop, state, decider, printable ASCII, UTF-8. nox owns how axis reduces; it does not own that 0x80 is hemera and 0x97 is trop_matmul. a byte that names five algebras is a soft3 spec.

the why is energy. one byte, one meaning. 54 reclaimed C0/C1 codes (18 ISA + 36 jets) plus 40 reserved. printable text and UTF-8 lead bytes stay sacred. the 2026-03-27 journal already states the consequence of jets-as-opcodes: 400× code compression against a formula noun, O(1) array dispatch, one range-check constraint instead of formula verification. that is the stack being cheap at the encoding layer, not a nox optimisation note.

live counterparts (do not copy over them):

• /soft3/nox/specs/patterns — the 18 reductions. canonical ISA semantics
• /soft3/nox/specs/jets — the 36 genesis jets, same group counts as the research table
• /soft3/nox/specs/encoding — Model B noun layout: length-discriminated, tag-free, formula tag is an 8-byte atom 0–17. a different layer
• /soft3/specs/languages — sixteen dialects over five algebras. not a byte map
• /soft3/specs/filenames — NTFS path safety. not this

two encodings, both true. Model B is how data lives (an atom is 8 bytes, a pair is 64, type from length — migration phase 3, done). 256 symbols is how a program is a byte stream: ISA and jets occupy the teletype's dead codes so instruction fetch is one byte while text still parses as UTF-8. the spec must name both layers or it fights nox/specs/encoding.md and soft3/specs/terms.md ("never in a tag byte inside the data").

nox hygiene, not a reason to dump the article into nox: nox/specs/vm.md still says 12 genesis jets; nox/docs/explanation/jets.md still says five. living registry is 36. reconcile those to the jets README.

no existing soft3 spec is this law. inventing a dump page is forbidden; writing the missing spec is the job. filename soft3/specs/bytes.md, alias 256 symbols. live URL /soft3/specs/bytes.

file table

soft3/specs/languages.md gets one sentence: the substrate's byte alphabet is bytes. do not grow languages.md by 900 words.

work order

1. write soft3/specs/bytes.md as the stack alphabet (groups, UTF-8, energy, two layers). opcode rows are an index into living nox specs, not a second ISA
2. one sentence on soft3/specs/languages.md; add bytes to the soft3 spec shelf in this document's target tree
3. reconcile nox vm.md and docs/explanation/jets.md to 36 jets
4. delete cyber/research/256 symbols.md; point 256 symbols and the 2026-03-27 journal at /soft3/specs/bytes

2 · cyb — target structure

the robot as a navigation tree. the repo's root/ directory dissolves — pages live flat; links below are today's paths. the anatomy is the contract every name answers to.

• README — the robot: what it is, get it at cyb.ai
  • anatomy — the source of truth: 20 parts in six layers; every doc, world, and crate names things by it
    • state — external truth with a tier: T0 proof · T1 anchor · T3 badge
  • product — intelligence you own (absorbs the living claims of the cyb whitepaper)
    • philosophy · story · spec
  • roadmap — where it goes
    • team · dev
  • reference — how it works, one page per organ where an organ exists
    • architecture (absorbs JS-era architecture) · rendering · routing · terminal · cells · particle · avatar · truth · features · scripting
    • formats: format · cyb-registry · cyb-model · cyb-vocab · fs
    • platforms: android
    • audit: benchmarks
    • security audit private key import — incoming from cyber
  • releases — how it ships
    • release-process · v0.1.0
  • ward — the guardian
  • legacy/ — one README over the retired JS era (32 pages fold here)
  • .claude/plans/ — the workbench (4 plans)

proposal — the design absorption (from review, to decide pointwise)

four claims on the table, each a separate yes/no:

1. code must wear the anatomy — shell/core/cli/apps is not anatomy; target mapping: shell worlds (graph · sigma · com · body · cells) → organs/, soma bridge → organs/soma, vault code + signing → organs/vault (signer lives on as vault, its JS-era file stays in legacy), cyb-core → tissue/ (shared flesh), mir = the paint of organs/brain. executed as anatomy phase 4.
2. reference/ dissolves into design/: design/surface (how worlds render — prysm/UX: rendering · routing · particle) · design/body (the Bevy runtime: architecture · terminal · android · benchmarks) · design/stack (the contracts to soft3: format · cyb-registry · cyb-model · cyb-vocab · scripting).
3. product trims to 4 — robot · product (absorbing the living claims of philosophy/story/spec) · roadmap · team.
4. anything fitting none of the shelves is legacy or a soft3 component's page.

the ledger — cyb (83 pages, 83 verdicts, 0 undecided)

status: executed 2026-09-06 — root/ dissolved into six shelves, 111 path links healed; the rows keep their pre-move addresses as the record.

3 · cyberia — target structure

the nation as a navigation tree: six shelves, each with a contract README.

• README — the nation
  • foundation — why: vision · manifesto · whitepaper · architecture · strategy · space doctrine · org · cyberian · your share of the sun (moves in)
  • protocol — how the state runs: century index · bank above banks · location proof · space accounting · services · system · marketplace · marketplace spec · ladder · orgs · ephemeris · dyson sphere · maps (absorbs its 7 one-liners)
  • land/ — where (promoted from research/cyb-land; 42 pages move in, 23 empty die)
    • visit · stay · activities · attractions · community · flora
  • community — who: talents · chronicle (receives 22 valley entries from cyber's blog)
  • courses — teaching: edge-city-patagonia-2025 (6 lessons)
  • research — the workbench, explicitly unfinished
    • mimi · migration-market · genome-protocol · oxytocin · cyber-sheep · cyberia-my · tech (16 seeds keep pages, 26 fold to its table)
    • incoming: smart capital
    • events — extracts to its own repo; a one-page product card stays

the ledger — cyberia (180 pages, 180 verdicts, 0 undecided)

4 · order of movements

1. deletions that free names (1c + empty cyb stubs + empty cyberia stubs) — zero inbound by measurement, zero breakage
2. within-repo folds — rank⊕cyberank · maps table · tech index · cyb-land → land/ · cyb root/ flattening
3. cyber → outward (1b) — ~24 pages with ~40 link fixes
4. research redistribution (1a) — pages home by subject. bbg eight: absorb into existing spec/explanation (see §1a), do not copy. research index rewritten as the map of what stayed and where the rest went
5. cyb legacy fold (2a + 2b)
6. cyberia boundaries — events extraction, incoming placements
7. contract promotions — cyber/epistemology, cyber/identity, cyber/proofs written from epistemology, identity, security material

5 · acceptance

• link integrity ≥ 99% per subgraph (measured 94.5% in cyber on 2026-09-01)
• zero pages under 12 words outside indexes (was 38)
• zero phantom targets with ≥ 3 inbound refs (was 7)
• every page passes the rule in one step; arguable pages are named in this document with their tiebreak
• crystallinity ≥ 95% (was 88%) — same script, number published in each phase's commit message

plan approved → phases execute as separate commit series. finished rows leave the table.