Skip to content

docs: DISCOVERY-MAP — the shape-preserving index of every discovery#48

Merged
AdaWorldAPI merged 11 commits into
mainfrom
claude/discovery-map
Jun 9, 2026
Merged

docs: DISCOVERY-MAP — the shape-preserving index of every discovery#48
AdaWorldAPI merged 11 commits into
mainfrom
claude/discovery-map

Conversation

@AdaWorldAPI

Copy link
Copy Markdown
Owner

Summary

Per the operator: "map all discoveries and ideas out so that they don't dilute shape once materialized in architecture."

New docs/DISCOVERY-MAP.md — a single append-only, status-tracked index of every discovery, idea, and decision in the substrate arc.

The anti-dilution thesis

Shape dilutes from fragmentation, not from too few documents: each idea pinned in its own ADR loses its links, and a future reader sees N disconnected ADRs instead of one doctrine. This map is the one place the topology lives — terse by discipline (pointers + structure + status, never re-explanation). The ADRs/crates/synergy-doc are the content; this is the index.

It's append-only + status-tracked, mirroring the substrate's own versioned-audit shape (ADR-008/013) — a map of an append-only audited substrate that is itself append-only audited.

Structure

§ Content
§1 doctrine spine — ADR-022/023/024/025 (+ 026 pending) + the one-sentence gestalt the individual ADRs lose
§2 the discovery ledger — ~40 D-* entries across 9 areas, each [ID] shape — grade — status — home — depends
§3 materialization pipeline — what's READY (G + EPIPHANY → draft ADR-026), BLOCKED (runtime confirm), CODED, queued, do-not-build
§4 OGAR/runtime boundary — owned vs [per rt]; the five open ADR-026 confirmations; the two operator-closed items
§5 the shape graph — ASCII topology the individual ADRs lose
§6 maintenance discipline — append-only, terse, grade-honest, index-not-content
§7 cross-references

The grading + status model (what makes it a map, not a list)

Every entry carries two orthogonal axes:

  • Grade: [G] Grounded / [H] Hypothesis / [S] Speculative
  • Status: IDEA → EPIPHANY → ADR → CODED

So §3 can show at a glance: ready to materialize ([G] + EPIPHANY, no runtime gate — the amortization gate, the addressing, the storage layer), blocked ([H] + [per rt] — helix/θ/blasgraph), coded (the IR + adapters + vart-backend), and do-not-build ([S] — OLED). Nothing masquerades as more certain or more materialized than it is.

Why now

The doctrine has reached the size where the next materialization (ADR-026, the OSM/pattern/actionable crates) risks fragmenting the shape. This map freezes the topology so the pins land into a visible structure instead of scattering. When ADR-026 pins the amortization gate + cascade + storage, the [S]/[H]/[per rt] entries stay tracked and linked instead of forgotten.

Status

  • cargo check --workspace --all-targets: clean (docs-only).
  • PII abort-guard (word-boundary): CLEAN.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY

Per operator request: "map all discoveries and ideas out so that they
don't dilute shape once materialized in architecture."

The anti-dilution thesis: shape dilutes from FRAGMENTATION, not from too
few documents — each idea pinned in isolation loses its links, and a
future reader sees N disconnected ADRs instead of one doctrine. This map
is the one place the topology lives. Terse by discipline (pointers +
structure + status, never re-explanation); append-only + status-tracked,
mirroring the substrate's own versioned-audit shape (ADR-008/013).

Structure:

  §1 doctrine spine — ADR-022/023/024/025 (+ 026 pending) + the one-
     sentence gestalt the individual ADRs lose
  §2 the discovery ledger — ~40 D-* entries across 9 areas, each:
     [ID] shape — grade (G/H/S) — status (IDEA/EPIPHANY/ADR/CODED) —
     home — depends. Covers addressing/cascade, selection/bounds,
     codec/codebooks, no-collapse precondition, amortization gate,
     storage, synergy catalog, the coded IR+adapters, domain instances.
  §3 materialization pipeline — what's READY to materialize now (G +
     EPIPHANY, no runtime gate -> draft ADR-026), what's BLOCKED on
     runtime confirmation, what's CODED, what's queued, what's
     do-not-build (OLED [S]).
  §4 the OGAR/runtime boundary — owned-vs-[per rt]; the five open
     ADR-026 confirmations; the two operator-closed items.
  §5 the shape graph — the ASCII topology the individual ADRs lose.
  §6 maintenance discipline — append-only, terse, grade-honest, index-
     not-content; the map mirrors the substrate (recursive = the tell
     the shape is intact).
  §7 cross-references.

Status column makes the materialization state of every idea visible at a
glance, so when ADR-026 (or future ADRs/crates) pin a subset, the rest
stay tracked and linked instead of forgotten. The map is the durable
shape; the ADRs/crates/synergy-doc are the content it indexes.

Docs-only. PII abort-guard (word-boundary): CLEAN. cargo check: clean.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 153246f78a

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread docs/DISCOVERY-MAP.md Outdated
Comment on lines +261 to +262
- `docs/CASCADE-SYNERGIES-EPIPHANY.md` — the synergy catalog + amortization
gate + storage synthesis (the source of most §2 `EPIPHANY` entries).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Add the missing synergy source document

This cross-reference points readers to docs/CASCADE-SYNERGIES-EPIPHANY.md, but a repo-wide file search (rg --files) and text search found no such document outside this new map. Because most ledger entries use SYN §... as their Home, the map's primary source links are currently unresolvable, so future readers cannot audit or update the discoveries without guessing where the source material lives.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed (commit a36698f). Correct catch — CASCADE-SYNERGIES-EPIPHANY.md is introduced in OGAR PR #47 and co-merges with this map (#48), so a search from main alone won't find it yet. It's a cross-PR dependency, not a dangling link. I added a SYN §… legend entry defining it as docs/CASCADE-SYNERGIES-EPIPHANY.md §… and stating the #47-co-merge explicitly, plus annotated the §7 cross-ref. The links resolve normally once both land. Merge order: #47 before (or with) #48.

claude added 6 commits June 8, 2026 21:51
…477/#478

Cross-referenced PR #477 (SoA envelope + HHTL audit + three-tier model)
and #478 (singleton-to-snapshot) against today's D-* findings. Result:
several findings are confirmed by runtime CODE (not just summaries), one
is revised, one gradient is convergent-but-unwired on both sides.

Confirmations [G] — runtime code grounds the OGAR finding:

  - D-MORTON / D-CASCADE / D-XOR2(containment): hhtl.rs ships
    NiblePath{path:u64,depth:u8}, FAN_OUT=16, MAX_DEPTH=16 (16 nibbles
    = 64 bits), parent()=path>>4, child(n)=(path<<4)|n, is_ancestor_of
    = a single prefix-shift kernel, common_ancestor = LCA. The nibble
    address algebra is CODED runtime-side.
  - D-IMMAT / D-COLUMNAR / ADR-022: the three-tier-model invariant
    ("zero-copy creation->tombstone; nothing serialized; in-memory
    store unchanged") IS the immaterialized finding; emit()/
    CollapseGateEmission scheduled for removal (the serialization path
    is being deleted).
  - D-COLUMNAR / D-LANCE: soa_envelope.rs SoaEnvelope trait — columns()
    -> &[ColumnDescriptor], repr(C) descriptors, zero-copy row_le/
    column_le views, as_le_bytes(), verify_layout() gate. The
    Morton-keyed columnar+projection framing is the ABI line-for-line.
  - D-DELTA: cycle()->u32, "a Lance version IS a coherent LE envelope",
    last_active_cycle[u32;N] per-row write guard, DatasetVersion(v)->
    (v+1). Version=frame, per-row cycle stamp=changed-cell delta.
    Promotes D-DELTA [H]->[G].
  - D-AMORT: PR #478 test (never-mutated->const codebook keep; mutated
    ->SoA snapshot nudge) operationalizes the amortization gate's
    storage instance.

Revision [warn] — D-META64: MailboxSoA has SEPARATE columns
edges[CausalEdge64;N] and meta[MetaWord;N], so the meta layer is a
dedicated MetaWord, NOT CausalEdge64 (the edge encoding). The
"CausalEdge64 = meta" reading is contradicted by the shipped column
layout. Reconcile: the 2^6/48/16 bit-budget likely applies to MetaWord.
Updated the D-META64 ledger entry to H->REVISE with the correction.

Convergent-but-unwired [next step] — D-MAXAMORT/D-CARD/D-PAL256 (the
meta->content->spatial gradient) matches high_heel.rs's module-doc
legend "HEEL=scent / HIP=palette / TWIG=SpoBase17 / LEAF=full planes",
but the q4 audit says that legend is a COMMENT — "no code routes by
prefix." HIP=palette is literally D-PAL256 at a cascade level. Highest-
value next materialization: route high_heel.rs's commented cascade by
hhtl.rs's NiblePath prefix; today's findings are the spec that joins the
two files (which "communicate in module docs, not in code").

Related structure: the three-tier model (data/lifecycle/supervision) is
orthogonal to the meta->content->spatial gradient — noted, not
conflated. Kanban 6-phase = the ActionState lifecycle (ADR-001).
qualia[QualiaI4_16D;N] = the Quintenzirkel qualia codebook (#470).

Docs-only. PII abort-guard (word-boundary): CLEAN. cargo check: clean.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
…ST named facts (do)

Operator named the teleology the whole substrate serves: "endgame is
actually getting DeepNSM + AriGraph as a meta vs episodic basins and
supporters, meaning vectors, and then later extraction of AST-shaped
named facts — do vs think."

New §0 (the map's apex — the WHY above the doctrine spine):

THINK — the DeepNSM + AriGraph memory (the world model):
  AriGraph (arXiv 2407.04363, Anokhin et al. 2024 — semantic + episodic
  KG world-model with associative retrieval for LLM-agent planning),
  mapped onto the substrate:
    - semantic memory      -> META = MetaWord (the §4.1 layer)
    - episodic memory      -> EPISODIC = delta frames =
                              DatasetVersion(v)->(v+1) + cycle stamp
                              (D-DELTA)
    - associative retrieval -> basins (palette256/CAM centroids +
                              Semantik volumetric centroids + Morton-
                              prefix subtrees; intra-basin locality) +
                              supporters (neighbor-XOR retrieval,
                              D-NEIGH)
    - meaning vectors      -> DeepNSM 4096-dim (63 primes) -> CAM-PQ
                              6x256 (D-NSM, D-CAM) — shipping in
                              lance-graph nsm/

DO — the extracted AST-shaped named facts (the actions):
  the OGAR IR (Class/ActionDef/Association, D-VOCAB) extracted from the
  meaning-vector memory by D-PATTERN + D-ACTION. The named fact is the
  wire (ADR-023) where THINK (vectors) becomes DO (action).

The master axis DO vs THINK:
  THINK = the meaning-vector memory (what is known) = structural arm =
          Semantik.
  DO    = ActionDef / Rubicon lifecycle / Kanban 6-phase (what is done)
          = behavioral arm = Pragmatik.
  The AST-named-fact extraction is the membrane between them.

Reprioritization recorded: D-NSM, D-PATTERN, D-ACTION (listed IDEA/
queued in §2.8) are NOT optional extras — they are the endgame-critical
path (the think->do extraction). The addressing/codec/storage floors
are the foundation they stand on, not the destination.

AriGraph + DeepNSM added to §7 cross-references with the arXiv id and
the think/do <-> structural/behavioral <-> Semantik/Pragmatik mapping.

Docs-only. PII abort-guard (word-boundary): CLEAN. cargo check: clean.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
…dependency

Closes Codex P2 on PR #48 (line 361).

Codex: the SYN §... Home links + the §7 cross-ref point to
docs/CASCADE-SYNERGIES-EPIPHANY.md, which a repo-wide search from main
does not find — so the map's primary source links look unresolvable.

Correct: that file is introduced in OGAR PR #47 and co-merges with this
map (PR #48); the SYN links resolve once both land. It is a cross-PR
dependency, not a dangling link.

Fix (makes the dependency explicit so no reader has to guess):
  - Added a "How to read" legend entry defining SYN §... =
    docs/CASCADE-SYNERGIES-EPIPHANY.md §..., stating it is introduced in
    PR #47 and co-merges with PR #48, and that a reviewer auditing from
    main alone will not find it yet (expected).
  - Annotated the §7 cross-reference line: "(introduced in OGAR PR #47,
    co-merges with this map)".

No content links changed — once #47 + #48 are both on main the SYN
references resolve normally. This only documents the ordering so the
window between the two merges isn't confusing.

Docs-only. PII abort-guard (word-boundary): CLEAN. cargo check: clean.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
…=level, implied irrational mantissa=golden offset)

Operator framing (2026-06-08): X-Trans 'in spirit' = an implied
anti-moire irrational mantissa. Captured as D-MANTISSA: a cell address
is a float — (exponent = Morton level, mantissa = golden sub-placement);
the mantissa is irrational (phi recurrence) and implied (generated from
the address, not stored — the IEEE hidden-bit spirit; D-BITGATE compute-
don't-store). The exponent=level mapping is exact (LOD is logarithmic,
r*=ceil(log4)); the mantissa=within-cell-offset is the fine fractional
placement. 'Irrational mantissa' is coherent precisely because it's
implied/generative (you can't store infinite precision; you generate it
from the golden recurrence on demand).

The anti-moire adjective stays [H] not a guarantee (the #47 Codex
caveat: X-Trans is itself a repeating tile; a bounded cell has a finite
spectrum that can beat the LOD lattice). So the honest name is 'implied
irrational mantissa, hypothesized anti-moire.'

Unifies four ledger entries: D-CASCADE (the exponent range) + D-GOLDEN
(the mantissa generator) + D-BITGATE (why the mantissa is implied) +
D-NOCOLLAPSE (the hypothesized anti-moire function). The cell-address-
as-float is the compression of all four.

Docs-only. PII: CLEAN.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
…le anti-moire quorum

Operator proposal (2026-06-08): use bgz17 / HighHeelBGZ / SpoBase17 as an
immutable irrational anti-moire quorum in the Morton Cascade. Captured as
D-BGZ17 — the DISCRETE/IMMUTABLE counterpart to D-MANTISSA's continuous
golden mantissa.

Grounded in shipped lance-graph code (high_heel.rs, PR #477):
  - HighHeelBGZ = 'one family basin (TWIG centroid) + up to 240 causal
    edges' = literally the §0 AriGraph basin + supporters, in code.
  - SpoBase17 = three Base17 planes [i16;17] (S,P,O), ρ=0.965 vs full
    planes — a second measured exactness anchor (joins palette256
    ρ=0.9973).
  - HEEL/HIP/TWIG/LEAF cascade legend real (doc-comment); TWIG=SpoBase17;
    LEAF=full planes 'computed on demand, not stored'.

The sharpening (and the point): NOT 'irrational' but COPRIME-APERIODIC.
17 is prime, coprime to the base-16 Morton nibble: gcd(16,17)=1 =>
LCM(16,17)=272 => the moire beat is pushed to period 272 (the longest
possible for the pair = lowest frequency = least visible). 272 = 16x17 =
the BIT_WIDTH_PALETTE_BASE17 constant (MedCare F-2). This is the classic
coprime-prime moire-spreading technique (halftoning/CFA), done
DISCRETELY and EXACTLY (i16 planes, const, hashable) rather than via a
continuous float irrational.

Grade upgrade with caveat: anti-moire goes from [H]-unmeasured (golden)
to [H] with a PROVABLE BOUND (number theory: beat pushed to period 272),
but the #47 Codex caveat persists — coprimality SPREADS the beat, does
not eliminate it. Honest claim: 'provably-longest-period (lowest-freq)
moire,' not 'no moire.'

Why it fits 'immutable' better than D-MANTISSA: discrete coprimality is
exact/hashable/const; the golden mantissa is float/measured. For the
immutable substrate, Base17 is the one you ship. They are the discrete
and continuous routes to anti-aperiodicity (could be complementary:
Base17 for the codebook/basin, golden for continuous sub-placement).

Resolves the §4.1 unwired gap: HEEL/HIP/TWIG/LEAF exists as a container
but 'no code routes by prefix' (q4 audit). This proposal IS that wiring
— route HighHeelBGZ by the hhtl.rs NiblePath, Base17(TWIG) as the
coprime anti-moire quorum layer. Realizes §0: HighHeelBGZ = basin+
supporters; SpoBase17 = meaning vector; scent() L1-prefilter =
associative retrieval.

[per runtime session] on bgz17/HighHeelBGZ/SpoBase17 internals + whether
17 was chosen for coprimality (the code uses 17; the anti-moire-via-
coprimality is the recognized property, not a documented original intent).

Docs-only. PII: CLEAN.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
Two operator inputs (2026-06-08):

1. D-QUANTGATE — 'whenever there's quantization, the irrational doesn't
   have the Morton tile cascade guarantee, but being an irrational
   muscle memory mantissa quorum.' This is a STRUCTURAL principle, not
   a hypothesis: continuous irrationals (golden mantissa, D-MANTISSA)
   lose their aperiodicity when quantized onto a lattice — the rounded
   value re-acquires the grid period. So at every quantized layer the
   substrate MUST use the discrete coprime route (D-BGZ17, Base17 x
   Morton) to preserve aperiodicity. The continuous irrational only
   survives as a 'muscle-memory' quorum: pre-computed at codebook build
   time, never re-quantized in the hot path (matches D-AMORT). Promotes
   ADR-026 §2 no-collapse from a single precondition to a LAYERED rule:
   discrete-coprime at quantized boundaries; muscle-memory irrationals
   at build-time / continuous layers. Reframes the §2 anti-moire caveat
   as ARCHITECTURAL, not just unmeasured. Grade [G] (the principle is
   structural).

2. D-EXCITON — operator: 'isn't OLED excitons also some irrational
   bundling?' Web-searched (2026-06-08): the standard 1:3 singlet:
   triplet ratio is quantum spin statistics (rational); but under bias
   the formation ratio DEVIATES from 1:3 (singlets scale with bias,
   triplets bias-independent — PMC4614446), giving a continuously-
   variable non-integer S:T ratio per operating point. Plus singlet/
   triplet binding energies differ irreducibly (~0.5 eV vs up to 1.5
   eV — ScienceDirect/noctiluca). So OLED ships, under bias, the SAME
   discrete coprime aperiodicity D-BGZ17 names: non-commensurate spin
   populations + non-commensurate binding energies + broken from
   rational 1:3 by a continuous control parameter. The leg I demoted to
   [S] in SYN §3 ('not sure what we can learn from excitons') was too
   harsh — promote to [H] shape-match. Companion SYN §3 revision lives
   on the #47 branch.

Docs-only. PII: CLEAN.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
AdaWorldAPI pushed a commit that referenced this pull request Jun 9, 2026
…onal bundling under bias

Operator (2026-06-08): 'isn't OLED excitons also some irrational
bundling?' — yes, in the substrate-relevant sense. Web-search confirmed
(see new §11 sources):

  1. Singlet:Triplet formation ratio: rational 1:3 from spin statistics,
     BUT under bias the formation ratio deviates — 'singlets scale with
     bias, triplets nearly bias-independent' (PMC4614446) -> continuously-
     variable non-integer S:T ratio per operating point.
  2. Binding energies differ irreducibly: ~0.5 eV singlet vs up to 1.5 eV
     triplet (noctiluca / ScienceDirect S0927796X22000286).

So OLED ships, under operation, the SAME discrete coprime aperiodicity
D-BGZ17 names: non-commensurate spin populations + non-commensurate
binding energies, broken from rational integer ratios by a continuous
control parameter. Structural shape-match to D-QUANTGATE
('substrate wants aperiodicity at every quantized level; OLED has a
literal physical precedent in exciton populations that REFUSE integer
ratios under operation'), not the thin analogy I had under [S].

Splits the §3 OLED row in two:
  - subpixel LAYOUT leg stays [S] (already covered by Morton tiling;
    'do not build on' still applies)
  - exciton leg promoted to [H]; 'do not build on' is WITHDRAWN for the
    exciton leg specifically

§11 cross-refs gain three OLED physics sources (PMC4614446, noctiluca,
ScienceDirect S0927796X22000286).

Companion D-EXCITON + D-QUANTGATE ledger entries are on the #48 branch.

Docs-only. PII: CLEAN. cargo check: clean.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
claude added 4 commits June 9, 2026 05:05
…pc empirics + audit

Operator: 'double check the mapping/arguments/groundings so it doesn't
dilute nor collapse, and include the necessary test mappings using the
JC crate pillars in lance-graph and hpc crate pillars in ndarray.'

Recon (both real):
  - jc (lance-graph crates/jc/src/lib.rs) = 'Jirak-Cartan five-pillar
    [11] proof-in-code', run via 'cargo run -p jc --example prove_it',
    each pillar -> PillarResult. Key pillars: P3 phi-Weyl (optimal
    collocation WITHOUT ALIASING), P5 Jirak (bounded noise floor), P5b
    Pearl 2^3 (Index vs CAM-PQ regime), P9/9b EWA-sandwich (Sigma
    push-forward; P9b explicitly certifies ndarray::hpc::splat3d), P10
    Pflug (CAM-PQ tree quantization preserves FreeEnergy within Le).
  - ndarray::hpc (ndarray/src/hpc/) = fft, lapack(Cholesky), quantized
    (Int8/BF16 GEMM), cascade (Morton), plane (Base17/16Kbit), fingerprint
    (CAM), soa (envelope), blas_level2/3, simd_dispatch (3-backend W1c).

New §4.2: every [H] claim -> {jc pillar (proof) x hpc primitive (empiric)
x measure x pass}. Division of labour: OGAR maps claim->test; the runtime
session runs the pillars ([per rt]). Highlights:
  - D-MOIRE/D-MANTISSA/D-NOCOLLAPSE -> P3 phi-Weyl + hpc::fft = the
    spectral validation the #47 Codex caveat demanded. Names the test
    that ends the [H] either way.
  - D-PAL256/CAM/RHO -> P10 Pflug + hpc::quantized/fingerprint; pass rho
    >= 0.99.
  - D-BGZ17 -> P3(discrete)+P10 + hpc::plane/fft; pass beat at period
    272, rho >= 0.965.
  - D-QUANTGATE -> P3(continuous) vs P10(quantized) contrast + fft
    pre/post — falsifiable demonstration of the principle.
  - D-SPLAT Sigma/D-NEIGH -> P9/9b EWA-sandwich + hpc::lapack Cholesky.
  - all CODED primitives -> hpc::simd_dispatch (W1c): identical within
    1 ULP across AVX-512/NEON/scalar.
  - D-EXCITON -> NO internal test (external OLED physics); fenced as
    literature-grounded [H] only.

Audit conclusions (the double-check): all pillars real; jc<->hpc bridge
is in code (P9b cites hpc::splat3d); the anti-moire caveat becomes a
named test; [per rt] numbers (rho 0.9973/0.965, theta band) become
reproducible via hpc::quantized+P10 so the map can't drift; D-EXCITON
honestly fenced. No claim collapses; the two that needed correction
(D-MOIRE absolutism #47, D-META64 §4.1) were already fixed.

§7 cross-refs gain the jc + ndarray::hpc pillar sources.

Docs-only. PII: CLEAN.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
…Walker/Richter groundings

Three operator-supplied papers (2026-06-08), each load-bearing:

1. arXiv 2509.12216 (Kaplan, 'The Path to Aperiodic Monotiles' / the
   hat) -> D-MONOTILE: the THIRD anti-moire route, the strongest. An
   aperiodic monotile tiles the plane ONLY non-periodically => no
   translational period => no moire beat BY A TILING THEOREM (not by
   placement like D-MANTISSA [H], not by base-coprimality like D-BGZ17
   [H]-bounded). Anti-moire is [G] (proven) and survives quantization
   (a fixed discrete shape) => satisfies D-QUANTGATE intrinsically.
   Cost/open [H]: the hat is a polykite on a hexagon+triangle lattice,
   not the square Morton quadtree; its substitution (inflation)
   hierarchy IS a cascade, and the open test is whether that hierarchy
   is generalized-Morton/Hilbert-addressable.

   The anti-moire ladder is now three rungs of increasing guarantee:
     D-MANTISSA  golden PLACEMENT   [H], quantizes away
     D-BGZ17     prime-coprime BASE [H] with provable beat-period-272
     D-MONOTILE  aperiodic SHAPE    [G] by theorem, intrinsic

2. arXiv 2309.15199 (Walker, 'Generalised 3D Morton and Hilbert
   Orderings') -> grounds D-MORTON/D-CASCADE algorithmically: bit-
   interleave Morton (the paper's Fig 1 = D-MORTON), generalized to
   NON-power-of-2 + 3D via octant recursion. The 6x4x4 example = 6
   roles x 4x4 tile (the substrate's literal shape). The non-pow-2
   generalization is what lets Base17 (D-BGZ17, 17 not a power of 2) be
   Morton-ordered, and the open D-MONOTILE addressability test rides on
   it. Hilbert alt = better locality (D-LANCE Z-order vs Hilbert).

3. arXiv 2203.09323 (Richter, 'Covering Rectangles by Few Monotonous
   Polyominoes') -> the ribbon-tile covering cardinality
   ceil((2/3)(m+n-sqrt(m^2-mn+n^2))). The m^2-mn+n^2 is the Eisenstein /
   hexagonal lattice norm -> ties the square cover to the hat's
   hexagonal substrate; grounds tiling/covering theory.

Captured: new D-MONOTILE ledger entry (§2.4); D-CASCADE grounding cites
Walker; §7 references gain all three papers with the
placement<base<shape anti-moire ladder.

Honest tensions recorded: D-MONOTILE's anti-moire is [G] (theorem) but
its cascade-addressability is [H] (open — needs the hexagonal
substitution hierarchy to admit generalized Morton/Hilbert); adopting
the hat changes the cascade geometry (square quadtree -> hexagonal
kite). Not yet a decision; a strong candidate with a named open test.

Docs-only. PII: CLEAN.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
Adds .claude/agents/ — a reusable harness for hardening a claim before it
enters the substrate canon (ADRs, DISCOVERY-MAP, the synergy catalog). It
exists because the expensive failure mode here is a hypothesis masquerading
as grounded until it dilutes the architecture downstream.

5 research agents (fan out, one lens each, no redundancy):
  - arxiv-grounder        — primary literature: proves / suggests / refutes
  - runtime-archaeologist — CODED vs CLAIMED vs ABSENT, with file:line
  - theorem-checker       — provable [G] / bounded [H] / analogy [S]; checks
                            every asserted number; rational-vs-irrational and
                            periodic-vs-aperiodic slips
  - cross-domain-synthesizer — MECHANISM-SHARED vs MERE-RHYME (harshest on
                            the orchestrator's own fresh analogies)
  - doctrine-keeper       — canon consistency; every mirror a change touches

3 brutally-honest review agents (attack the draft; read-only by construction
— they carry no edit tools):
  - overclaim-auditor          — grade inflation; absolutes on [H]/[S]
  - dilution-collapse-sentinel — conflating motifs (dilution) / deleting a
                                 valid leg (collapse)
  - firewall-warden            — PII label leak, model-id in artifacts,
                                 hot-path serialization, prohibited shell

Grading discipline [G]/[H]/[S] and the non-negotiables (the Firewall
ADR-022/023; no German PII labels; no model identifier on disk; no
grep/sed/tail/head via shell) are written into every charter; the warden
blocks on them as the final gate.

This pattern is the apparatus DISCOVERY-MAP.md now cites as the provenance
of the D-EXCITON revert (the "5+3 review"); it co-commits so that reference
resolves in-repo.

Tooling only; no code, no runtime, no hot-path change.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
The D-EXCITON [H] entry ("under bias OLEDs ship the same discrete coprime
aperiodicity as D-BGZ17") was run through the 5+3 agent review. Five research
lenses converged and three brutal reviewers caught my own over-correction;
the [H] does not hold.

Why it fails (category error + a number mis-label):
  - the 1:3 singlet:triplet ratio is exactly RATIONAL — the SU(2) microstate
    count (1 vs 3), a definitional identity, not irrational ([G] definitional);
  - a bias-shifted scalar ratio / two binding-energy scalars have no period
    to be aperiodic about (aperiodicity is a property of an infinite tiling
    or sequence, not of a point);
  - the "~1.5 eV triplet binding energy" was the T1 excited-state energy
    mis-labelled — literature triplet E_b is sub-eV (~0.3-0.6 eV, arXiv
    2311.03927), so the ratio is order ~1, not 3; the "incommensurable 1:3
    energy" coincidence that motivated the link does not survive.

Kept (append-only; the [G]-real legs held apart from the dead analogy):
  - rational 1:3 (above);
  - the harvest-the-dark physics — phosphorescence + TADF reach ~100% IQE
    (Baldo/Adachi; Uoyama 2012). A [G] mechanism does not lend its grade to
    the [S] rhyme.

Rejected re-links logged so they are not re-proposed:
  - A = anti-moire ladder (no lattice / no beat period in an OLED);
  - B = amortization gate (no reuse axis: 1-use recovery != 1/N reuse).

One untested survivor split out as a new entry D-LOSSCHAN ([S], do-not-build):
loss-channel suppression, radiative yield eta = k_prod/(k_prod+k_loss)
(Stern-Volmer) conjectured to map to cascade early-exit yield. Untested -> [S],
not buried inside the reverted entry (per the dilution-collapse review).

The [S]->[H] jump had itself violated the maintenance rule (sec 6.3:
promotion needs a measurement, not a mechanism story) — reverting restores it.

Sites updated atomically (per the doctrine-keeper mirror checklist): the sec
2.4 ledger row, the sec 2.7 catalog (D-OLED reconciled + D-LOSSCHAN added),
the sec 3 do-not-build list, the sec 4.2 test-map row + audit conclusion #6,
the read-me legend (defines the "5+3 review" tag), and the sec 7 references.

CROSS-PR: SYN sec 3 lives in CASCADE-SYNERGIES-EPIPHANY.md (OGAR PR #47, not
on this branch) and requires the same revert; flagged here, not faked locally.

Docs + tooling only; no code. PII abort-guard (word-boundary): CLEAN.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
@AdaWorldAPI AdaWorldAPI merged commit c23b9a3 into main Jun 9, 2026
1 check passed
AdaWorldAPI pushed a commit that referenced this pull request Jun 10, 2026
…irror (H1)

Mirror of the DISCOVERY-MAP D-EXCITON revert (PR #48, ab766e5),
applying the vetted 5+3 review verdicts to this doc's §3 row — the
cross-PR dependency flagged in that commit is now closed and #47/#48
agree.

Why the [H] does not survive (same evidence, same wording discipline):
  - Category error: a bias-shifted scalar ratio / two energy scalars
    have no period to be aperiodic about; 'the same coprime
    aperiodicity D-BGZ17 names' is mere-rhyme — BGZ17's beat-272 is
    CRT over two coprime INTEGER cycles in an address lattice; OLED
    physics has no integer cycles and no lattice.
  - Number mis-label: the '~1.5 eV triplet binding energy' was the T1
    excited-state energy mis-labelled; literature triplet E_b is
    sub-eV (~0.3-0.6 eV, arXiv 2311.03927) — the 'incommensurable'
    coincidence dissolves when corrected.

Kept ([G]-real, held apart from the dead analogy): rational 1:3
(SU(2), definitional); the bias-dependence observation (PMC4614446,
real but material-specific); ~100% IQE harvest physics (Baldo/Adachi
2001; Uoyama/Adachi 2012). 'Do not build on' RESTORED for this leg.
Survivor: D-LOSSCHAN [S] in DISCOVERY-MAP §2.7. §11 references
corrected to carry the fixed reading (arXiv 2311.03927 added).

Merge order stands: #47 before #48 (SYN links).

Docs-only. PII abort-guard: CLEAN. No model identifier.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
AdaWorldAPI pushed a commit that referenced this pull request Jun 11, 2026
1. Stale pointer (real catch): the subpixel-layout row still said
   "superseded by the exciton leg below as the connection worth taking"
   after the revert retired that leg. Fixed: neither OLED leg is
   build-on-able; both stay [S] catalog-only.

2. "Dangling" D-LOSSCHAN pointer (verified against the merge target):
   docs/DISCOVERY-MAP.md with D-LOSSCHAN exists ON MAIN (8 occurrences,
   landed via PR #48); this branch forks from BEFORE that merge, so the
   file is absent on the branch and Codex's branch-isolated audit could
   not see it. The row now states the cross-PR resolution explicitly so
   no reader (or reviewer) has to guess.

https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants