M9-15 JSON/XML Data Export & Exchange Support

Milestone: M9 — Hardening and Compliance SOW Reference: NFR4 Requirement Clarity: ✅ Clear Dev Status: ❌ Not started — CSV export is well covered (M3-08, M5-06, M3-11), but JSON and XML export/exchange are confirmed absent anywhere in the codebase

Overview

NFR4 requires "data exports (e.g. CSV, JSON) and data exchanges (e.g. JSON, XML) supported in standard formats" — CSV is done, JSON/XML are not.

Tasks

• Confirm which specific exports/exchanges actually need JSON/XML support (e.g. credential data, audit logs, disclosure records) versus which are CSV-only by design
• Add JSON export alongside the existing CSV export endpoints where confirmed needed
• Add XML support only where a specific external exchange partner requires it (the requirement is generic; avoid building XML support nobody consumes)

Dependencies

• M3-08, M5-06, M3-11 — natural places to add a format option rather than building a separate export system.

Acceptance Criteria

• Data export interfaces (CSV/JSON) and data exchange interfaces (JSON/XML) supported in standard formats (per SOW NFR4)

Existing Reference Material

None.

Blockers & Risks

• Needs clarification: the requirement is generic ("e.g. JSON, XML") rather than tied to a specific integration partner — confirm concrete use cases before building speculative XML support.