RFC-0052 · 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: How can the platform install DAG avoid the db.pg ↔ core dependency cycle?
Status: Open
Source: RFC-0052 §§3.1, 3.4, 4.1, 6
Issue: db.pg depends on core; core depends on db.graph; and db.graph depends on db.pg. The asserted rank-1-through-rank-7 DAG is cyclic and would be rejected by RFC-0041’s planner.
Recommendation: Define a minimal bootstrap core vocabulary as a Phase-1 artifact or remove db.pg’s runtime dependency on core, then verify the declared manifest DAG by topological sort.
Q: Which database schemas are actually created in Phase 1?
Status: Open
Source: RFC-0052 §§3, 6; RFC-0051 §§4, 12.2
Issue: The catalog lists eight db.* modules, including db.util owning util, while Phase 1 creates only six schemas and §3 says each physical module owns one schema even though db.pg owns none. The ownership and first-install timing of util are unspecified.
Recommendation: State the schema inventory by phase, include util when needed, and make the db.pg meta-module exception explicit in the invariant.
Q: How can a protected db.graph template be called by core.* modules?
Status: Open
Source: RFC-0052 §8; RFC-0039 §3.3
Issue: RFC-0039 allows a protected template only to the declaring module and descendants of its namespace. core.* is not a descendant of db.graph, yet RFC-0052 says protected db.graph.resource-create is available to core.*.
Recommendation: Define an explicit privileged export or capability grant for named platform modules, rather than expanding protected namespace semantics implicitly.
Q: Where is the extends manifest field declared and validated?
Status: Open
Source: RFC-0052 §7; RFC-0040 §§3, 11
Issue: The extends protocol is required for layered modules but does not appear in RFC-0040’s manifest envelope or compile pipeline. Its object merge, version constraints, and collision checks therefore lack a canonical source contract.
Recommendation: Add a typed extends declaration to RFC-0040 or a dedicated extension contract, with deterministic merge and compatibility rules.
Q: What does the claimed Phase-2-only equivalence mean on an empty database?
Status: Open
Source: RFC-0052 §§2, 6.1, 10 invariant 4 Issue: The invariant says Phase 1 plus Phase 2 equals a from-scratch Phase 2 install on an empty DB, but the normal installer needs graph tables, ID generators, roles, and the system principal that only Phase 1 creates. A Phase-2-only install cannot start in that state. Recommendation: Define the fixed point as re-running Phase 2 after Phase 1, and separately test that generated Phase-1 artifacts agree with the overlapping declarative module outputs.