Skip to content

Close the resource-scope blind spot across 384 dispatch vectors - #337

Merged
aruintelligence merged 1 commit into
mainfrom
codex/dispatch-resource-cross-product
Oct 14, 2026
Merged

aruintelligence merged 1 commit into
mainfrom
codex/dispatch-resource-cross-product

Conversation

@aruintelligence

Copy link
Copy Markdown
Owner

Finding and change

The earlier 192-vector matrix caught six of seven selected source mutations. Weakening exact resource matching changed none because every rule was exact or absent. This adds an other resource-rule scope across the full existing cross-product while keeping the first 192 indices stable. All 192 new rows block before approval and callback in the reference boundary; the resource-wildcard mutant now changes all 192 new rows.

The separate Python state oracle verifies every receipt, resource binding, digest, callback, claim, and local write across 384 rows. The mutation report detects all seven selected source substitutions. The dispatch atlas now has side-by-side resource lanes, a resource filter, and proposal/rule binding details; the homepage points to the expanded atlas.

Verification

  • node pilots/action-boundary/dispatch-matrix.mjs --check
  • python3 pilots/action-boundary/verify_dispatch_matrix.py docs/action-dispatch-matrix.json
  • node pilots/action-boundary/dispatch-mutants.mjs --check
  • Boundary/vector checks, focused Node tests, links and deployment-surface checks

Scope remains finite, project-authored, and local. No provider delivery, authenticated human approval, or formal production-safety proof.

@aruintelligence
aruintelligence merged commit aa20ee6 into main Oct 14, 2026
62 checks passed
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