RFC-0036 graph storage and RDF 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: source-bound domain review and first-release model proposal, 2026-10-03. Owners: Graph Platform, Storage, and spec. No Gnomon system is deployed, so no live graph records or CRDs require migration.
Source boundary
RFC-0036’s alignment note is authoritative: Resource and Statement are
platform intrinsics declared only by db.graph. Application authors use
templates, projections, queries, and mutations rather than declaring or
writing those two tables. The rest of §4/§6/§7 describes backend record
shapes, write inputs, caches, policies, a legacy sync row, and an optional
envelope. They are not Gnomon top-level authoring declarations. The ontology
currently defines NamedDeclaration as an instance of a Gnomon declaration
kind, Field as a slot on such a declaration, and DataType as a Gnomon
Value type. These meanings make the inherited projection overstate what an
application can author.
The source-bound review covers all 92 domain nodes. The mismatches include:
| Nodes | Conflict |
|---|---|
Nine declaration/* backend shapes other than Resource/Statement | Write-side inputs, policy/cache rows, Predicate, Workspace, legacy ExternalLink, and VersionedData are represented as Gnomon named declarations despite no such authored declaration in §4/§6/§7. |
Their 24 field/* nodes | Backend record slots are represented as fields on Gnomon declarations. |
field/Resource/kind | §3.2 requires backends to treat kind as opaque text despite the ltree convention; RDF assigns LtreePath as its type, turning a convention into a stronger authoring type. |
Seven type/* nodes | Bigint, Number, Instant, LtreePath, PermissionBits, and Subgraph are storage/internal types absent from RFC-0006’s complete author-writable Value hierarchy. The RDF Map summary also permits arbitrary JSON values, conflicting with RFC-0006’s typed non-null Map<K,V> and RFC-0036 §7.2’s null prohibition. |
Resource, Statement, their other 19 field nodes, the five permission
levels, two architecture decisions, 19 invariants, db.graph, and the
Text/Boolean/List type nodes agree with authored source at the level
reviewed. A matching verdict is not a backend conformance test. No RDF
triples or subject IRIs changed during this review.
Proposed model
Represent persistent and write-side graph shapes using explicit
GraphRecordType, GraphInputType, GraphCacheType, or other documented
backend classes under DomainEntity; use GraphRecordField for their
slots. Retain NamedDeclaration only for a specific Gnomon declaration or
platform intrinsic that the compiler exposes as one. Separate storage scalar
types from Gnomon Value types. Preserve each field’s concrete storage type
and optionality; define an explicit adapter mapping to RFC-0006 Integer,
Timestamp, Text, Map<K,V>, and other authoring types where such a mapping
is valid. Subgraph belongs to the graph query/projection algebra, not to
the author-writable Value hierarchy. Resource.kind remains opaque Text
with optional ltree-compatible indexing and validation only where another
contract expressly requires it.
The global AGENTS.md boundary-DTO preference applies when a graph input,
cache, manifest, or payload crosses a process, language, or file boundary:
use a versioned .proto message unless the existing graph contract has an
established schema layer. Inventory the actual producer and consumer before
choosing a schema; a TS or Rust runtime struct can still represent internal
state. Preserve the savvifi.graph.v1 wire identity until its separate
destination-archive cutover is verified.
Acceptance
- Align ontology, RFC-0036, RFC-0006, RFC-0037/0038/0049/0050/0052, Lean, source protobuf projections, generated Turtle, and any backend or authoring type adapters. Record any old-to-new RDF IRI mapping before the first publication; no deployed-state conversion is required.
- Verify
db.graphexclusivity, opaquekindbehavior, backend ID allocation, predicate consistency, bitemporal interval rejection, soft deletion, and null-free data at the wire/storage boundary. - Test cross-repo graph descriptors and pins, compare checked-in SPARQL results, and rebind all source-bound projection reviews after correction.