Repository navigation
feat(v0.6): establish W41 fleet mutation kernel - #151
Merged
Merged
Conversation
Introduce additive W41 fleet kinds/actions and a separate fail-closed compound requirement normalizer while preserving the v0.5 single-action path and stable legacy idempotency identity. Refs #150 Signed-off-by: Ammar Heidari <ammar@arad-itc.org>
This was referenced Sep 24, 2026
Add provider-neutral durable observation and post-cap read reservation accounting for W41. Refs #150 Signed-off-by: Ammar Heidari <ammar@arad-itc.org>
Verify restart/fencing preservation, charge-before-I/O post-cap reservations and lifetime caps for W41. Refs #150 Signed-off-by: Ammar Heidari <ammar@arad-itc.org>
Add typed outstanding-effect obligations, governed uncertainty outcomes and a live-identity resolution contract without introducing provider mutation behavior. Refs #150 Signed-off-by: Ammar Heidari <ammar@arad-itc.org>
Cover quarantine blocking, supersession tombstones, typed evidence release and immutable disposition bindings for W41. Refs #150 Signed-off-by: Ammar Heidari <ammar@arad-itc.org>
akhiabanchian
marked this pull request as ready for review
September 24, 2026 10:00
akhiabanchian
approved these changes
Sep 24, 2026
This was referenced Sep 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Authority
Implements governed W41 from #150 under admitted v0.6 planning tracker #146. Planning was admitted through #147 at protected-main merge
1c0c9be76a811a0ffe5f8a3c7620aae716389e79.This PR is intentionally draft/in-progress until the complete W41 exit evidence is present. It must not merge based on this initial slice.
Current implemented slice
Exact initial head:
452b9544906af9400b04d8b925ab574fe36dc7a1.FleetMutationAuthorizationclosed compound-requirement normalizer rather than weakening v0.5MutationAuthorization.NormalizeTargets;mutation.reconcileplus the unresolved original effect conjunction for uncertainty disposition;Remaining W41 work before ready-for-review
Durable fleet progress/checkpoints, sticky outstanding-effect obligations, observation accounting/budgets, additive SQLite/PostgreSQL persistence and recovery/concurrency tests, current-identity integration contract, reconciliation/tombstone semantics, shared conflict integration, pinned-client capability probes, replication bypass-guard foundation and full applicable CI/evidence.
Safety
All RFC-0006/ADR-0007 and inherited v0.5 invariants remain mandatory. No generic Kafka execution surface, no raw durable secret/record material, no read=>mutation implication and no provider mutation activation in W41.
Refs #150.