RFC-0037 legacy compatibility statements
Versioned draft snapshot
RFCs, reference catalogs, and evidence reflect Spec 3b2e3e7a114fb826b1445d39a48756b8fff629cd. Counts and pending/status notes belong to that snapshot. Read the dated project update for later progress.
Source repositories are private during staging. Links marked “repository access required” need access to the linked repository.
This is a trace and gap record from the pinned draft specification. It does not establish proof or implementation conformance.
RFC-0037 §8.1 still calls the specification a near-verbatim codification
of the legacy backend contract and says the memory and PostgreSQL backends
need no behavior changes. Those statements predate the owner-approved
edge-rich traversal path. Before Gnomon commit 215179432,
graph-backend-model/model/traversal.ts used an edge with targetId and a
path with only resourceId, depth, and resource-ID path. The current
§4.5 path requires physical edge endpoints, statement and predicate IDs,
and ordered resource and edge arrays. Commits 215179432 and e222fc91d
changed the model and adapters to implement it. The legacy claim therefore
cannot remain a present-tense conformance statement.
Revise §8.1 and the associated Lean/RDF claims to describe the legacy starting point and the measured compatibility delta. Keep the source history and exact commit references in the migration record. Regenerate the reference and Turtle from source, refresh review hashes, and verify both backend conformance tests before claiming compatibility. This is a factual update; it does not reopen the selected traversal path shape.
Resolution
RFC-0037 §1 and §8 now call the old PostgreSQL and memory backends migration baselines and name the edge-rich traversal delta. The Lean motivations and two RDF claims use the same scope, without asserting backend conformance. Their claim subject IRIs remain stable. Both adapters still require the broader service conformance evidence described in the migration audit before a release claim can say they fully implement RFC-0037.