- Status: approved (2026-07-18)
- Priority: P0 EXT — blocking (production rollout gated via YSD-0139)
- Decision owner: @GreyChimp
- Drafted: 2026-07-18 by Claude Code (claude-fable-5)
- Approval: approved as recommended by @GreyChimp on 2026-07-18; outcome recorded in decision-log.json; review by 2027-07-18
Question#
Which interchange formats are mandatory at launch?
Recommendation#
Launch set: W3C Web Annotation JSON (annotation portability — nisaba already speaks the selector model); BibTeX/RIS/CSL-JSON citations (nisaba primitives exist); CSV/JSON structured study-data export; OpenTimelineIO for NLE timeline handoff; USD for DCC/3D handoff (neith importers + on-box pxr); signed study-pack JSON (shared content-signing) for teaching packs; Metis-native + CSV for learning records. Engine backlinks ride the existing Bellona bridge formats. Alignment with proposal §19.4 interoperability profile to be verified during Section 15 implementation.
Options considered#
- EDL instead of OTIO — kept as an export-only extra later; OTIO is the modern interchange with wider tooling.
- Proprietary-only exports — rejected: §22.4/§25.14 longevity requirements.
Consequences#
- Section 15 items implement these targets; YSD-22037 proves durability across provider/model/UI changes.
Machine-enforced outcome (once approved)#
Export registry enumerates exactly the approved targets; unsupported formats return explicit unsupported responses.