R1.2 verify-provenance — fixture preview

Owner pixel-visual check. Fixture data — not a live surface. The same GatedWriteProvenanceCard renders on the public verify page once Z+D land the gated-write fields on the transparency-log entry.

1 · Clean gated write

All seven gates pass; nucleus signature verified. The canonical happy path — what a real logged entry looks like.

OPEN

Validated & signed write

This write was validated by the SEIF reliability pipeline and signed into the transparency log.

Object-model anchor

nucleus_root (object-model HEAD)9f2c41a7b8e0d36c5a14f9b2e7c80d6143a9f5b2c8e1d04a7f3b6c92e85d10f4
manifest_sha2563a1d7e90c4b25f86a0e1d9c73b48f25160a7c9e3d8b14f06a25c7e93b1d8046f
nucleus signatureOPENsigned ✓ (verifiable via seif verify)
signature.algorithmed25519
signature.key_fingerprint49CCC301ECF0A67C
signature.scope_versionSCOPE_V2
signature.signed_at2026-05-21T05:30:00Z
signature.public_key (hex)b3662df64d295eadef47c982d67678707edb5aa9b3662df64d295eadef47c982d67678707edb5aa9b3662df64d295ead
signature.signed_hash (hex)7a1c3e9d05b8462f0a9c7b1e63d840f29a5c8e7b34106d9f2a8c5b07e91d3f600

Reliability pipeline (G0–G5 + secret-scan)

7 passed of 7 gates.

  • G0-substrateOPEN
  • secret-scanOPEN
  • G1-coherenceOPEN
  • G2-doc-codeOPEN
  • G3-integrityOPEN
  • G4-nucleusOPEN
  • G5-signingOPEN

2 · Passed with advisories

Passes, with the two heuristic gates (coherence assertion-guard, prose drift) advisory. Advisories are shown as advisory, not failures.

OPEN

Validated & signed write

This write was validated by the SEIF reliability pipeline and signed into the transparency log.

Object-model anchor

nucleus_root (object-model HEAD)c70b9a3e15d8462f0a9c7b1e63d840f29a5c8e7b34106d9f2a8c5b07e91d3f62
manifest_sha2561f8c2a905d7e34b6c081f9a4e2b7d56038c1a9e7b540d2f86a93c7e015b8d240
nucleus signatureOPENsigned ✓ (verifiable via seif verify)
signature.algorithmed25519
signature.key_fingerprint49CCC301ECF0A67C
signature.scope_versionSCOPE_V2
signature.signed_at2026-05-21T05:31:42Z
signature.public_key (hex)b3662df64d295eadef47c982d67678707edb5aa9b3662df64d295eadef47c982d67678707edb5aa9b3662df64d295ead
signature.signed_hash (hex)c12a905d7e34b6c081f9a4e2b7d56038c1a9e7b540d2f86a93c7e015b8d24011

Reliability pipeline (G0–G5 + secret-scan)

5 passed · 2 advisory of 7 gates.

  • G0-substrateOPEN
  • secret-scanOPEN
  • G1-coherenceSYNCadvisory

    1 assertion-guard REVIEW (non-blocking)

  • G2-doc-codeSYNCadvisory

    prose drift in 1 doc section

  • G3-integrityOPEN
  • G4-nucleusOPEN
  • G5-signingOPEN

3 · Degraded (defensive render)

A non-clean verdict / failed signature. A real logged entry should never reach this state (only PASS writes are logged) — included to verify the honest, non-affirmative copy renders.

ERROR

Provenance not confirmed

This write carries one or more failed reliability gates — it is not a clean signed write.

Object-model anchor

nucleus_root (object-model HEAD)00aa11bb22cc33dd44ee55ff66007788990011223344556677889900aabbccdd
manifest_sha256ddccbbaa00998877665544332211009988776655443322110000aa11bb22cc33
nucleus signatureOPENsigned ✓ (verifiable via seif verify)
signature.algorithmed25519
signature.key_fingerprint49CCC301ECF0A67C
signature.scope_versionSCOPE_V2
signature.signed_at2026-05-21T05:30:00Z
signature.public_key (hex)b3662df64d295eadef47c982d67678707edb5aa9b3662df64d295eadef47c982d67678707edb5aa9b3662df64d295ead
signature.signed_hash (hex)0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff

Reliability pipeline (G0–G5 + secret-scan)

6 passed · 1 failed of 7 gates.

  • G0-substrateOPEN
  • secret-scanOPEN
  • G1-coherenceOPEN
  • G2-doc-codeOPEN
  • G3-integrityOPEN
  • G4-nucleusOPEN
  • G5-signingERROR

    nucleus signature invalid