RFC-0003 · 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: Which composition failures are recoverable at runtime?
Status: Open Context: Deferred. Partially addressed in §7 — missing targets produce non-silent diagnostics and controlled placeholders in non-dev mode. Full recovery taxonomy deferred to implementation experience.
Where normative: n/a — pending future RFC or implementation experience
Q: Should layout-level data fetch be forbidden or discouraged?
A: Forbidden. Data fetch is page-level only (§4, Layer 2). Layout declarations MUST NOT initiate data fetches; they MUST receive data through page-level bindings. Layout-level fetch would couple structural layout to data orchestration, undermining the layer separation contract. Violation produces warning M03225 (reserved).
Where normative: §4 (layer model) of RFC-0003
Q: What telemetry thresholds trigger compatibility adapter removal?
Status: Open Context: Deferred. Operational concern — deferred to deployment documentation.
Where normative: n/a — pending future RFC or implementation experience
Q: Should view declarations support layout hints?
A: Yes, as optional hints. A view declaration MAY include layout hints (columns, sectionOrder) that the runtime theme layer MAY use. Hints are advisory: the theme layer may ignore them. The compiler MUST NOT reject a view for declaring hints the runtime theme does not support. This preserves the semantic/presentation separation while giving authors influence over layout without requiring them to drop down to direct layout authoring.
Where normative: §4 (view declarations) of RFC-0003
Q: When a view references a Claim<T> field, what is the default widget rendered — the raw value, the claim wrapper with confidence indicator, or a configurable choice?
A: The default widget is the built-in claim-field composite widget (value + confidence indicator + provenance link + status badge). Module authors MAY override per-field using claimWidget: in the view’s show block. Override widgets MUST accept ClaimFieldProps.
Where normative: §4.4 of RFC-0003
Q: Is priority required in source when an aspect contributes a widget?
A: No. The source field is optional; each contribution has an effective
integer priority. A supplied value MUST be an integer. When the field is
omitted, the compiler MUST assign effective priority 0 before ordering
contributions and checking priority ties. Contributions to the same extension
point with equal effective priorities MUST produce M03210, including an
omitted field paired with an explicit 0 or two omitted fields. This
resolves the former conflict between explicit declaration and default 0.
Where normative: §4.1 of RFC-0003
Q: Which diagnostic identifies a layout declaration that initiates data fetch?
Status: Open
The earlier Q&A says layout fetch is forbidden and reserves
M03225 for it, but authored §5a and the Lean catalog already allocate
M03225 to a missing default widget kind with a generic text fallback.
Authored §4 describes data orchestration as a page responsibility but does
not state the layout-fetch prohibition or its diagnostic explicitly. Keep
M03225 for the authored missing-widget condition. Before the first release,
add the layout-fetch prohibition to the normative text and allocate a distinct
registered diagnostic with its own trigger, severity, and compiler test.
Where normative: §4 or §5a after owner decision