CARRIER — ORGANIC REVISION 01
Local research edition · 2 October 2026

OPEN
review/organic-revision.html

THE AUTHORISED PROMOTION
The fourth working entry was w2418, “historical description, current allocation.”
It is now checked/2442 in state-promoted/, making 2,443 checked entries. Its
definition, RGB colour and allocation identity are unchanged. The three original
working examples w0–w2 remain unchecked. The complete earlier live snapshot is
preserved in evidence/live-before/. The colour registry is byte-identical.

THE ORGANIC REVISION
All 2,443 checked definitions received an AI reading, individual scope note and
one to three family assignments. Existing relation lists were inspected with
each definition. New typed links require evidence from both endpoint definitions
and an explicit qualification. The full original-source books were not reread,
and every possible pair was not semantically adjudicated.

The map contains every checked concept. “Referenced by” is rebuilt from all
checked records; references from the working examples appear separately. The
complete machine-readable reverse index includes both tiers. Families overlap.
The spatial arrangement of families is not a claim about the ontology of reality.

Neighbour circles show reference distance, not Local/Global/System/Galactic/etc.
Those seven named perspectives remain separately inspectable vocabulary. A finite
graph is not described as physically infinite or evidence of other universes.

Threads are curated reading itineraries. Each step identifies whether it uses a
recorded link, a proposed link, or a juxtaposition. A chain is not a proof; the
presence of A–B and B–C does not establish every possible A–C assertion.

TWO LOCAL STATE EDITIONS
carrier-local-promoted.zip / state-promoted/
  Only the authorised working-entry promotion. No new relation proposals applied.

carrier-linked-proposal.zip / state-linked-proposal/
  A schema-valid exploratory projection of the AI link proposals into Carrier's
  existing untyped relations field. Each affected record retains a provenance
  note marking the additions AI-proposed. Definitions, IDs, payloads and colours
  are unchanged. Symmetric navigation for related/contrast/analogy is materialised
  in both directions; this is never a reverse causal assertion. The typed evidence
  and qualifications in relation-evidence/ must accompany this edition.

Do not mistake the second edition for completed human review. Its checked markers
belong to the definitions, not automatic approval of every proposed connection.
Its new hash chain is a new snapshot; earlier expression pins continue to refer
to their preserved earlier snapshot. Nothing has been uploaded or sent to the gate.

REVIEWING THE LINKS
The Review links tab presents both definitions, the relation type, rationale and
qualification. Accept, decline or reset each proposal. Download decisions before
closing the tab: no browser storage or automatic saving is used. Import a saved
decision file to resume; its dictionary and proposal-set pins must still match.

To materialise only accepted decisions locally, from the release folder run:
  node tools/build-linked-state.cjs --decisions PATH-TO-DOWNLOADED-DECISIONS.json

The output is state-linked-approved-local/. The command checks the base head, exact proposal-set hash,
known proposal IDs, duplicate decisions and allowed statuses, then validates the
complete five-file state. It does not authenticate a human identity or upload it.

NEW MEANINGS AND SIMULATIONS
Candidate meanings are unallocated drafts, outside both Carrier tiers. Each has
parents, a proposed distinction, rationale, counterexample and lexical neighbours.
Distinct wording does not prove novelty. Existing meanings may already suffice.

The synthesis lab produces a structured composition with exact parent pins. It
checks the form and explicitly leaves semantic obligations outstanding. A thought
can be new without requiring another dictionary entry. COMPOSITION-RULES.txt
describes the provisional discipline; it is not a claim to established new laws.
RELATION-RULES.txt defines the five experimental relationship types and how their
qualified assertions differ from navigating the graph in either direction.

The 12,000 seeded requests simulate navigation under uniform, within-family and
cross-family workloads, plus a five-hub-outage scenario. They compare the recorded
graph with the proposed graph. They do not simulate actual linguistic competence,
real readership, autonomous invention, or demand for a particular new concept.
Shorter paths cannot validate the very hypotheses added to produce them.

EVIDENCE
analysis/promotion.json              Exact local promotion and state heads
analysis/graph.json                  Entire annotated map and derived views
analysis/referenced-by.json          Complete recorded reverse index, both tiers
analysis/review-ledger.json          All individual AI definition observations
reviews/a-review.json etc.           Partitioned reviews, proposals and rationale
proposals/typed-links.json           Proposed relation evidence
proposals/concept-gaps.json          Unallocated candidate meanings
analysis/simulation-tasks.json       Every deterministic workload request/result
analysis/simulation.json             Results and limitations
analysis/findings.txt                Findings, measured outcomes and next steps
analysis/browser-checks.json         Local interface and synthesis checks

REPRODUCING THE LOCAL BUILD
Requires Python 3.10+ and Node.js 22+. The data builders use standard libraries.
The original checked and working snapshots are already included; do not re-fetch
into their preserved evidence directory after the live registry changes.

  node tools/promote.cjs
  python tools/prepare-review.py
  python tools/build-graph.py
  python tools/simulate.py
  node tools/build-linked-state.cjs
  python tools/build-desk.py
  python tools/write-findings.py
  python tools/package.py

Human-readable AI review notes and edges are retained authored input, not regenerated
by a lexical algorithm. The browser QA helper uses the original machine's installed
Playwright/Edge path; adapt it on another machine. It is unnecessary for reading.

The historical LEGACY_ID_HISTORY warning for w3–w9 is preserved. State validation
establishes internal consistency and allocation policy, not the truth of definitions,
the usefulness of a new relation, or the authenticity of a review decision.
