gnomonlearn
Docs/RFC-0051 PostgreSQL claim review

RFC-0051 PostgreSQL claim 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.

Status: all 102 claim nodes reviewed on 2026-10-05; 97 match and five mismatch. Owners: Storage, Compiler. No RDF facts changed.

Reviewed scope: adapter status, §10 type mapping, service lowering, transaction commands and savepoint wrapper, live workspace projections, and bootstrap contents, generation, versioning, and CI drift behavior. Matching verdicts establish source agreement; they do not prove backend conformance, current integration-test scope, or a successful live bootstrap.

Function-call mapping overstatement

service-to-pg-deterministic says every backend service operation lowers to a PostgreSQL function call. Resource/Statement Query operations instead lower to parameterized SELECT, and WorkspaceService lowers to projection-style read queries. §13.10 repeats the blanket wording, so this is an authored consistency issue rather than merely a projection typo.

Recommend specifying deterministic PostgreSQL operations: functions, queries, and transaction commands as appropriate. Acceptance: align §11’s introduction, §13.10, Lean, and RDF; preserve the claim IRI; verify each service’s lowering shape in adapter tests when implemented. Keep typed effect alias ownership separate from concrete backend call mappings.

Extension, diagnostic, and schema review

Thirty more claims were reviewed; twenty-eight match their sources. Two mismatch: uuid-ossp-required retains UUIDv7 generation despite §3’s explicit correction that the extension does not supply it; namespace-schema-correspondence omits §4.1’s application-module view scope and therefore incorrectly covers the differently named platform schemas.

The legacy no-schema-migration statement is authored, but §14.2 separately requires runtime marker, RLS policy, and bootstrap version updates. A source match does not establish existing deployment compatibility. Diagnostic verdicts match the structured catalog; no diagnostic emission was exercised here.

Completed table, RLS, generator, and audit review

The final 42 claims have verdicts. Forty agree with the sources; two mismatch: kind-immutability-trigger names a PostgreSQL function as the trigger itself, while the SQL names the trigger resource_enforce_kind_immutability; and reserved-namespaces-bootstrap-only omits the permitted db.graph install extension path already identified in the domain review.

Source matches do not establish marker authenticity, initialized tenant context, complete bitemporal semantics, or correct Snowflake arithmetic. The adapter sources leave a tenant GUC initialization gap and use timestamp_bits ambiguously between value and bit width in the generator formula. Those implementation/contract gaps remain open rather than being covered by source-agreement verdicts.

All 204 RFC-0051 claim and domain nodes now have source-bound verdicts: 138 match and 66 mismatch. The corpus ledger reports 5,115 of 6,954 reviewed, 1,231 mismatches, and 1,839 unreviewed. No RDF facts changed during the review.