RFC-0046 · 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: Where do secret backend values enter the four-layer precedence order?
Status: Open
Source: RFC-0046 §§3–5, 8 invariant 1 Issue: The normative four layers omit the secrets backend, while every sensitive value must be resolved through it. The RFC does not say whether a vault value overrides an override file, env var, or default, or whether a missing vault key falls back to a non-secret layer. Recommendation: Define an explicit sensitive-value resolution order and distinguish secret references from plaintext values in every layer; reject unintended plaintext fallback.
Q: Which declaration schema contains exported, flag, and perTenant?
Status: Open
Source: RFC-0046 §§4.1, 4.3, 6.1, 6.4
Issue: Cross-module access requires exported: true, and feature behavior depends on flag and perTenant, but the normative config declaration shape lists none of these fields.
Recommendation: Add the three typed slots, defaults, and validation rules to the declaration schema and compiler lowering.
Q: Which runtime contexts may resolve the configuration service?
Status: Open
Source: RFC-0046 §7.1; RFC-0040 §5.1.1
Issue: RFC-0046 registers services.config with core capability scope but says it is resolvable from any context. RFC-0040 defines core as platform-level only, while application operations need config access.
Recommendation: Assign a scope consistent with intended consumers, and enforce per-value export and sensitivity checks at each read.
Q: How are sensitive configuration values protected from generic configuration and flag APIs?
Status: Open
Source: RFC-0046 §§4.3, 5.5, 6.2, 7.1
Issue: services.config.get<T> and core.flags.list() expose values or metadata, but the RFC only specifies redaction at emission boundaries. It does not define caller authorization, whether sensitive values can be exported, or whether list() reveals per-tenant flag state to ordinary callers.
Recommendation: Define capability checks for config reads and flag enumeration, forbid sensitive exports by default, and keep secret values out of enumerable APIs.
Q: What numeric strings are accepted in environment overrides?
Status: Open
Source: RFC-0046 §3.3
Issue: Number.parseInt and Number.parseFloat accept prefixes such as 12junk, which can silently turn a malformed deployment value into a valid integer or number. Empty strings and non-finite values are also unspecified.
Recommendation: Require full-string parsing with explicit integer range and finite-number checks; report M46021 for any unconsumed or invalid input.