What does a signature actually bind?
A signature binds a precise message and verification context. The C3 journey exposes real signed public artifacts and native QC checks.
Implementation & contract
The C3 caller reuses checkpoint QC, validator registry and the native post-quantum signature provider.
Matching bytes, algorithm, signer authority and context are required. A digest alone does not establish the truth or availability of the named data.
Run the existing case
The local synthetic C3 run exercises its signature and certificate checks. It is not a KMS, customer key-custody service or certification of every crypto profile.
Where to read the result & proof
Open Execution details & proof for the returned proposal, votes and certificates. Native QC checks and the observation checksum have different roles.
Who uses this?
A security reviewer checks which context a signed artifact authenticates and which external facts remain unverified.