Repository navigation
Conversation
Signed-off-by: Srinivasa Consultants <78673153+dinakarjs@users.noreply.github.com>
This branch has not been deployed
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
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 journal in #144 deliberately leaves lost acknowledgements unresolved. Propose an operator-led authenticated readback flow that can establish matching inclusion without turning timeout or an unsigned negative lookup into permission to resubmit.
This is an informative design-only draft on current main. It specifies conservative unknown states, archival and transactional reconciliation boundaries, and future positive/negative/crash/concurrency cases. It asks maintainers to choose the readback API, identity/key-rotation policy and retry contract before implementation. No runtime files from #144 are included; no witness is contacted, no automatic retry or deployment is enabled, and #144 is not closed.
Validation: manually checked against #144's exact-bytes/trust-policy identity and documented limitations; git diff --check passes. No executable behavior changed, so no runtime test result is claimed. AI-assisted with Codex; DCO signed.