feat: add draft data, gap analysis report, and workspace config
This commit is contained in:
@@ -0,0 +1,28 @@
|
||||
# Revision Plan
|
||||
|
||||
## Blocking changes
|
||||
|
||||
- Add a normative requirement that receivers evaluate authorization before honoring a rollback request.
|
||||
- Add a normative replay-handling rule tying request identity, idempotency token, and stale-request rejection together.
|
||||
- Add a compact state-transition table covering normal failure, rollback request, partial success, irreversible outcome, and compensation-required cases.
|
||||
- Add one non-normative end-to-end example flow with concrete identifiers and a partial-success outcome.
|
||||
|
||||
## High-value improvements
|
||||
|
||||
- Clarify rollback-set structure and how transitive scope is represented or reported.
|
||||
- Strengthen `rollback-result` requirements for partial-success, refused, and irreversible outcomes.
|
||||
- Tighten the abstract, introduction, and terminology wording to sound more like an actual I-D.
|
||||
- Either define the coordinator role more clearly or remove it from this version.
|
||||
|
||||
## Deferred items
|
||||
|
||||
- Binding to a specific execution-evidence substrate
|
||||
- Human override or operator approval flow
|
||||
- Registries for failure classes and rollback outcomes unless implementation feedback requires them
|
||||
|
||||
## Draft order for next iteration
|
||||
|
||||
1. Revise abstract and terminology.
|
||||
2. Revise Sections 5 through 8 for authorization, replay, scope shape, and state transitions.
|
||||
3. Add non-normative example flow.
|
||||
4. Revisit Security, Privacy, IANA, and References after the protocol text settles.
|
||||
Reference in New Issue
Block a user