QR verification (§15 Q6 → §10.4.5): spec MUSTs, then show/scan/reciprocate flows #106

Closed
opened 2026-08-21 13:45:41 +02:00 by thecrealm · 1 comment
Owner

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.

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.
Author
Owner

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.

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.
thecrealm added
now
and removed
next
labels 2026-08-25 16:03:31 +02:00
thecrealm 2026-08-25 16:50:30 +02:00
  • closed this issue
  • removed the
    now
    label
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
thecrealm/katrix#106
No description provided.