Development record

docs/explanation/artefacts.md:19 says an intent is filed as shipped once its acceptance criteria are verifiably met. That holds on the build loop's closing lane, where an unmet or undecided audit fails the round (internal/core/implement/loop/validate.go:129,186-205). A spec closed by hand ships the intent first and the audit follows; an unmet criterion then leaves the intent in shipped/ with an owed check and an issue (internal/core/intent/audit_owed.go:9-21, ruling DQ1c).