Captured during the 2026-08-14 repo-reorg planning so it isn't forgotten.
Today @pdpp/reference-contract mixes two things: the normative protocol surface (AS/RS auth, grants, data query — what the spec should eventually own as machine-readable, conformance-testable schemas, per OIDC/FHIR precedent) and implementation-internal routes (console/admin/ops — which belong to the implementation alone).
Target state: the spec owns versioned protocol schemas that the conformance suite tests against; the implementation's contract imports and extends them. reference-contract as it stands is a scaffold toward that, not the terminal design.
Not now: do this as part of conformance-suite work, after the repo split. Until then, avoid deepening the mixing (new normative routes should be clearly separable from implementation-internal ones).
Assisted-by: AI
Captured during the 2026-08-14 repo-reorg planning so it isn't forgotten.
Today
@pdpp/reference-contractmixes two things: the normative protocol surface (AS/RS auth, grants, data query — what the spec should eventually own as machine-readable, conformance-testable schemas, per OIDC/FHIR precedent) and implementation-internal routes (console/admin/ops — which belong to the implementation alone).Target state: the spec owns versioned protocol schemas that the conformance suite tests against; the implementation's contract imports and extends them.
reference-contractas it stands is a scaffold toward that, not the terminal design.Not now: do this as part of conformance-suite work, after the repo split. Until then, avoid deepening the mixing (new normative routes should be clearly separable from implementation-internal ones).
Assisted-by: AI