RFC-0013 · 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 test blocks and invocation target are canonical for the first release?
Status: Open — owner decision requested.
Context: RFC-0008 §6.9/§8.12 and the extracted EBNF require given/when/expect and actor attempts statements. RFC-0013 §§4–5 require given/when/then, Boolean post-state assertions, and an action invocation with an actor, even though RFC-0008 §6.10 assigns actor and authorization logic to procedure, not action. RFC0013_TEST_CONTRACT_PROPOSAL.md compares the first-release choices and the dependent grammar, diagnostic, Lean, RDF, and compiler work. Do not treat either form as implementable until these clauses agree.
Where normative: RFC-0008 §6.9/§8.12 and RFC-0013 §§4–5 after reconciliation.
Q: Should a future revision allow multiple when invocations per test (multi-action tests)?
Status: Open
Context: Deferred. The single-action constraint is normative for RFC-0013. Some scenarios naturally involve a sequence (e.g., create, then update, then verify). Whether intermediate then assertions should be permitted between when steps is not yet decided.
Where normative: n/a — pending future RFC or implementation experience
Q: Should there be syntax for asserting that an action should fail or a precondition should be violated (negative-path tests)?
Status: Open
Context: Deferred. There is currently no syntax for asserting that an action should fail. A future throws or fails with clause could address this. Until specified, negative-path testing must be handled by testing that the object graph state did not change.
Where normative: n/a — pending future RFC or implementation experience
Q: Should there be a fixture declaration kind for shared, reusable given contexts?
Status: Open
Context: Deferred. The given block is inlined per test. No syntax is reserved for a named reusable fixture in RFC-0008 §8.12 at this time.
Where normative: n/a — pending future RFC or implementation experience
Q: Should AI agents be permitted or encouraged to author test declarations?
Status: Open Context: Deferred. AI agents are currently scoped to production declarations. This is a DX and RFC-0009 concern not addressed in RFC-0013.
Where normative: n/a — pending future RFC or implementation experience
Q: Must test ordering guarantees be preserved in a future parallel execution mode?
Status: Open Context: Deferred. Tests within a file are run in declaration order; tests across files run in lexicographic file path order. Whether a future parallel execution mode must preserve this ordering for diagnostic reproducibility is not yet decided. The current model is strictly serial.
Where normative: n/a — pending future RFC or implementation experience