QR verification (§15 Q6 → §10.4.5): spec MUSTs, then show/scan/reciprocate flows #106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Sub-issue of #86. Step 1 is a spec change: §10.4.5 gains the QR MUSTs (modes, how QR payload bytes and scanned payloads cross the SDK boundary — the camera and renderer are the app's, observable flow states, reciprocation, trust written only after the peer's confirmation; CR refs). Step 2: implementation in katrix-crypto + engine, testkit corpus + an Element interop e2e on the existing chromium stack. Q6 timing is settled by the roadmap (M6 criterion 2); the D-entry records the mode scope decided with the user.
Scope decided 2026-08-21 (D55): show + scan + reciprocate (m.qr_code.show.v1, m.qr_code.scan.v1, m.reciprocate.v1). Q6 marked resolved in §15.