Skip to content

D-CTX-7: GadamerRevision as a candidate evidence writer of EpistemicState5 - #1379

Merged
AdaWorldAPI merged 2 commits into
mainfrom
claude/zen-planck-pldzo7
Oct 7, 2026
Merged

AdaWorldAPI merged 2 commits into
mainfrom
claude/zen-planck-pldzo7

Conversation

@AdaWorldAPI

@AdaWorldAPI AdaWorldAPI commented Oct 7, 2026 •

Copy link
Copy Markdown
Owner

This proposes one declared, versioned candidate writer for ISS-NO-EVIDENCE-WRITER-FOR-EPISTEMIC-STATE. It does not close the issue: whether a writer like this belongs in production is still open.

What the probe does

examples/revision_epistemic_writer_probe.rs tracks the claim "pixel P is a material boundary" in one MailboxSoA CausalEdge64 row.

  • A source is one Moore direction of P, read from the resident palette tile only.
  • Each cycle:
    1. takes the start-of-cycle copy of the row through MailboxSoaView;
    2. presents the cycle's encounters to GadamerRevision;
    3. settles the code with a declared transition;
    4. writes it with write_row in cycle k, so cycle k+1 reads it.
transition V1 when, in this cycle
3 OBSERVED → 7 ASSOCIATED ≥ 2 roots the revision admitted with IncreaseEligible, from readings where the neighbour differs
7 → 3 the revision returns ContradictionPreserved on the claim (a complete Moore check finds all eight neighbours the same)

Bits 59..63 are written as one joint code (spare() << 2 | truth_raw(), the #1370 reading), never one half alone. Every write lands on a code EPI_LAW declares. Codes 3 and 7 also agree with D-GSO-7a's band reading (Open → Associated).

Measured

check result
trajectory: render only, one source, two sources, tile rewritten + complete check codes 3, 3, 3, 7, 3; eligibility OBS, OBS, OBS, OBS|STRATIFY, OBS
360 rendered witnesses proposing the claim never move the code in either direction: they carry no independent root, so the revision never admits them
one direction repeated 50 times one root; no promotion
a reading where the neighbour is the same not counted as support
complete check counts only its differing roots: 3 promote alone; 1 does not; 2 promote under V1, not V2
V2 (needs 3 roots) refuses what V1 accepts
fields touched only bits 59..63
restart from to_le_bytes continues identically
heap 0 allocations per cycle
one source in cycle k + another in k+1 never combine (missing state, pinned by a test)

12 tests. All 8 disable runs fail as they should:

  • adopt every revision;
  • give render witnesses their own roots;
  • count encounters instead of roots;
  • count a same-material reading as support;
  • don't carry the horizon within the cycle;
  • skip demotion;
  • write only half of the code;
  • count all roots of a complete check (the Codex finding, fixed in 0b1a7ec).

Two of those disables passed on the first draft, which exposed weak tests:

  • The probe's own supports flag kept the render out, rather than the revision. The flag is now a mask of supporting roots, and the render would count every root it carried. It carries none, so only the missing root keeps it out.
  • No fixture admitted more than one root per encounter. The complete-check tests now tell roots and encounters apart.

Board

🤖 Generated with Claude Code

https://claude.ai/code/session_01U5ZJLtEBxeLPKX1pLRkHhc

…tate5

Addresses ISS-NO-EVIDENCE-WRITER-FOR-EPISTEMIC-STATE with one declared,
versioned candidate; the production decision stays open. One MailboxSoA
CE64 row tracks "pixel P is a material boundary". Each cycle reads the
start-of-cycle copy through MailboxSoaView, presents its encounters to
GadamerRevision, and settles the code by transition V1 (3 -> 7 on >= 2
admitted Differs roots, 7 -> 3 on ContradictionPreserved); the code is
written in cycle k and read in k+1. Bits 59..63 are written as one joint
code (the #1370 reading); every write is a code EPI_LAW declares.

Rendered witnesses propose the claim but carry no root, so the revision
never admits them and they never move the code. One source repeated is
one root; cross-cycle corroboration is pinned as missing state. 11 tests,
7 disable runs red.

Board: D-CTX-5 and D-CTX-6 -> Shipped (#1367); D-CTX-7 row and entry.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01U5ZJLtEBxeLPKX1pLRkHhc
@coderabbitai

coderabbitai Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Warning

Review limit reached

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

Next included review available in 42 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 2 included reviews currently available. Your 59 included PR review attempts over the past 7 days set your current allowance at 2 reviews per hour.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: c4ffdc32-9d4b-4761-b524-e0a076fc24cb
📥 Commits

Reviewing files that changed from the base of the PR and between 3e8fda2 and 0b1a7ec.

📒 Files selected for processing (6)
  • .claude/board/STATUS_BOARD.md
  • .claude/board/entries/2026-10-07-ctx7-revision-writer-for-epistemic-state.md
  • .claude/board/entries/README.md
  • crates/cognitive-shader-driver/Cargo.toml
  • crates/cognitive-shader-driver/examples/README.md
  • crates/cognitive-shader-driver/examples/revision_epistemic_writer_probe.rs
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.


Comment @coderabbitai help to get the list of available commands.

@cursor

cursor Bot commented Oct 7, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: 14d6303b-9b8e-4cc4-87b7-a52ffd889310)

@AdaWorldAPI
AdaWorldAPI marked this pull request as ready for review October 7, 2026 09:59
@cursor

cursor Bot commented Oct 7, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: d3db3a51-c9f6-4a17-bccb-40ea16bf0500)

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 7, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-07T10:01:03.609721Z 0602e2c Draft marked ready
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@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: 0602e2cbc3

ℹ️ 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".

Codex review on #1379: a CompleteCheck with one Differs and seven Same
readings admitted eight new roots and added all eight to earned_support,
so it promoted under V1 and V2. The encounter now returns the mask of
its supporting roots and settle counts only admitted roots inside it.
New test: one differing neighbour does not promote, two promote under
V1 and not V2. 12 tests, 8 disable runs red (incl. the reported bug).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01U5ZJLtEBxeLPKX1pLRkHhc
@cursor

cursor Bot commented Oct 7, 2026

Copy link
Copy Markdown

Bugbot couldn't run - usage limit reached

Bugbot is counted against Cursor usage for this user or team, and this run hit a usage or spend limit.

A user or team admin can review and increase usage limits in the Cursor dashboard.

(requestId: ccac3b98-8fbc-44cb-b50b-a44dfd1f6db8)

@AdaWorldAPI
AdaWorldAPI merged commit 37ca06f into main Oct 7, 2026
11 checks passed
AdaWorldAPI pushed a commit that referenced this pull request Oct 7, 2026
…esian V1)

Replaces the hand-assigned ten-code #1370 codebook with the dense product
the two old fields already formed: raw5 = topology | certification << 2,
CausalTopology ordinals x P7a certification codes, 24 meaningful states,
8 reserved (certification 6/7). Validity is only certification < 6;
IndirectUnknown x Causes and Unknown x Causes are meaningful (procedure is
the affordance law's job). OBSERVED is dropped: observation is evidence,
not a coordinate.

- contract: Topology2, Certification3, per-factor facts, derived
  COMPILED_FACTS_V1, factor updates (with_topology/with_certification);
  the legacy translation table is gone (P7a + topology is identity packing).
- causal-edge: with_topology is the canonical topology-factor writer (no
  longer deprecated); the TrustTexture / historical-band / untyped writers
  stay deprecated for bypassing the declared reading.
- affordance law compiles per factor; state = topology & certification.
- probes remapped: #1379/cycle/nextstate 3/7 -> 0/4 (Direct x Open /
  Direct x Associated), affordance fixtures 25/5/17 -> 10/9/21, streamdto
  7 -> 4; P7a stamps every contract; entropy_topology migrated to the
  canonical projection.
- #1378 probe: canonical == topology lens + P7a decode over all 32 codes
  (24 agree / 0 disagree / 8 reserved), derived table == rules, frontier
  cases 22/23, legacy-reading class refuses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_0177nSSyQaXqbNuGR1vMXXN6
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