RFC-0007 · 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.
Q: Multi-host write sharding for gnomon primitive
RFC: RFC-0007 §6.0a
Status: Open Gnomon’s single-writer-per-instance model does not address multi-host write sharding. How should gnomon instances be partitioned across hosts when horizontal scaling is required? Is this a non-goal permanently, or a deferred design decision?
Q: At what scale does the universal base table become a bottleneck, and what sharding strategy should be preferred?
A: Namespace-level PostgreSQL table partitioning by kind prefix at ~50M rows. Cross-host write sharding is deferred to a future RFC; normative spec assumes single Postgres instance or replica set.
Where normative: §6.0a of RFC-0007
Q: Should embedding projections live in the base table, the support table, or be configurable per kind?
A: Default is gnomon_embedding support table. Modules MAY promote to projection table columns via projection: { embedding: true } on the derive block, for cases where ANN search with field filters requires co-location.
Where normative: §6.4 of RFC-0007
Q: What is the right API for explicit identity merge (two gnomons determined to represent the same real-world entity)?
A: gnomon.merge({ canonical, duplicate, reason }) as an explicit lifecycle operation. Duplicate is marked superseded; edges are updated atomically; gnomon_merge table records the redirect. gnomon.resolve follows merge redirects transparently. Authorization required per kind.
Where normative: §7.6 of RFC-0007
Q: Should derivation scheduling be synchronous, async, or event-driven? How does staleness tolerance interact with the lifecycle plan?
A: Event-driven async by default (triggered by source gnomon writes). mode: sync available for lightweight deterministic derivations only. Staleness tolerance declared per derive block as maxStaleness: Duration; expired derived gnomons are flagged M07621 and hidden from queries unless allowStale: true.
Where normative: §8 (derivation scheduling) of RFC-0007
Q: Should the gnomon query API compile to SQL at module compile time or at query runtime?
A: Compile to SQL ahead-of-time at module compile time. Runtime values are substituted as parameterized query arguments (prepared statements); the SQL shape is fixed at compile time. True runtime query recompilation is not supported in the normative spec. Dynamic predicate composition MUST be expressed through a declared query with typed parameters, not ad hoc SQL generation.
Where normative: §9 (query API) of RFC-0007