RFC-0044 transform identity and cache proposal
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.
Evidence
RFC-0044 §7 explicitly distinguishes its build-time transforms: manifest entries from the runtime data transform declaration in RFC-0008. The shared RDF IRI declaration/transform is nevertheless used for both. Four domain projections assign it incompatible kindClass values: Migrations (RFC-0006 and RFC-0040), Operations (RFC-0021), and Composition (RFC-0044). The existing domain identity gate compares only RDF class and FQN, so it misses this conflict.
RFC-0044 §§3.5 and 5.2 require explicit projectors to run in manifest order and allow later projectors to observe earlier outputs. Section 5.4 hashes sortedList(projectors) into the cache key. Reordering two projectors can therefore change output while preserving the key and incorrectly reusing old output. The Lean grammar repeats the sorted-list formula.
Parser adapters and projectors are registered build-system components. RFC-0044 does not define them as Gnomon source declaration kinds, but its domain projection types declaration/parser-adapter and declaration/projector as DeclarationKind.
Recommended contract
- Give the build-time manifest entry a distinct identity, for example
manifest/transform, with a manifest-entry class. Keep the runtimedeclaration/transformidentity for the RFC-0008/RFC-0021 data transform, then reconcile its remaining class ownership separately. Update RFC-0040 and RFC-0044 links to the manifest identity. RFC-0044’sfield/transform/*nodes and seveninvariantOflinks also need to follow that split; their presenttransformparent implies the runtime declaration. - Represent registered parser adapters and projectors as build components, not language declaration kinds. Their concrete implementations remain named components.
- Hash the effective ordered projector sequence. Resolve a default sequence from registration order first; preserve explicit manifest order. Canonicalize the profile map, include parser name/version and source content hash, then hash an unambiguous serialized tuple. Reordering projectors must invalidate the cache.
Acceptance
- Tests show that exchanging two order-sensitive projectors produces distinct keys and distinct output; repeat builds with identical inputs reuse output.
- A changed parser version, source content, or normalized profile invalidates the cache.
- Narrative, Lean, source-domain protobuf, generated Turtle, references, and site pin agree.
- Shared IRI identity checks report
kindClassconflicts and show the build-time and runtime transform identities separately. - Checked-in claim/domain queries and local framework KG consumers are compared before and after the RDF identity change.
Nothing is deployed, so first-release identities can be corrected without a stored-data migration.