docs(synergies): REVERT §3 OLED exciton leg [H]→[S] — close the live canon fork on main#49
Merged
Merged
Conversation
…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
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 2c4e0dcb82
ℹ️ 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 on lines
+507
to
+508
| Uoyama/Adachi *Nature* 492:234, 2012). Survivor: D‑LOSSCHAN `[S]` | ||
| (DISCOVERY‑MAP §2.7). |
There was a problem hiding this comment.
This adds D-LOSSCHAN/DISCOVERY-MAP §2.7 as the place readers should go for the surviving OLED claim, but this repository currently has no docs/DISCOVERY-MAP.md and no D-LOSSCHAN occurrence outside this new text (checked find docs -iname '*DISCOVERY*' and rg -n "D-LOSSCHAN|D-EXCITON|DISCOVERY-MAP"). In this docs-only canon update, that leaves the only survivor pointer unresolvable, so the revert no longer gives readers an actionable source of truth.
Useful? React with 👍 / 👎.
Owner
Author
There was a problem hiding this comment.
Codex correct on the symptom — branch-isolated audit can't see DISCOVERY-MAP.md. Verified the target: the file exists on main (8 occurrences of D-LOSSCHAN, landed via #48 yesterday); this branch forks from before that merge. The pointer now states the cross-PR resolution explicitly in 33605bc so a reviewer doesn't have to reproduce the trace.
| | palette256 ↔ indexed‑color codec palette | **[G]** | HEVC‑SCC + VVC ship an indexed‑palette mode (the codec's own ≤‑256‑ish codebook for screen content) | | ||
| | palette256 ↔ OLED subpixel emission (layout) | **[S]** | OLED PenTile RGBG layout is a palette‑on‑a‑lattice for *perceived* resolution; the subpixel *layout* is shape‑match only and already covered by Morton tiling. Kept [S] but **superseded by the exciton leg below** as the OLED→substrate connection worth taking. | | ||
| | OLED **excitons** ↔ **irrational bundling under bias** | **[H — promoted from prior [S], 2026‑06‑08]** | **Operator: "isn't OLED excitons also some irrational bundling?"** — yes, in the sense the substrate cares about. Measured (web sources, see §11): (1) the rational 1:3 singlet:triplet ratio is quantum spin statistics, **but** under bias the formation ratio *deviates* — *"the generation efficiency of singlets scales with the bias, whereas that of triplets is nearly bias‑independent"* (PMC4614446), giving a **continuously‑variable non‑integer S:T ratio per operating point**. (2) Singlet/triplet binding energies differ irreducibly: *"~0.5 eV (singlet) vs up to 1.5 eV (triplet)"* (noctiluca / ScienceDirect S0927796X22000286). So OLED ships, under bias, **the same discrete coprime aperiodicity D‑BGZ17 names**: non‑commensurate spin populations + non‑commensurate binding energies, broken from the rational integer ratio by a continuous control parameter. The shape‑match is structural, not analogical: a substrate that wants aperiodicity *at every quantized level* (D‑QUANTGATE) has a literal physical precedent in OLED exciton populations *exactly because* they refuse to sit on integer ratios under operation. The recommendation from the prior version ("do not build on") **is withdrawn for the exciton leg specifically** — it remains for the *subpixel layout* leg above. | | ||
| | OLED **excitons** ↔ **irrational bundling under bias** | **[S — REVERTED from [H], 2026‑06‑09 by the 5+3 agent review]** (mirror of the DISCOVERY‑MAP D‑EXCITON revert, PR #48) | The 2026‑06‑08 `[H]` promotion below this line does **not** survive review — kept for the record, struck in substance. **(1) Category error (theorem‑checker):** a bias‑shifted *scalar* ratio and two energy *scalars* have no period to be aperiodic about — aperiodicity is a property of an infinite tiling/sequence, not of points in ℝ; "the same discrete coprime aperiodicity D‑BGZ17 names" is MERE‑RHYME: D‑BGZ17's beat‑272 comes from two coprime *integer cycles* in an address lattice (CRT), and OLED physics offers no integer cycles and no lattice. **(2) Number mis‑label (arxiv‑grounder):** the "~1.5 eV triplet *binding* energy" is the **T1 excited‑state energy mis‑labelled** — literature triplet E_b is sub‑eV (≈0.3–0.6 eV, arXiv 2311.03927); corrected, the ratio is order ~1, not 3, and the motivating "incommensurable" coincidence dissolves. **Kept (`[G]`‑real, held apart from the dead analogy):** the exactly‑rational 1:3 (SU(2) microstate count — definitional); the bias‑dependence observation (PMC4614446 — real but material‑specific, carries no aperiodicity); the ~100% IQE harvest physics (Baldo/Adachi; Uoyama 2012). **"Do not build on" is RESTORED** for this leg. The one untested survivor lives as **D‑LOSSCHAN `[S]`** (loss‑channel suppression ↔ cascade early‑exit, Stern‑Volmer form) in DISCOVERY‑MAP §2.7. | |
There was a problem hiding this comment.
After this row reverts the exciton analogy to [S] and restores “Do not build on”, the immediately preceding OLED layout row still says it is “superseded by the exciton leg below” as the connection “worth taking.” In the §3 table those two statements now conflict, so readers are still directed to build on the same leg this revert is meant to retire.
Useful? React with 👍 / 👎.
Owner
Author
There was a problem hiding this comment.
Caught — that's a real stale pointer. The subpixel row was still routing readers to the leg this PR retires. Both OLED legs now read [S] catalog-only in 33605bc.
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
This was referenced Jul 6, 2026
AdaWorldAPI
pushed a commit
that referenced
this pull request
Jul 7, 2026
…(W1)
W1 of the odoo→odoo-rs transpile arc. Replace the deprecated odoo-rs
corpus witness with real, unmodified Odoo 19 source as the kausal-parity
consume witness.
Fixture: addons/account/models/account_payment_term.py (AdaWorldAPI/odoo
2c78d5f1, byte-identical + PROVENANCE.md). Drives the shipped frontend
end to end: ruff_python_spo::extract_from_source →
compile_graph_python::<OdooPort> → lift_actions.
Pin (tests/odoo_kausal_parity_probe.rs, hand-derived from the source):
- 8/8 @api.depends compute methods across two models round-trip to
ActionDef.kausal == Some(KausalSpec::Depends { paths }) verbatim,
including the 9-path _compute_example_preview (two co-computed fields
→ ONE ActionDef, one per method not per field).
- 8 plain methods assert kausal == None (facts-only guard).
ruff_python_spo added as dev-dependency floating on main (D-NEVER-PIN-BUMP).
Scope: Arm A only; arms B (constrains/onchange) + D (computed.stored)
out of scope pending ruff #49. Ledger: D-KAUSAL-CONSUME-PIN-ODOO.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NSfzujtWL1BnHgnJGAhg9N
AdaWorldAPI
pushed a commit
that referenced
this pull request
Jul 7, 2026
…#49 The rebase onto main (which carries arms B+D via ruff #49 / D-ATC2-KAUSAL-RUFF-GATED) surfaced that @api.constrains methods now get KausalSpec::Constrains. Extend the W1 witness to pin all 3 constrains methods verbatim (was: asserted kausal==None). Now 11/11 kausal (8 depends + 3 constrains); _check_lines moved from the plain-methods list to the Constrains pin. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NSfzujtWL1BnHgnJGAhg9N
AdaWorldAPI
pushed a commit
that referenced
this pull request
Jul 7, 2026
…(W1)
W1 of the odoo→odoo-rs transpile arc. Replace the deprecated odoo-rs
corpus witness with real, unmodified Odoo 19 source as the kausal-parity
consume witness.
Fixture: addons/account/models/account_payment_term.py (AdaWorldAPI/odoo
2c78d5f1, byte-identical + PROVENANCE.md). Drives the shipped frontend
end to end: ruff_python_spo::extract_from_source →
compile_graph_python::<OdooPort> → lift_actions.
Pin (tests/odoo_kausal_parity_probe.rs, hand-derived from the source):
- 8/8 @api.depends compute methods across two models round-trip to
ActionDef.kausal == Some(KausalSpec::Depends { paths }) verbatim,
including the 9-path _compute_example_preview (two co-computed fields
→ ONE ActionDef, one per method not per field).
- 8 plain methods assert kausal == None (facts-only guard).
ruff_python_spo added as dev-dependency floating on main (D-NEVER-PIN-BUMP).
Scope: Arm A only; arms B (constrains/onchange) + D (computed.stored)
out of scope pending ruff #49. Ledger: D-KAUSAL-CONSUME-PIN-ODOO.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NSfzujtWL1BnHgnJGAhg9N
AdaWorldAPI
pushed a commit
that referenced
this pull request
Jul 7, 2026
…#49 The rebase onto main (which carries arms B+D via ruff #49 / D-ATC2-KAUSAL-RUFF-GATED) surfaced that @api.constrains methods now get KausalSpec::Constrains. Extend the W1 witness to pin all 3 constrains methods verbatim (was: asserted kausal==None). Now 11/11 kausal (8 depends + 3 constrains); _check_lines moved from the plain-methods list to the Constrains pin. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NSfzujtWL1BnHgnJGAhg9N
AdaWorldAPI
pushed a commit
that referenced
this pull request
Jul 7, 2026
…(W1)
W1 of the odoo→odoo-rs transpile arc. Replace the deprecated odoo-rs
corpus witness with real, unmodified Odoo 19 source as the kausal-parity
consume witness.
Fixture: addons/account/models/account_payment_term.py (AdaWorldAPI/odoo
2c78d5f1, byte-identical + PROVENANCE.md). Drives the shipped frontend
end to end: ruff_python_spo::extract_from_source →
compile_graph_python::<OdooPort> → lift_actions.
Pin (tests/odoo_kausal_parity_probe.rs, hand-derived from the source):
- 8/8 @api.depends compute methods across two models round-trip to
ActionDef.kausal == Some(KausalSpec::Depends { paths }) verbatim,
including the 9-path _compute_example_preview (two co-computed fields
→ ONE ActionDef, one per method not per field).
- 8 plain methods assert kausal == None (facts-only guard).
ruff_python_spo added as dev-dependency floating on main (D-NEVER-PIN-BUMP).
Scope: Arm A only; arms B (constrains/onchange) + D (computed.stored)
out of scope pending ruff #49. Ledger: D-KAUSAL-CONSUME-PIN-ODOO.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NSfzujtWL1BnHgnJGAhg9N
AdaWorldAPI
pushed a commit
that referenced
this pull request
Jul 7, 2026
…#49 The rebase onto main (which carries arms B+D via ruff #49 / D-ATC2-KAUSAL-RUFF-GATED) surfaced that @api.constrains methods now get KausalSpec::Constrains. Extend the W1 witness to pin all 3 constrains methods verbatim (was: asserted kausal==None). Now 11/11 kausal (8 depends + 3 constrains); _check_lines moved from the plain-methods list to the Constrains pin. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NSfzujtWL1BnHgnJGAhg9N
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this PR exists (merge FIRST — it closes a live canon fork on
main)PRs #47 and #48 merged one minute apart (2026-06-09 05:55) — in the right order, but before the cross-PR mirror revert existed. Result:
maincurrently disagrees with itself:docs/DISCOVERY-MAP.md(via docs: DISCOVERY-MAP — the shape-preserving index of every discovery #48) carries the D-EXCITON revert[H]→[S](the 5+3 agent review verdict).docs/CASCADE-SYNERGIES-EPIPHANY.md(via docs: cascade-synergies epiphany capture — Morton/palette256/golden-helix convergence #47) still carries the §3 OLED[S]→[H]promotion that the review refuted.This 1-commit PR applies the vetted mirror so both docs agree.
What the revert says (same evidence, same wording discipline as #48's
ab766e5)[G]-real, held apart): the exactly-rational 1:3 (SU(2), definitional); the bias-dependence observation (PMC4614446 — real but material-specific); the ~100% IQE harvest physics (Baldo/Adachi 2001; Uoyama/Adachi 2012).[S](DISCOVERY-MAP §2.7). §11 references corrected (arXiv 2311.03927 added).Docs-only · PII abort-guard CLEAN · no model identifier.
https://claude.ai/code/session_01PBTGaPCSnnt6u3pjXpbLwY