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

14
plugins/reporting-governance/README.md
View File

@@ -224,9 +224,23 @@ This slice now has one small but testable contract path:
- truthful delivery / receipt state
- runtime execution result when explicitly requested
Current runtime contract in this repo is intentionally narrower than a future generalized aggregation model:
- **single notice settlement path only**
- one governance-triggered operator notice route is evaluated as one truth boundary
- overall truth state may promote to `acked` only when the observed terminal outcome set for that single path is fully acked
- mixed observed outcomes such as `acked + pending` or `acked + blocked` must stay non-`acked`
- this slice does **not** yet claim generalized multi-notice aggregation, fan-in settlement, or cross-notice quorum semantics
This is intentionally **planning-level end-to-end plus one adapter bootstrap layer**, not full live inline interception.
It proves contract alignment without pretending all runtime enforcement is already extracted.
What this means for implementers right now:
- treat `dispatched` / `pending_external_send` / `blocked` as honest end states unless the single notice path reaches sender-backed ack proof
- do not collapse partial success into overall `acked`
- if future work introduces multiple notice paths, that must land as a separate runtime-contract slice with its own tests
## Not yet included
This package still does **not** claim full implementation of: