openclaw/reporting-governance-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

reporting-governance: document single-notice settlement guardrail

Browse Source
This commit is contained in:
Eve
2026-05-08 12:16:15 +08:00
parent a188b0390a
commit 36bc00cc3f
3 changed files with 70 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
docs/specs/reporting-governance-adapter-interface.md
View File

@@ -651,11 +651,21 @@ Examples:
Verify orchestrated chain behavior.
For the **current runtime contract**, treat the reference chain as a **single notice settlement path**, not a generalized multi-notice aggregation framework.
That means:
- the runtime may promote overall truth state to `acked` only when the observed terminal set for that one notice path is fully acked
- `acked + pending` must remain non-`acked`
- `acked + blocked` must remain non-`acked`
- any future multi-notice aggregation semantics must be introduced as a separate contract slice, not inferred from this one
For example:
- runner -> queue -> dispatcher -> bridge -> sender -> `acked`
- runner -> queue -> dispatcher -> bridge -> `pending_external_send`
- runner -> queue -> dispatcher -> bridge -> `blocked`
- mixed observed outcomes `acked + pending` -> overall state must **not** promote to `acked`
- mixed observed outcomes `acked + blocked` -> overall state must **not** promote to `acked`
## Roadmap impact