# Follow a claim into its sources. The reference is organised for inspection at several depths: a common architecture, seven Geometry Atlas views, finite numerical profiles, recorded evidence and explicit trust limits. Visitor question: Where can I inspect the architecture, mathematics and evidence? Genre: reference. Website explanation · Updated 2026-10-03. ## Architecture [Seven views of the same activity — Geometry Atlas](/research/geometry/) connects each GEO-1…GEO-7 source to concrete episodes and the [one-kernel map](/understand/one-kernel/). It is distinct from the Incident Atlas. The accepted architecture lock GitHubGitLab defines the common relationships and their authority. Publication chapters and diagrams help explain them; they do not create new runtime interfaces. A conceptual arrow is not evidence that every depicted relationship ran together in one experiment. The Geometry Atlas overview GitHubGitLab holds one activity in view while separating its concerns: | View | Question and source scope | | --- | --- | | GEO-1 GitHubGitLab | How does intent become bounded, consuming Work? A conceptual view of semantic input, topology and typed child results. | | GEO-2 GitHubGitLab | How do independent owners retain their decisions? A conceptual pattern with a recorded Football inset. | | GEO-3 GitHubGitLab | How can useful work outlive a changed resource? The principal EWS3R2 lane separates resource, result and permission lifetimes. | | GEO-4 GitHubGitLab | How does a source body become checked local input? Recorded Football E, B and C relationships keep refusal separate from consumption. | | GEO-5 GitHubGitLab | How do different computations contribute? Recorded W4 revision 1 connects semantic material, quantum samples, local checking and consumption; EWS is a separate inset. | | GEO-6 GitHubGitLab | How does experience affect expenditure? G3/G4 connects qualified history to finite allocation and actual Work; calibration reuse is a separate witness. | | GEO-7 GitHubGitLab | How does a new capability enter later work? HOW, WHAT, authoring, examination and admission remain distinct from current runtime permission. | ## Mathematics Each numerical profile answers a particular question. The experience chapter GitHubGitLab defines integer advisory values, exact rounding, eligibility and finite budget allocation. Its fixed-point scale `Q = 10^9` is dimensionless; a Work dispatch unit is neither a token nor money, time or a probability of safety. Hard eligibility precedes ranking. The Wedding mathematics section GitHubGitLab defines guest/table indicators, mandatory-condition penalty `H`, and the objective `Q(x) = P × H(x) + selected_soft_cost(x)`. Here `Q(x)` is an optimisation objective, distinct from the fixed-point scale. A solver or QPU supplies candidates; original-condition checks determine whether they satisfy this finite problem. The recorded hardware result establishes no quantum advantage. Calibration is another profile: an exact rational correction in abstract input units. Qualified reuse reduces specific observed Work calls while retaining a current read and Root decisions; it does not by itself measure a wall-clock, energy or monetary saving. These explicit meanings make the formulas useful without turning them into universal performance claims. ## Evidence and verification Keep five evidence classes separate: **accepted contract**, **recorded execution**, **independent checking within a declared trust scope**, **architectural inference**, and **proposed future work**. A signature binds bytes within its trust scheme; it does not establish every external fact or grant present permission. Start with a concrete claim in [Workspace](/demonstrations/workspace/#recorded-evidence), then follow its record ID and field into the selected source. The Paper Source Key GitHubGitLab resolves editorial labels, primary paths, historical refs and selectors. Five Implementation Routes GitHubGitLab connects Root/effect, child topology, memory/time, external evidence and authorship to contracts, code and recorded checks. Reading sources, checking saved artifacts, starting a new deterministic run, making a new live provider call, and independently admitting code are different activities. The verification chapter GitHubGitLab describes those routes. This website performs no runtime campaign, and opening it authorises none. ## Incident-to-Proof Atlas **[A refusal is only half the test](/research/incident-atlas/).** Read the full map of twenty cards and five experience consumers, with selected lawful continuations and offline Readers. The Incident-to-Proof Atlas GitHubGitLab asks where finite risk/control cases reach a boundary and how lawful work can continue. It is a different publication from the seven-view Geometry Atlas. Its twenty cards cover five actual consumers and seven effective history samples. Direct causal evidence, a shared domain proof and a control performed after consumption have different scope. The catalog combines reported incidents, research and requirements; it does not claim twenty independent learners or reproduced external attacks. Exact case routes GitHubGitLab preserve those distinctions. Supported saved replay does not recreate live authority. ## Reference today Version and role travel with the material. These are related sources, not one byte-identical snapshot: | Basis | Identity and role | | --- | --- | | Accepted technical basis A | `2e965ecb18e545e428380eb8e9aa5a7037a388be`. The accepted finite technical reference is `G6A_TECHNICAL_READY`; its recorded composition includes fresh and retained evidence. | | Publication snapshot P | `800f38c3407b3f4ec93dc943c977ffeecb614881`, tag `radiolaria-os-reference-g6b6f-v01`. The public Release was published on 29 September 2026 and contains eight assets. | | Later repository entry | `62716374021e273b46878a824af39c1a94593cd7`, as recorded on 1 October 2026. Navigation and illustrations changed after P; the frozen release assets did not thereby become new exports. Live main can advance. | | Public handoff | Author-supplied snapshot of 1 October 2026, an explanatory engineering companion containing historical lessons and source identities. It is not a new normative contract or independent audit. | | This website | English editorial candidate of 2 October 2026, built for local review. Its explanations and machine-readable routes are new editorial work, not newly executed experiments. | | Further work | New integrations, an integrated capability factory, broader numerical programmes and a native ecosystem require their own engineering and acceptance. Publication does not close the entire Gate 6 programme. | Historical `PENDING`, `NOT_RUN` and unpublished-proposal captions remain in frozen documents. Read them with their date and later Release/handoff record; neither erase them nor use them as today's publication status. The four approved technical deferments remain separate from achieved reference scope. [Downloads](/downloads/) identifies the actual published files. ## Limits and trust The finite reference assumes its declared reviewed source, runner, observer and independently retained inputs. It does not establish general isolation for arbitrary hostile code, production security, universal planning, global federation or a real banking/booking deployment. Those operational responsibilities belong to the next integration's specific design. A limitation does not excuse a demonstrated violation of an in-scope contract. Equally, an uninspected source is not evidence that a mechanism is absent. The historical scope document GitHubGitLab preserves its preparation-era status, while the method chapter GitHubGitLab explains how to assess a bounded claim and its lawful neighbour. Continue with one [demonstration](/demonstrations/), use an [evaluation prompt](/read-with-ai/#evaluate), or follow the [Build route](/build/) for a concrete domain task. ## Trace the result, not just the answer Exact bytes and hashes identify a material; a seal binds the relationships declared by its scheme. A signature is checked against its identity, key, source and scope. These checks do not establish every real-world assertion or grant a new action. The [external E → B → C story](/demonstrations/external-drs/) follows producer, published body and current local consumer; [Wedding](/demonstrations/wedding/#quantum) follows a measured candidate through validation and consumption. Stored verification checks recorded relationships. A native rerun executes its declared program again; a mock action, fresh live model call and hardware task are different operations. Opening a Reader performs none of them. ## A better score cannot buy a forbidden action [Experience](/demonstrations/experience/) follows finite G4 allocation: cap 9, spent 1, reserve 1, distributable 7; actual Work shifts from 4/3 to 3/4. AVF is advisory within eligible choices. Hard conditions and current owner permission remain outside that trade. N1-05 records a score of 1.0 without effect authority; full AVF/StrongGT are separate deferred mathematical work, not a reason to erase the finite working path.

From governance commitments to executable controls

Engineering interpretation ·

Safety commitments need controls that people can inspect: what may run, who may authorise it, and what evidence shows the outcome. A policy states the obligation; an execution system must make the relevant checks concrete. Radiolaria provides a technical basis for that work: local decision authority, scoped action permissions, cryptographic evidence and verification of recorded execution. The [Incident-to-Proof Atlas](/research/incident-atlas/) connects defined failure cases to refusal boundaries and useful continuations. Source routes GitHubGitLab let reviewers inspect the mechanisms and their stated trust assumptions. The 29 September 2026 [White House Accord on Super Intelligence](https://www.presidency.ucsb.edu/documents/white-house-accord-super-intelligence) calls for internal controls, internal review, independent external assessment and board oversight. It is a voluntary commitment, not a certification standard. Radiolaria offers mechanisms and recorded evidence relevant to selected execution controls; it does not replace independent auditors, corporate oversight or a deployment-specific compliance assessment. ## Sources and scope - Accepted architecture lock GitHubGitLab — accepted architecture contract; ref `2e965ecb18e545e428380eb8e9aa5a7037a388be`; path `specs/current_architecture_lock_v01.md`. Source date: accepted technical basis A. Access: HTTP_200; orientation passages inspected; explanatory handoff consulted; checked 2026-10-02. - Geometry Atlas overview GitHubGitLab — publication explanation; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/atlas/OVERVIEW.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - GEO-1: Intent becomes bounded, consuming Work GitHubGitLab — publication conceptual or recorded view; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/atlas/GEO-1.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - GEO-2: Independent owners retain their own decisions GitHubGitLab — publication conceptual or recorded view; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/atlas/GEO-2.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - GEO-3: Useful work can outlive a changed resource GitHubGitLab — publication conceptual or recorded view; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/atlas/GEO-3.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - GEO-4: Qualified context reaches Work; refusal stops GitHubGitLab — publication conceptual or recorded view; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/atlas/GEO-4.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - GEO-5: Different computations share checked consumption GitHubGitLab — publication conceptual or recorded view; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/atlas/GEO-5.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - GEO-6: Recorded experience changes finite expenditure GitHubGitLab — publication conceptual or recorded view; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/atlas/GEO-6.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - GEO-7: Creating a component does not grant its authority GitHubGitLab — publication conceptual or recorded view; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/atlas/GEO-7.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - Experience, choice and finite expenditure GitHubGitLab — publication explanation; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/chapters/05_experience.md`. Source date: 2026-09-29. Access: HTTP_200; complete chapter text read; checked 2026-10-02. - Wedding: changing a plan GitHubGitLab — publication explanation; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/chapters/08_wedding.md`. Source date: 2026-09-29. Access: HTTP_200; complete chapter text read; checked 2026-10-02. - Evidence and method GitHubGitLab — publication explanation; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/chapters/06_method.md`. Source date: 2026-09-29. Access: HTTP_200; complete chapter text read; checked 2026-10-02. - Verification levels and limits GitHubGitLab — publication explanation; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/chapters/13_verification.md`. Source date: 2026-09-29. Access: HTTP_200; complete chapter text read; checked 2026-10-02. - Five implementation routes GitHubGitLab — publication source index; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/release/IMPLEMENTATION_ROUTES.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - Exact publication source key GitHubGitLab — publication source index; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/PAPER_SOURCE_KEY.md`. Source date: 2026-09-29. Access: HTTP_200; targeted source/index inspection; checked 2026-10-02. - Incident-to-Proof Atlas GitHubGitLab — historical showcase context; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/incident_to_proof_atlas_v01/README.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - Incident Atlas exact case routes GitHubGitLab — historical case index; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/incident_to_proof_atlas_v01/reader/CASE_ROUTES.json`. Source date: 2026-09-29. Access: HTTP_200; route file retrieved; not a new proof-package review; checked 2026-10-02. - Historical publication scope and trust limits GitHubGitLab — publication explanation; ref `800f38c3407b3f4ec93dc943c977ffeecb614881`; path `docs/showcase/radiolaria_os_v01/LIMITS.md`. Source date: 2026-09-29. Access: HTTP_200; text read; checked 2026-10-02. - Radiolaria reference v0.1 release GitHubGitLab — publisher release metadata; ref `radiolaria-os-reference-g6b6f-v01`; path `https://github.com/AAkhtanin/hedgehog-os/releases/tag/radiolaria-os-reference-g6b6f-v01`. Source date: 2026-09-29. Access: supplied task and public handoff metadata; binaries and DOI resolver not reverified; checked 2026-10-02. - Later repository entry snapshot GitHubGitLab — later navigation snapshot; ref `62716374021e273b46878a824af39c1a94593cd7`; path `README.md`. Source date: 2026-10-01. Access: HTTP_200; entry passages inspected; not the frozen publication snapshot; checked 2026-10-02. - [Public Work Assistant Handoff](/downloads/RADIOLARIA_PUBLIC_WORK_HANDOFF_EN_V01_20261001.txt) — author supplied engineering context explanatory companion; ref `public snapshot 2026-10-01`; path `public/downloads/RADIOLARIA_PUBLIC_WORK_HANDOFF_EN_V01_20261001.txt`. Source date: 2026-10-01. Access: complete supplied text read; expected bytes and SHA-256 verified locally by task intake; checked 2026-10-02. - [White House Accord on Super Intelligence](https://www.presidency.ucsb.edu/documents/white-house-accord-super-intelligence) — governance context not certification; ref `document dated 2026-09-29`; path `documents/white-house-accord-super-intelligence`. Source date: 2026-09-29. Access: APP full document read; four control/audit layers and possible future codification checked.; checked 2026-10-03. This page is a website explanation, updated 2026-10-03. Its explanation does not create a new execution result or change the status of its sources. ## Continue reading - [Work that keeps its meaning.](/understand/) - [Different tasks. A common organisation of work.](/demonstrations/) - [Read with your AI assistant](/read-with-ai/) - [Choose what you want to explore](/downloads/)