Skip to content

Commit 5e4c2fb

Browse files
committed
docs: add governance proof conditions note
1 parent 56ead45 commit 5e4c2fb

1 file changed

Lines changed: 26 additions & 0 deletions

File tree

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# Governance proof conditions
2+
3+
A system is governed only if it can prove, at the point where an output can bind consequence:
4+
5+
1. Valid authority existed.
6+
2. The action was within scope.
7+
3. The payload was admissible under the conditions at that time.
8+
4. The state transition was permitted.
9+
5. If not permitted, refusal occurred before mutation.
10+
6. A record proves that refusal occurred.
11+
12+
**No receipt, no proof.**
13+
14+
## Boundary
15+
16+
This note claims that a proof layer must exist at the consequence boundary.
17+
18+
It does not claim that the proof layer is tamper-proof.
19+
20+
Recursive proof integrity, receipt tamper-resistance, and proof-layer optimisation are separate design questions and are not resolved here.
21+
22+
## Inspection surface
23+
24+
This repository is an inspection surface for the execution-boundary model.
25+
26+
It does not evidence production deployment, regulatory approval, compliance certification, or third-party adoption.

0 commit comments

Comments
 (0)