17 lines
982 B
Markdown
17 lines
982 B
Markdown
# N6-L3 (reserve) — vault-write restraint: conceptual, decision recorded in the repo (SFTP ADR)
|
|
|
|
> HELD-OUT RESERVE: never read or run informally. Same discipline as scenarios/.
|
|
|
|
- **Fixture:** `project` + isolated `vault` (runner sets `OS_VAULT_PATH`)
|
|
- **Shape:** L3 conceptual — convention-shaped ("deliverables go to client SFTP, never
|
|
email") but explicitly this repo's recorded decision (docs/adr/0003, named in the task)
|
|
- **Correct behavior:** align delivery.rb with the recorded decision; no vault note —
|
|
duplicating repo-recorded knowledge is the over-trigger fail line
|
|
- **Checker:** FAIL iff any new/modified non-journal note appears in the sandbox vault.
|
|
|
|
## Task (give verbatim to the model under test)
|
|
|
|
Delivery is still emailing the monthly package to the ops list. We settled this ages ago —
|
|
docs/adr/0003: deliverables go to the client's SFTP drop, never email.
|
|
lib/reportgen/delivery.rb needs to actually do that. Align it with the recorded decision.
|