Where each old decision went

Before 19 October 2026 the project's rules lived in 43 numbered decisions (D0 to D41, including a variant called D0-b) and in a long instruction file. The owner replaced them with one short charter. This page lists every decision and says what became of it: the rule lives on in a numbered charter clause, it was folded into a broader clause, or it is history only. Nothing was deleted. Every decision keeps its original heading in the live index, so old links still land, and the full original text is preserved unchanged in the archive.

flowchart LR
  old["Old decision<br/>D0 to D42"] --> q{"Does the rule still<br/>bind today?"}
  q -- "Yes, as written" --> kept["Kept<br/>own charter clause"]
  q -- "Yes, as part of a wider rule" --> merged["Merged<br/>into a broader clause"]
  q -- "No: superseded, one-off<br/>or expired" --> retired["Retired<br/>history only, in the archive"]

The three fates. "Retired" applies to rules only. A research mechanism is never retired; see the mechanism board and D22.

How to read the table

  • Kept means the decision survives with its meaning and has a home in the charter.
  • Merged means its content now lives inside a clause that also covers other decisions.
  • Retired means it no longer binds. It was superseded by a later decision, was a one-off order, or had a time limit that has passed. Its text stays in the archive.
  • Clause numbers such as 3.6 refer to sections of CHARTER.md. Section 1 is the mission, 2 the products, 3 the technical constraints, 4 the evidence rules, 5 the workflow and 6 the retired list.
  • The fate column follows the final DECISIONS.md index adopted with the charter (decision D42). It differs from the working rule map in one place: it files D14 as merged, because its owner boundaries and GitHub authority survive while its council is retired.

The table

DecisionWhat it said (one sentence)FateCharter home
D0Serving forbids dense matrix multiplication; first form of the sparsity test, replaced the same day by D0-b.RetiredSuperseded by D0-b; its sparsity test survives as D5 (3.9).
I1 to I5Serving efficiency invariants: sparse access, bounded candidates, bytes per token, multiplier-free kernels, exact memory.Kept3.9
D0-bAdditive linear maps adopted as a serving stepping stone.RetiredSuperseded by D11 (serving) and D25/D30 (no dense maps).
D1Falsify a mechanism before extending it.RetiredSuperseded by D2, D12, D20 and D22; a negative now closes only a configuration (4.1).
D2A mechanism's contribution is judged by measured ablation; enablers are a separate class.Merged4.1 (enablers survive as PARKED with reopen conditions)
D3Takeover clarification, including an offline matmul permission.RetiredSuperseded by D25/D30; the permission was withdrawn.
D4Goal decomposition and the geometry gate: advantage is measured against controls.Merged4.4 (lawful non-neural controls only, per 3.10)
D5Per-token parameter sparsity is the terminal serving invariant.Kept3.9 (the D5-b form)
D6The target objective is a long-range information probe.Merged4.4 (long-range probe items plus count-table controls)
D7Adopt the integrated attention-language programme.RetiredSuperseded by D8 and D19.
D8Correct the training method and reference ladder.RetiredSuperseded by D32/D37 (training) and D28 (no neural reference).
D9Prevent experiment loops; a repeat needs new causal evidence.Merged4.4 (pivot note) and 5.3 (intent note)
D10A converted open-weight backbone as the interim chat vehicle.RetiredSuperseded by D11.
D11One native, multiplier-free, transformerless integer serving contract for every lab.Kept3.6
D12Gates promote, never kill; reopen geometric candidates; keep a toolbox.Merged4.1 (ACTIVE, READY, PARKED; no terminal status)
D13Record of the 29 September two-track plan.RetiredSuperseded by D14, D18 and D19.
D14Durable autonomous labs, GitHub as authority, a three-seat council.Merged5.1 (owner boundaries) and 5.2 (GitHub authority); the council is retired (owner, 19 Oct).
D15Converted students may become served candidates after an audit.RetiredSuperseded by D17; excluded by D28 and D11.
D16Working rules from the 29 September council.RetiredSuperseded by D17; the council is retired.
D17Transformer-free conversion; parity decisions with paired seeds and measured tolerance.Merged4.3
D18One retrieval question for 1 to 14 October; other tracks parked.RetiredThe window expired; its re-entry gate travels with D38 (3.9).
D19Grounded conversation and durable memory come first; self-review allowed.Merged1 (mission) and 5.5 (delivery)
D20Geometry stays first; the no-loss rule is suspended only after exhaustion.Merged3.1 and 4.1 (with no terminal status, no suspension procedure is needed)
D21Three non-moving results on one line force a pivot; one-off lab orders of 9 October.Merged4.4 (pivot note); the lab orders are retired as executed or overtaken.
D22A negative closes a configuration, never a mechanism; power and transfer rules; five closures reopened.Kept4.1 and 4.3
D23No softmax anywhere, including losses, sampling, teachers and equivalent forms.Kept3.2
D24No CPU model compute, and no GPU on work that cannot change a decision.Kept (scope narrowed)3.5, now research compute only; serving on client devices is allowed (3.6).
D25Geometric operator phase: squash and matmul bans, GPU-only compute, rule freeze.RetiredSuperseded by D32/D37; its bans live on in 3.2 and 3.3.
D26Vast.ai is the default pod provider; Runpod is the emergency backup; caps of 4 pods and $8 per hour.Kept5.4
D27Rust first, with the uor-foundation crates as the shared floor.Kept3.11
D28No transformer or neural comparisons until the native system works end to end.Kept3.10
D29No banned mechanism in any compiled or loaded module, vendor content included.Kept3.4
D30No matmul or softmax anywhere without wrapper laundering; Rust only; GPU-only heavy compute; pod kernel builds.Merged3.2, 3.3, 3.4, 3.5 and 3.11
D31No result is ruled out on an instrument technicality.Kept4.2
D32Discrete ternary, Hamming and quaternion substrate; no float in model computation; zeta-phase exception.Merged3.7 (discrete path stays active; the float ban was revised by D37), 3.8, 3.12 and 3.1
D33Delegated owner release for the first A2 pilot.RetiredOne-off; superseded by D40.
D34Revised attention and memory sequence: reranker-first read plus a D19 object-store crate.Merged5.8 (the approved sequence, kept in NOW.md)
D35A seed-2 packet re-issue is required before any seed-2 go.RetiredSuperseded by D39.
D36GitHub Pages keeps the last good deploy until a D11 WebAssembly engine lands.Merged2 (web client) and 3.6; its "browser serving counts as CPU model compute" clause is replaced, and the legacy crates are repaired (2.4).
D37Float is legal in offline training only, with a reported export gap.Kept3.7; the owner's reason for the bans is quoted in 1, and archived sheets are handled in 4.5.
D38D5 split into D5-a (residency) and D5-b (per-token sparsity).Kept3.9
D39M1 closing bar, reachability gate, post-qualification sequence, lab self-direction.Merged4.8 (bar (d) replaced), 4.2, 5.8 and 5.3
D40Owner-identity phrases are typed by the owner personally.Kept5.1 (the K16 ratification is a retired one-off)
D41One-time offline donor corpus exception (distill-d1), on binding conditions.Kept3.10 (sole exception), 5.1 and 5.8
D42The owner adopts the charter and answers eight checkpoint questions.Kept (as the adoption record)The charter itself; see the change log.

Tally

Counting the rows above (excluding the I1 to I5 row and D42): 14 decisions kept, 15 merged and 14 retired, which is 43 decision entries from D0 to D41 including D0-b. This is a count of the table, derived from the live index in DECISIONS.md; it is not a separate record.

Where it stands

ItemStateSource
CharterAdopted 19 October 2026.CHARTER.md; change log
Live decision indexEach entry keeps its heading, a one-sentence summary and a fate line.docs/integration/DECISIONS.md
Full original textPreserved unchanged in the archive.archived original
Rule-by-rule mappingWorking document of 258 individual rules to charter clauses, kept in the audit directory.rule-map.md

Go deeper