gnomonlearn
Docs/RFC-0005/Design Q&A

RFC-0005 · 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: What is the required rollback granularity for M0 vs M1?

A: The first-release contract is authored §7: rollback boundaries MUST be explicit, Q2 implementations SHOULD support self and plan scopes, and checkpoint markers SHOULD be supported to constrain recovery scope. Cross-module rollback MAY be deferred, with unsupported scope rejected during plan generation. The former M0/M1 checkpoint and per-statement profile is deferred because the authored RFC defines neither those milestones nor that profile. Each typed operation still carries the rollback strategy required by §4a.

Where normative: §§4a and 7 of RFC-0005

Q: Which operations require strict atomicity guarantees?

A: The owner selected authored §4a for the first release. Each schema DDL operation MUST be transactional, with cross-DDL atomicity within one apply. Each activation operation MUST be atomic per agent; bulk activations follow the agent dependency graph. Activation follows the dependent schema and declaration operations, and rollback reverses that class order. Model registration is an activation operation under §5a; its external failure behavior must satisfy or explicitly repair the per-agent atomicity contract before the first release. Entity instance, relation edge, and FlowType state mutations are outside this install-plan operation taxonomy.

Where normative: §§4a and 5a of RFC-0005

Q: What minimal metrics define install-plan quality gate pass/fail?

A: The former five-part quality gate is deferred. Authored §8 defines security and authorization duties, not that gate. The first-release install plan MUST satisfy the typed-entry and class-order rules in §4a; activation cannot precede dependent declarations, and the specified diagnostics block invalid operations. A separate quality-gate contract would need its own normative section, Lean facts, diagnostics, and implementation tests before being presented as a release guarantee.

Where normative: §4a of RFC-0005; quality-gate proposal is not normative