Plan ConfigKit adoption and clarify implementation policy

This commit is contained in:
2026-09-12 02:39:03 +00:00
parent 946fa10764
commit 00972e8d48
8 changed files with 1342 additions and 576 deletions

View File

@@ -87,6 +87,13 @@ Do not force all behavior through oversized end-to-end tests. Do not test every
A test should protect a decision, contract, or invariant—not memorialize the current implementation.
Tests must not create a stronger product contract than the requirement they
protect. In particular, do not turn an incidental limit, restriction,
permission choice, validation rule, or implementation default into policy by
asserting it without an expressly selected contract. Follow the
[implementation-discipline rules](architecture.md#implementation-discipline)
when deciding what behavior deserves durable protection.
Before adding or retaining a test, ask:
> What realistic defect would this test catch?