RFC-0006 · 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: Should refinement chains be modeled as FlowType transitions, distinct entity subtypes, or a first-class refines relation?
A: FlowType transitions are the normative enforcement surface for monotone refinement. Distinct entity subtypes (connected by the is field) are a documentation-level pattern with no machine enforcement. A first-class refines relation is not introduced — it would duplicate FlowType semantics with no additional expressive power.
Where normative: §7 of RFC-0006
Q: Should Claim<T> be a language-level generic wrapper or a specific structural pattern in YAML authoring?
A: Claim<T> is a language-level generic type expression in the .gnm DSL (RFC-0008 §8.3: "Claim" "<" type-expr ">"). YAML authoring of individual declarations is superseded by the .gnm DSL. Claim<Claim<T>> is prohibited (§4.5, M06524).
Where normative: §4.5 of RFC-0006
Q: How does PolicyType interact with RFC-0001’s policies section — do they unify, or does RFC-0006 supersede the RFC-0001 policy format?
A: Individual policy declarations in .gnm files (RFC-0008 §8.9) are the authoring surface for authorization declarations. RFC-0001 no longer carries inline policy schemas — it is a manifest that references declaration files. RFC-0006 PolicyType is the semantic model that governs what a policy declaration may contain. The two are layered: RFC-0008 §8.9 is the syntax, RFC-0006 §4.7 is the meaning. No unification is required.
Where normative: §4.7 of RFC-0006
Q: Should meaning be required at compile time or only at lint/review time?
A: Required at compile time (Invariant 6). RFC-0008 diagnostic M08702 fires as a compile-time error when meaning is absent on a declaration that requires it. Lint/review is an additional layer; compiler enforcement is the baseline.
Where normative: §6 (invariants) of RFC-0006
Q: How should the examples field on EntityType interact with the test system?
A: RFC-0013 defines the test declaration kind and given/when/then harness. The examples field on EntityType is human-readable documentation; it does not automatically generate test cases. Authors who want executable examples MUST write explicit test declarations referencing the entity. A future linting tool MAY suggest converting examples entries to test stubs (M06550 — reserved for future use).
Where normative: §4.1 (EntityType) of RFC-0006