gnomonlearn
Docs/RFC-0037/Design Q&A

RFC-0037 · 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: Does TransactionService implement read() and write()?

A: No. The two-method contract applies to the seven query services. TransactionService has the lifecycle API in §4.8. The authored invariant, Lean catalog, and RDF projections now state the exception.

Source: RFC-0037 §§3.3, 4.8, 7 invariant 1 Issue: The earlier invariant applied the two-method surface to all eight services, contradicting the TransactionService shape.

Q: Which RFC owns the cross-backend tenancy model?

A: RFC-0014 defines module versioning, not tenancy. RFC-0036 and RFC-0037 now cite RFC-0045 for tenant-mode configuration and RFC-0051 for PostgreSQL RLS binding, and explicitly mark the complete cross-backend tenancy contract deferred.

Source: RFC-0037 §§4.7, 5.4; RFC-0036 §6.1; RFC-0051 §7 Issue: The prior text assigned tenancy to RFC-0014, which has no such contract.

Q: May a backend ignore an unknown resource query filter?

Status: Open

Source: RFC-0037 §4.1; RFC-0000 conformance and diagnostic rules Issue: Implementations may accept extra filters and clients must tolerate unknown filters being ignored. A caller can therefore believe a query is restricted when the backend returns broader data, including across an authorization or tenant boundary. Recommendation: Reject unsupported filters with a stable diagnostic or negotiate supported filters explicitly; never silently ignore a restriction-bearing filter.

Q: Is Statement soft delete part of the service write surface?

Status: Open

Source: RFC-0037 §4.2; RFC-0036 §9 Issue: §4.2 says to use Delete via the common pattern for system-time removal, but its StatementService write table lists only Create, CreateMany, Update, and Invalidate. RFC-0036 requires soft deletion semantics. Recommendation: Add a distinct Delete query with a stable discriminant and soft-delete behavior, or remove the reference and define another authorized deletion path.

Q: Can TransactionService.execute() bypass tenant and policy checks?

Status: Open

Source: RFC-0037 §§4.8, 5.4; RFC-0051 RLS contract Issue: The optional SQL escape hatch shares a backend with scoped services but has no declared authorization, transaction, or RLS obligations. A caller could bypass service-level tenant filtering through raw SQL. Recommendation: Restrict it to a privileged internal interface with explicit principal, tenant context, audit, and RLS enforcement; exclude it from the general GraphBackend surface.

Q: What is the portable transaction-context propagation contract?

Status: Open

Source: RFC-0037 §§4.8, 5.3 Issue: Service calls must observe the open transaction in the same async context, but the RFC does not define how context is propagated across callbacks, nested transactions, or process boundaries. A partial backend may silently execute a write outside the intended atomic scope. Recommendation: Pass an explicit transaction token/context to service calls or define an equivalent portable propagation mechanism with nested and cross-service tests.

Q: Does the isolated client callback add a new backend transaction interface?

A: No. The approved GraphClient.isolatedTransaction method composes the existing backend lifecycle and optional savepoint operations. The default joining client callback remains unchanged. Nested isolation requires complete savepoint support and rejects before its callback otherwise; lifecycle failures remain fatal with causes retained.

Source: RFC-0037 §4.8; RFC-0038 §3.4; approved Gnomon implementation fed0662ece0d3ecd6774469085cef261d303ad9e Issue: Joining an active transaction does not by itself establish an independent rollback boundary. This clarification does not close the broader portable transaction-context propagation question above or establish runtime conformance.