Security Validation — honest CURE surfacing

GFTCL-LION-SECURITY-001.

What the cell HONESTLY guarantees

The cell surfaces post-quantum cryptography work without claiming summit closure. MLKEMConstraint.lean and PQWalletFinance.lean are CURE-state (skeleton + algebraic tautology) — the actual ML-KEM break is Nobel-class open work on summit.mlkem.break.

The substrate CHECK enforces closes_summit = 0 on every security_validations row. The cell physically cannot lie that it closed an open summit.

What the cell DOES seal:

Walkthrough

SecurityDomainPanel → tap an implementation → SecurityValidationWalkthrough opens:

1. Implementation confirmation(impl_id, kind, version) from sealed substrate row

2. Test kindkat_conformance / constant_time / side_channel / oracle_check

3. Outcomepass | fail | inconclusive | refused (substrate CHECK enforces)

4. Honest scope reminder — touches_summit shown; closes_summit forced to 0

5. Witness sealed — append-only security_validations; signed quintet; broadcast permitted

Federation

What stays NAMED OPEN (Nobel-class)

Files

Federation cosignature: pending operator signing host (v26). Witness (sha256 of rendered body): 97223e233c630912b64d29d7a822cfd91f0bd20c4c99f0c25eb65ff8070fa513. This page serves with a substrate-honest pending-signature notice until the operator's Franklin signer cosigns it.