Skip to content

Restart EdgeMech under M5 CLAW with unreviewed edges first - #226

Draft
realmarcin wants to merge 3 commits into
implement/content-review-20261119from
ops/m5-edge-review-restart-20261120
Draft

realmarcin wants to merge 3 commits into
implement/content-review-20261119from
ops/m5-edge-review-restart-20261120

Conversation

@realmarcin

@realmarcin realmarcin commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

The user requested M5 CLAW resume EdgeMech to completion with unreviewed occurrences first, then reassess previously reviewed occurrences using LBNL services. The prior production order required the retained100 reassessment before expansion.

This registers the new CLAW assignment, explicitly replaces only that cohort-order dependency, and freezes an exhaustive, disjoint baseline A/B partition. It preserves scientific calibration, exact-runtime/evidence checks, candidate-correction verification and measured scaling. It requires actual worker library access and one persisted unreviewed canary before batches, immutable historical reviews, durable continuation checkpoints and full-target completion accounting.

Separate read-only review identified #223 and #224 before repair; re-review passed. This is a documentation/dispatch change with no executable-code changes. Initial head945c421 passed automated checks in run44675683681.

CLAW accepted the exact request hash and registered the task. After the user's explicit approval, the isolated coordinator accepted its assignment and recorded an active native continuation goal. Its first separate preparation worker is prepared at the same reviewed head and awaits its own exact folder-trust decision; no library/canonical canary or scientific coverage is claimed.

The missing historical census was recovered into private M5 staging: a verified single-partition canary preceded the remaining copy, and full checksum comparison reported no differences across 904 files / 8,044,208,003 bytes. The correct original graph archive was also recovered: its three TSVs match their manifest-declared SHA256 and sizes, and the manifest matches its separately pinned hash. Review finding #229 records and corrects that provenance distinction. Controlled source-path restoration, maintained census replay and baseline A/B freeze remain coordinator work. The startup record retains the earlier failed/blocked attempts and hashed private receipts. Operational helper-provenance issue #228 remains open; original helper bytes are preserved in the reviewed, unmerged CLAW PR #1299.

Based on unmerged #214. The canonical CLAW generic EdgeMech review hooks remain disabled; this is a named native-workflow coordination assignment, not a capability-flag bypass or merge authorization.

Fixes #223.
Fixes #224.
Fixes #229.

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