gnomonlearn
Docs/RFC-0036/Design Q&A

RFC-0036 · Design Q&A

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.

← Read the authored RFC

Q: May a new Statement reference a soft-deleted Resource?

A: No. RFC-0036 §9.2 explicitly forbids it with M36050. Section 4.2, the Lean invariant, and the RDF projection now require existing, non-deleted endpoints at insert time; older Statements may remain after a Resource is deleted.

Source: RFC-0036 §4.2 invariant 2; §9.2 Issue: The earlier §4.2 wording allowed a possibly soft-deleted endpoint, while §9.2 rejected the same insert.

Q: How do Predicate, Workspace, and policy records fit the two-table graph claim?

Status: Open

Source: RFC-0036 alignment note; §§4.3, 6; RFC-0052 §3.4 Issue: The alignment note says Resource and Statement are exactly two physical tables, while the RFC describes Predicate and multiple auxiliary types as separately persisted graph entities with their own IDs and fields. Their storage mapping and global ID allocation are unspecified. Recommendation: Map each auxiliary shape to Resource, Statement, or an explicitly named non-graph table and define one global ID allocator across the persisted forms.

Q: Can a caller supply ResourceInput.id?

Status: Open

Source: RFC-0036 §§3.1, 4.1 Issue: IDs are declared backend-allocated and never caller-supplied, but ResourceInput contains an optional id and says it is “usually” backend-allocated. The write contract could allow an external caller to choose a global graph ID. Recommendation: Remove caller-supplied id from ordinary create/upsert input, or define a separate privileged restore/import operation with collision checks and audit.

Q: What persisted history supports asOf(t) after a Resource or Statement update?

Status: Open

Source: RFC-0036 §§4, 8; RFC-0037 backend contract Issue: The shapes list createdAt, updatedAt, and deletedAt, but no historical versions or system-time interval rows. Updating a payload or relation in place loses its prior value, so an asOf(t) query cannot reconstruct the earlier state from these columns alone. Recommendation: Define append-only versions or history records with system-time bounds and specify how the two-table physical model stores and queries them.

Q: Where is data shape validation enforced for untrusted writers?

Status: Open

Source: RFC-0036 §4.1 invariant 3; §7; RFC-0037 service boundary Issue: The registered kind shape is normative, but validation is assigned to the client rather than the backend. A direct service caller or buggy client can persist an ill-typed JSON payload while the backend still claims conformance. Recommendation: Validate the registered shape at the authoritative write boundary, retaining client validation for early diagnostics; reject unknown or invalid fields according to an explicit policy.