Skip to content

Enforce coordination change-risk authority boundaries - #2830

Merged
EHotwagner merged 11 commits into
mainfrom
feature/coordination-change-risk-mitigation
Aug 22, 2026
Merged

EHotwagner merged 11 commits into
mainfrom
feature/coordination-change-risk-mitigation

Conversation

@EHotwagner

Copy link
Copy Markdown
Contributor

Summary

  • centralize command ownership and typed review/delivery lifecycle decisions
  • require completion and candidate self-host receipts before shared-state transitions
  • add always-reporting change-completeness CI and recoverable receiver-delivery receipts
  • commit the complete SDD work model, observed evidence, verification, and ship-ready projections

Scope

The implementation directly changes the .github coordination authority. FS.GG framework and product workspaces are affected when they consume the shared coordination tooling or release workflows; ordinary product code is not changed.

Validation

  • full Release test suites: 2,539 tests, 0 failures
  • engine parity through shim: 605 assertions, 0 failures
  • shim boundary parity: 86 assertions, 0 failures
  • coordination guards: 32 assertions, 0 failures
  • compatibility slices: 15 assertions, 0 failures
  • change-completeness route: 119 focused tests, 0 failures
  • SDD evidence: 39/39 observed obligations supported
  • SDD verification: 78/78 findings ready
  • SDD ship verdict: shipReady, 0 warnings, 0 blockers

Risk controls

  • standalone done remains nonterminal; typed delivery --apply owns completion
  • explicit candidate engines cannot write without stable-host verification
  • release recovery verifies immutable journals and per-receiver receipts before promotion
  • expensive engine CI remains path-sensitive behind an unfiltered required completeness context

@EHotwagner
EHotwagner merged commit 7f46a25 into main Aug 22, 2026
93 checks passed
@EHotwagner
EHotwagner deleted the feature/coordination-change-risk-mitigation branch August 22, 2026 19:09
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