PROBE-REVISION-ATTENTION-VIEW-1 — preserve the cognitive layers, move the view

[AdaWorldAPI]

Thesis

This PR opens the next bounded probe after #1000:

Keep the underlying cognitive population stationary, preserve concurrent rung-tagged activity, change the semantic view through typed selectors, and retain the transformation that changed the view.

It deliberately connects two already-established architectural disciplines:

• lance-graph-java / Panama / Valhalla mask-native execution: populations stay resident, semantic descriptors compose, materialization is terminal, and bulk work lowers to predicate/mask/SIMD where appropriate.
• r2sleigh → R2IL → ruff typed behavioral IR: behavior stays typed, transformations retain provenance, and reconstruction is a first-class falsifier.

The split is:

masking       = what state becomes visible / conductive
behavioral IR = what transformation occurred

No scheduler is introduced.

Architectural target

The hinge remains:

CognitiveWork
    ↓
Kanban Evaluation
    ↓
Revision
    ↓
another cognitive pass
    OR
Rubicon Commit

The probe must not reinterpret RungElevator as a global cognitive program counter. Multiple rung-associated contributions may coexist over one cognitive state. Attention is treated as visibility/composition over those contributions, not as a serial rung transition.

Grounded starting point

The preceding source audit established that:

• RungElevator is local to one ShaderDriver and does not impose one-hot global rung occupancy.
• multiple independent rung-tagged representations already coexist;
• Revision currently has no focus/mask/scope/branch editing surface;
• Kanban phase transitions record no attention provenance;
• current mask union/intersection generally destroys contribution provenance;
• RowFocusMask, FieldMask/WideFieldMask, Locus, GapKind, and CausalTopology are heterogeneous semantic selector families, so a universal CommonMask is not established;
• WitnessLens<'a> plus existing impl Fn(usize) -> bool filtering provides a real zero-copy execution seam;
• GapKind/ReasoningGap and Locus already provide production bulk-selection surfaces;
• CausalTopology has the desired semantic variants but no production bulk selector;
• ↑n denotes remaining 256-ary address-space breadth, not rung movement;
• 6×2×8-bit is a real regular FacetCascade geometry over twelve tier bytes.

Probe law

Do not build CommonMask → opaque universal bitmap.

Test instead:

heterogeneous typed selectors
        ↓
provenance-preserving composition description
        ↓
terminal lowering
    ┌───────────┴───────────┐
    ▼                       ▼
predicate                packed mask
    │                       │
    └────── zero-copy view ─┘

The semantic composition and the execution artifact are distinct. The lowered artifact may be fused and opaque; the semantic composition must retain who contributed what.

Falsifiers

• F-PARALLEL-RUNG-1: positively demonstrate multiple meaningful rung-tagged contributions coexisting over one cognitive state, with higher-rung activity not deleting lower-rung activity. This is concurrent cognitive occupancy, not a claim of wall-clock thread parallelism.
• F-VIEW-PROVENANCE-1: compose at least two semantically distinct selectors while retaining their identities above the lowering boundary.
• F-ZERO-COPY-VIEW-1: use an existing seam such as WitnessLens<'a> + impl Fn(usize) -> bool and prove that changing the view does not materialize/copy the underlying NodeRow population.
• F-TYPED-EDIT-ROUNDTRIP-1: represent one view change as a typed transformation and require exact reconstruction: BEFORE + EDIT == observed AFTER.
• F-REVISION-FOCUS-1: if current Revision APIs cannot carry a view edit, record ABSENT; demonstrate the intended behavior only through a clearly probe-local adapter. Do not substitute RungElevator.
• F-NON-DESTRUCTIVE-1: changing the effective view must not erase the underlying concurrent contributions.
• F-HETEROGENEOUS-SELECTOR-1: preserve different selector semantics without forcing one physical representation or one universal algebra.
• F-UNKNOWN-TEXTURE: do not manufacture a CausalTopology bulk selector just to satisfy the diagram; use production-wired GapKind/ReasoningGap/Frontier and Locus first where honest.
• F-RUBICON-BOUNDARY-1: stop before claiming Commit provenance is solved. Persistence across the Rubicon remains open.

Behavioral-BPE consequence

This PR does not implement behavioral BPE. It establishes only the lossless receipt substrate required for later learning:

repeated grounded episodes
        ↓
typed attention/reasoning transformations
        ↓
recurrence detection
        ↓
behavioral compression
        ↓
reusable behavioral IR/template

The intended future unit is a recurring grounded transformation of attention/reasoning geometry, not a prose instruction or text token.

Explicit non-goals

No central scheduler. No global current rung. No serialization of R0..R9. No CommonMask. No universal NOT/XOR merely for symmetry. No CE64 layout change. No forced CausalTopology bulk wiring. No ScenarioBranch resurrection. No temporal.rs→attention mapping. No Frozen/Learned/Explore thresholds. No behavioral learner. No Rubicon persistence. No #1000 threshold tuning. No claim that RungElevator is the metacognitive controller.

Success criterion

The strongest acceptable claim is:

At probe level, one cognitive state can retain multiple rung-associated contributions while a typed, provenance-preserving selector composition is changed and lowered into a different zero-copy reasoning view. The change is reconstructible as a typed behavioral transformation. No global rung transition or central scheduler is required.

Nothing stronger.

Full falsifier charter: .claude/plans/probe-revision-attention-view-1.md.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fd2bab00-6f2a-41fb-a207-f942f5e66709

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[cursor]

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: serverGenReqId_6e939d63-c891-4189-b17a-e000422c500b)