Type verification request closure semantics

This commit is contained in:
Meta Vens 2026-07-13 03:18:38 +01:00
commit 7e2e2de3ea
6 changed files with 59 additions and 42 deletions

View file

@ -990,6 +990,16 @@ grant.
Twelve high-authority families are now typed; 582 substring assertions remain.
## Verification-request prose substituted for Soul authority
`repo.verification_request` closure now parses exact typed request,
Substrate/Hands antecedent, receipt-chain, required-check, and authority
semantics. Soul owns the verdict; Mind admission remains downstream. The
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.
The same inspection found 33 consecutive duplicate `#[cfg(test)]` attributes
on provider constructors/writers and their re-exports. One gate already makes
each item test-only; the second owned nothing. The duplicates are removed.

View file

@ -308,6 +308,10 @@ Maintainer-review closure is now typed and class-guarded. Current count: twelve
typed high-authority families and 582 remaining substring assertions. The
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 latest structural count is 32 closure family branches, 744 remaining
substring assertions in the closure region, and 1,284 lines in
`closure_contracts.rs`. Do not blindly generate a struct forest for every