[Tracking] Citizen Autonomy without Foreign Server

[Jenziner]

Purpose

This tracking issue bundles all sub-issues arising from the exploration of citizen-side data autonomy: how a citizen can hold an independently verifiable copy of a finalized Record without depending on a third-party server (e.g. a Solid Pod) they must trust.

Outcome of the exploration

• No Solid Pod integration — neither in RWC nor in RWP (see RWC-4 for the ADR).
• The identified gap is closed by extending RecordWeb itself with two additions:
  1. A third classification dimension ("Transit") alongside Type and State.
  2. A "proof" object as a fourth structural component of a Record, enabling export of a self-verifying, signed instance ("Ausfertigung") to the citizen.

Sub-issues

RWC (concept):

• Add "Transit" as a third classification dimension (alongside Type and State) #6: Add "Transit" as a third classification dimension
• Define "Issued Copy" (Ausfertigung) as a citizen-held artifact #7: Define "Issued Copy" (Ausfertigung) as citizen-held artifact
• Extend Annex B with positioning against VC / OID4VCI / OID4VP / ISO 18013-5 #8: Extend Annex B with positioning against VC / OID4VCI / OID4VP / ISO 18013-5
• ADR — Decision against Solid Pod as primary citizen storage #9: ADR — Decision against Solid Pod as primary citizen storage

RWP (technical spec):

• Add "proof" object as fourth structural component of a Record rwp#7: Add proof object as fourth Record component
• Define export operation for Issued Copy rwp#8: Define export operation for Issued Copy
• Add schema attribute for minimal control-context payload rwp#9: Add schema attribute for minimal control-context payload
• Encode Transit as a metadata field rwp#10: Encode Transit as a metadata field

Consolidation window

Each sub-issue has a 14-day consolidation window per CG governance. None of them require a PR at this stage — text proposals are sufficient for round 1.