Skip to content

feat: add capability-state fusion - #95

Draft
douglas-grishen wants to merge 1 commit into
codex/sparse-collective-scale-v2from
codex/capability-state-fusion-v1
Draft

feat: add capability-state fusion#95
douglas-grishen wants to merge 1 commit into
codex/sparse-collective-scale-v2from
codex/capability-state-fusion-v1

Conversation

@douglas-grishen

Copy link
Copy Markdown
Contributor

Summary

  • add the public, provider-neutral @agentplat/collective-runtime/capability-state entrypoint
  • fuse bounded local Trust, role, capacity, reachability and recovery projections with strict canonical contracts
  • retain logical-time and source-revision high-water state behind a CAS store
  • narrow offer, bid, award, acceptance/execution and certified-recovery candidates without granting authority or replacing native selectors
  • document the architecture, security boundary and production composition

Safety and compatibility

  • opt-in node port; nodes without it preserve existing behavior
  • missing, expired, future, rolled-back, conflicting or malformed state fails closed
  • content-free local projections only; no global membership materialization
  • no assignment, lease, fence, grant or effect authority is created by fusion
  • public terminology is provider-neutral and industry-standard

Validation

  • pnpm build
  • pnpm run test:unit — 829 tests, 0 failures
  • pnpm run type-check:public
  • pnpm run audit:public
  • pnpm run verify:release
  • pnpm run verify:pack
  • focused capability-state tests, including CAS restart/rollback and the bounded 100,000-peer overlay profile

Stack

This PR is intentionally based on codex/sparse-collective-scale-v2 (#94) so its diff contains only Capability-State Fusion V1. Retarget to main after #94 lands.

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