RFC-0051 physical database identity 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.
Status: proposed first-release class correction. Owners: Storage, Security,
Specification. All 102 domain nodes have source-bound reviews in
RFC0051_DOMAIN_REVIEW.md; 61 currently mismatch. No Gnomon deployment exists.
Concrete class map
Introduce DatabaseObject under DomainEntity, with DatabaseTable, DatabaseFunction, and DatabaseColumn subclasses. These identify physical adapter objects, separately from source declarations, declaration Fields, algebra Operations, and storage-form selectors.
| Current nodes in RFC-0051 | Count | Proposed class |
|---|---|---|
| audit.events; graph.predicate_policy; graph.reserved_namespaces; graph.resource; graph.statement | 5 | DatabaseTable |
| audit.install_audit_trigger; graph.enforce_kind_immutability; graph.has_permission; graph.is_admin_session; graph.is_reserved_type; graph.set_session_user; ids.create_generator; ids.gen_audit_event_id; ids.gen_resource_id; ids.gen_statement_id | 10 | DatabaseFunction |
| All 21 nodes under domain/operation/graph.* | 21 | DatabaseFunction |
| All nodes under domain/field/audit.events, domain/field/graph.resource, and domain/field/graph.statement | 18 | DatabaseColumn |
| db.pg.audit-trail | 1 | NamedDeclaration (retain) |
Retain the current subject IRIs for this class correction because they identify the same adapter objects. Their path categories are historical identifiers, not class assertions. Check every shared source node before changing its class; apply the same classification wherever the same IRI names the same physical object. Scan property domains as well, so inherited properties do not imply the former classes. Do not treat a physical function as an algebra operation or runtime interface method merely because it is callable.
Effect ownership
The four effect IRIs in RFC-0051 are shared, not adapter-local inventions. Resource effects occur in RFC-0037, RFC-0043, RFC-0053 and claim references; statement.upsert occurs in RFC-0043. Preserve their owner definitions. Remove RFC-0051’s duplicated effect-definition nodes rather than globally renaming effects into database functions. Add explicit adapter mapping facts on the DatabaseFunction nodes for resource Create/Update/Delete only after confirming the owning effect’s input/output semantics. Do not map statement.upsert to Create/CreateMany without an authored conflict policy: insertion and upsert are not interchangeable. This source scan narrows the earlier mismatch findings from global effect identity to misplaced adapter ownership and unsupported upsert lowering.
Capability and summary corrections
The consumer scan confirms db.graph.unrestricted is owned by RFC-0050
§7.3, with definitions in RFC-0036, RFC-0050, and RFC-0051 and ten incoming
RFC-0050 references. Preserve the capability and those owner rules. The lack
of an adapter-local definition is an attribution gap, not evidence that the
privilege is globally unsupported. Remove only RFC-0051’s redundant definition
or explicitly attribute it to RFC-0050; do not remove the shared capability
or its existing authorization contract.
All eighteen physical columns carry fieldType/isRequired assertions whose
ontology domains imply Field. Introduce columnType and columnRequired with
DatabaseColumn domains and preserve the existing type/required values through
those properties. Otherwise retyping would still infer the superseded class.
See RFC0051_IDENTITY_CONSUMERS.md for every definition and incoming link.
Narrow KP28’s summary to production dedicated-role ownership, with the declared ids exception and development fallback. Correct the reserved-table invariant to allow privileged db.graph install extension while prohibiting application module additions. These are source-alignment corrections, not new backend rights.
Acceptance
- Obtain owner approval for the physical-object class map and adapter-local capability attribution. Preserve shared logical effect owners and source declarations.
- Inventory every node and incoming reference across source projections, framework embedded Turtle, site, query catalogs, and reasoner ontology inputs.
- Update classes and summaries consistently; remove adapter-local duplicate effect definitions and correct unsupported upsert mapping facts. Review property domains and ranges to avoid inferring the former classes.
- Bind semantic verdicts to the corrected sources, regenerate Turtle, compile Lean references, compare all public claim-query results, and run the five artifact-fed framework consumers and the repinned site build.
- Keep runtime security gaps and type-contract conflicts separate and open. Class correction does not establish a deployed PostgreSQL adapter.