Prove Soul verdict seal semantics
This commit is contained in:
parent
7e2e2de3ea
commit
a82466639e
5 changed files with 54 additions and 2 deletions
|
|
@ -999,6 +999,8 @@ request grants no verdict, rerun, state commit, Hands, publication, lifecycle,
|
|||
or cross-body consequence. The class guard prevents substring fallback.
|
||||
|
||||
Thirteen high-authority families are now typed; 543 substring assertions remain.
|
||||
A malicious typed fixture separately proves that commented
|
||||
`soul_verdict_authorized = false` cannot conceal an actual verdict grant.
|
||||
|
||||
The same inspection found 33 consecutive duplicate `#[cfg(test)]` attributes
|
||||
on provider constructors/writers and their re-exports. One gate already makes
|
||||
|
|
|
|||
|
|
@ -310,7 +310,7 @@ explicit malicious maintainer-approval fixture now passes as a negative proof.
|
|||
|
||||
Verification-request closure is now typed and class-guarded. Current count:
|
||||
thirteen typed high-authority families and 543 remaining substring assertions.
|
||||
Add the explicit malicious Soul-verdict fixture next.
|
||||
The explicit malicious Soul-verdict fixture now passes as a negative proof.
|
||||
|
||||
The latest structural count is 32 closure family branches, 744 remaining
|
||||
substring assertions in the closure region, and 1,284 lines in
|
||||
|
|
|
|||
Reference in a new issue