Informational Fresh jira_epic: GOV-E10
Module: Cryptographic Trust & Anchoring
Source: Jira Epic GOV-E10 — "Asymmetric signing and external anchoring". Generated per LEARN-STD-002 from authoritative artefacts: the Epic is this module, its Stories are the lessons, and each Story's acceptance criteria are the lessons' learning outcomes and knowledge checks.
The story of this journey
Turning evidence integrity from hashes into cryptographic trust: real KMS signing, external anchoring, and offline verification anyone can run.
Who this is for
Primary: Platform Administrator. Also relevant to: Software Engineer.
Flow
flowchart LR
L1[GOV-310] --> L2[GOV-311] --> L3[GOV-312]
Lessons (in sequence)
| # | Lesson (source Story) | Pts | Why it matters |
|---|---|---|---|
| 1 | GOV-310 — Real asymmetric signing with KMS | 13 | Real signatures (not placeholders) make evidence independently verifiable. |
| 2 | GOV-311 — External evidence anchoring | 8 | External anchoring proves when evidence existed, independent of us. |
| 3 | GOV-312 — Offline verifier tooling | 5 | Independent, offline verification is the ultimate trust guarantee. |
How this maps (LEARN-STD-002)
- Epic GOV-E10 → this Module.
- Each Story → a Lesson (
source_artifact: jira_story), sequenced byprerequisites. - Acceptance Criteria → learning outcomes + scenario knowledge checks — quoted, not paraphrased.
Assessment & certification
Passing all 3 scenario knowledge checks completes the module. Certification (learner-progress store) is deferred to Phase 3; until then completion is tracked informally and no metrics are fabricated.