Skip to content

[Pipeline 8/12] add optional clean-sample bounds during integration - #283

Draft
AnikethCheluva wants to merge 1 commit into
codex/arc-rebuild/03-flow-token-conditioningfrom
codex/arc-rebuild/04-flow-clean-sample-bounds
Draft

AnikethCheluva wants to merge 1 commit into
codex/arc-rebuild/03-flow-token-conditioningfrom
codex/arc-rebuild/04-flow-clean-sample-bounds

Conversation

@AnikethCheluva

@AnikethCheluva AnikethCheluva commented Oct 23, 2026 •

Copy link
Copy Markdown

Stack context

Pipeline 8/12 of the Cartesian ARC arrival-v2 review. Main stack: #311 (38 levels). Optional projection: #317, outside the main tip's ancestry. Parent: codex/arc-rebuild/03-flow-token-conditioning.

What and why

add optional clean-sample bounds during integration

Needed / not carried forward

This level supplies the capability named above. The integrated stack has one canonical Cartesian codec, fixed independent-stream execution and model-declared decode context; it does not carry duplicate E1/legacy codecs or selectable race/joint-distance algorithms. Independent planar/simulation codecs remain outside this cleanup. No tests, fixtures or local verification scripts are committed. No training job or hardware session is launched.

Compatibility and verification

The full integration intentionally changes ARC targets: source starts at the next frame, row zero is incoming travel, and timing is measured from current proprio. Fresh compatible normalization and new experiment identities are required. Old checkpoints retain their recorded sources; same tensor width does not make them compatible. Complete experiment menus activate at the config integration level; intermediate helper PRs are not production launch candidates.

External CPU checks: 114 codec checks; 457 staged-codec checks; 93 inference/evaluator context checks; 282 open-loop oracle checks; 27 diagnostic checks; numerical post-tokenization statistics and next-frame source/preflight checks. All 325 current YAMLs resolve; 24 ARC and four baseline config-to-decoder context constructions pass. The optional projection extension passed 14 dedicated checks. These are integration receipts, not claims that every intermediate PR ran a complete training or hardware test.

AnikethCheluva commented Oct 23, 2026 •

Copy link
Copy Markdown
Author

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

This stack of pull requests is managed by Graphite. Learn more about stacking.

@AnikethCheluva
AnikethCheluva force-pushed the codex/arc-rebuild/03-flow-token-conditioning branch from d37212d to 446927f Compare October 23, 2026 03:57
@AnikethCheluva
AnikethCheluva force-pushed the codex/arc-rebuild/04-flow-clean-sample-bounds branch from b2c5220 to 91ec971 Compare October 23, 2026 03:57
This was referenced Oct 23, 2026
@AnikethCheluva
AnikethCheluva force-pushed the codex/arc-rebuild/03-flow-token-conditioning branch from 446927f to ec74a07 Compare October 23, 2026 20:06
@AnikethCheluva
AnikethCheluva force-pushed the codex/arc-rebuild/04-flow-clean-sample-bounds branch from 91ec971 to 1aee8ac Compare October 23, 2026 20:06
@AnikethCheluva AnikethCheluva changed the title flow: add optional clean-sample bounds during integration [Pipeline 2/11] add optional clean-sample bounds during integration Oct 23, 2026
@AnikethCheluva
AnikethCheluva force-pushed the codex/arc-rebuild/04-flow-clean-sample-bounds branch from 1aee8ac to 9f67e16 Compare October 23, 2026 20:38
@AnikethCheluva AnikethCheluva changed the title [Pipeline 2/11] add optional clean-sample bounds during integration [Pipeline 8/14] add optional clean-sample bounds during integration Oct 23, 2026
@AnikethCheluva
AnikethCheluva force-pushed the codex/arc-rebuild/03-flow-token-conditioning branch from 1fd91d3 to 161e4c5 Compare October 23, 2026 22:02
@AnikethCheluva
AnikethCheluva force-pushed the codex/arc-rebuild/04-flow-clean-sample-bounds branch from 9f67e16 to 0e6f25d Compare October 23, 2026 22:02
@AnikethCheluva AnikethCheluva changed the title [Pipeline 8/14] add optional clean-sample bounds during integration [Pipeline 8/12] add optional clean-sample bounds during integration Oct 23, 2026
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.

1 participant