docs(eudi): pitch deck — Consent Wallet for the EHDS (use-case track)#73
Open
ma3u wants to merge 1 commit into
Open
docs(eudi): pitch deck — Consent Wallet for the EHDS (use-case track)#73ma3u wants to merge 1 commit into
ma3u wants to merge 1 commit into
Conversation
…72) 9-slide 16:9 deck + speaker notes for the EUDI Wallet Hackathon use-case/pitch track. Drafted via a multi-agent workflow (3 framings -> 4-persona jury -> synthesis -> adversarial fact-check). Fact-check corrected a material legal framing: EHDS Ch. IV secondary use is HDAB-permit + opt-out, not GDPR Art. 9(2)(a) opt-in consent; the wallet exercises the citizen's opt-out/consent right, it is not the legal basis. Revocation framed honestly as an auditable access-boundary re-check (status-list is roadmap). Includes a Q&A defense crib and a content-agnostic deck.json -> PDF renderer. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
6 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pitch deck — Consent Wallet for the EHDS (EUDI Wallet Hackathon, use-case track)
Deliverable for issue #72 (use case / pitch), backed by the implementation in #22.
What's here
docs/submissions/eudi-wallet-hackathon-2026/EUDI-Consent-Wallet-Pitch.pdf— 9 × 16:9 slides (hero + 8), real product screenshots on the cold-open, demo and why-us slides.speaker-notes.md— 3-minute timing plan, per-slide notes, a Q&A defense crib, and a real-vs-roadmap table.deck.json+make_deck.js— content-agnostic renderer (deck.json→deck.html→ PDF via the repo'suiPlaywright). Editdeck.json, re-run.README.md— file map + regeneration + provenance.How it was made
Multi-agent workflow: 3 framings (demo-first / regulation-first / citizen-story) → 4-persona jury (SPRIND innovation · BSI/eIDAS security · EHDS health-policy · pitch coach) → synthesis → adversarial regulatory fact-check.
Material correction the fact-check caught
The synthesized draft framed EHDS secondary use as GDPR Art. 9(2)(a) opt-in consent gated by the wallet — which is wrong and would be fatal in front of a BSI/health-policy jury. EHDS Chapter IV secondary use is actually HDAB-permit + a citizen opt-out right (no reason needed; opt-in consent is mainly for genetic data). Verified independently against the European Commission and legal sources.
The deck now frames the wallet as the citizen's verifiable channel to exercise their EHDS rights (opt-out by default, consent where the law requires) — not the legal basis. Revocation is framed honestly as an auditable access-boundary re-check (cryptographic status-list = roadmap), the verifier as the hosted EUDI reference verifier, and scope as a static schema today (dynamic per-study = roadmap).
All data synthetic; all orgs fictional (AlphaKlinik Berlin, PharmaCo Research AG, MedReg DE).
Closes part of #72.
🤖 Generated with Claude Code