threads: T19 CLOSED on the outbox-join proof; qorpe-sync accepted; T21/T22 RFCs drafted - #171
Merged
Merged
Conversation
…1/T22 RFCs drafted The adopter PoC's final leg ran: saga state in the app's OWN DbContext, fault injection proving the saga row and outbox rows commit or roll back in ONE transaction. All three host properties now proven by test — T19 moves to Closed threads. qorpe-sync flips to accepted on the owner's word (build next week, two-store rig first). Goldpath.Approvals and Goldpath.FileExchange get their RFCs (proposed) so the T21/T22 shelves are prepared; builds still wait on their Ring B triggers per the §5.1 by-product rule. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
…er decision
The owner pulled the T21/T22 Ring B triggers early ('nothing left incomplete').
Approvals: amount-laddered chains as data, four-eyes, depth-one delegation,
deadline escalation with top-rung expiry, worklist, full audit trail — 17
deterministic tests. FileExchange: rails as data with baked closures, file
contracts, idempotent (file,line) ingestion, quarantine-continues, zero-dup
replay/reprocess — 7-test planted-fault rig. Both wired into the manifest
schema and 'goldpath add feature'; RFCs flip to accepted with honest open DoD
rows (DB stores, template flags, console federation, adopter proofs).
Also lifts transitive SSH.NET past GHSA-q939-rpr3-3284 (NU1903 was red).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The published @qorpe/ui moved 4 minors ahead; the gate went red by design. Console rebuilt and 217/217 unit tests pass on 0.5.0 with the coverage floors enforced. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
The adopter PoC's final leg ran: saga state in the app's OWN DbContext, fault
injection proving the saga row and outbox rows commit or roll back in ONE
transaction. All three host properties now proven by test — T19 moves to
Closed threads. qorpe-sync flips to accepted on the owner's word (build next
week, two-store rig first). Goldpath.Approvals and Goldpath.FileExchange get
their RFCs (proposed) so the T21/T22 shelves are prepared; builds still wait
on their Ring B triggers per the §5.1 by-product rule.
Co-Authored-By: Claude Fable 5 noreply@anthropic.com