RFC-0053 view-mapping domain review
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.
Current adoption status (2026-10-16)
All 58 domain nodes have current source-bound reviews: 27 match and 31 mismatch. The approved owner/index-policy adoption changes no domain source, class, or domain review. Its 47 claim-review closures leave these 31 domain mismatches and the 21 remaining claim mismatches in place: 52 RFC-0053 mismatches in total. Source matches do not establish database or security conformance. The historical partial-review observations below retain their original counts.
Historical domain review (2026-10-05)
Status: all 50 domain nodes reviewed on 2026-10-05; 27 match and 23 mismatch. Owners: Compiler, Storage. No normative facts changed.
Five SQL function identities are typed NamedDeclaration, although the ontology means a Gnomon declaration instance. Coordinate database-function corrections with RFC-0051, especially the shared graph.has_permission identity. gnomon.template_marker is a runtime GUC and needs a runtime setting class; view-mapping.json is an emitted manifest and needs GeneratedArtifact.
Three resource.* effect nodes assert adapter-local effect definitions/lowering where §7 only names SQL procedures. Preserve effects with authoritative owners elsewhere; disposition the RFC-0053 duplication separately.
Three summaries exceed or contradict the source:
- KP26 expands gate acknowledgement to concurrent index creation, where §9.3 says gate-aware without specifying unconditional acknowledgement.
- core.migrations.RemoveField is described as required, but §9.2 makes JSON-key removal optional and explicitly retains payload data after view changes.
- field.indexed places expression indexes on generated views; §§3.2 and 4.1 place them on graph.resource.
The remaining reviewed declaration forms, source fields, synthetic template, and decision summaries agree with authored text. This review does not verify the PostgreSQL claims about RLS inheritance, materialized views, or write rejection; those need database conformance evidence.
Acceptance: inventory shared identities and incoming links, prepare bounded class/property and summary changes for owner approval, preserve provenance, regenerate RDF, and test the emitted view/index/write contracts against the supported PostgreSQL version. Source agreement alone is insufficient for security guarantees.
Remaining fields and catalog concepts
The remaining 30 nodes contain 20 matches and ten mismatches. Source fields, module examples, predicates, logical field-type mappings, and invariant summaries agree with their authored sections. Invariant agreement does not prove the underlying SQL behavior.
Seven §2 terms are typed DataType without language-type declarations: entity-type-view, expression-index, field-schema, instead-of-trigger, materialized-view, module-schema, and security-barrier-view. Represent their catalog or database-construct roles explicitly, with consumer inventory before changing classes.
Resource and Statement retain logical type identities but their summaries describe physical database tables. Keep the logical types and attach their PostgreSQL representations through storage mappings; do not collapse the logical type into graph.resource or graph.statement.
The materialize node is typed Operation, whose ontology meaning is an algebra operation kind. This RFC describes a projection configuration slot, distinct from the Materialization algebra operation. Give the slot a field or syntax representation with its canonical projection owner.
Acceptance requires shared-owner and property-domain checks, source-bound review refreshes, generated RDF validation, and class-selection query review. The pending physical database identity proposal for RFC-0051 can cover shared functions, but does not by itself authorize these other corrections.