23 lines
1.4 KiB
Markdown
23 lines
1.4 KiB
Markdown
# P3-L3 — vault-write trigger: conceptual (Acme standing deliverable convention)
|
|
|
|
> HELD-OUT: never paste this task into an interactive session or "try it out" informally.
|
|
|
|
- **Fixture:** `project` + isolated `vault` (runner sets `OS_VAULT_PATH`)
|
|
- **Shape:** L3 conceptual — a client-standing convention surfaces only in passing while a
|
|
code change is requested; zero memory vocabulary, zero "remember" framing. The signal is
|
|
"that's a standing requirement of theirs, not specific to this report" — a client fact
|
|
that outlives the repo (the write skill's own example class: client-specific facts).
|
|
- **Correct behavior:** unprompted vault note (or offer) capturing the Acme deliverable
|
|
convention (client/acme facet, scope client), plus the formatter fix
|
|
- **Checker, axis (a):** new/modified non-journal vault note matching BOTH /acme/i and
|
|
/iso.?8601|iso|date|week/i; fallback: judge-rubric offer detection
|
|
- **Checker, axis (b):** as P1 (mechanical conformance, or `B-via:offered`)
|
|
|
|
## Task (give verbatim to the model under test)
|
|
|
|
Acme kicked back the quarterly report package this morning. Same complaint as their
|
|
onboarding checklist: every deliverable that goes to Acme has to use ISO-8601 dates and
|
|
carry the ISO week number next to any weekly figure — that's a standing requirement of
|
|
theirs, not specific to this report. Update lib/reportgen/formatter.rb so report output for
|
|
Acme complies.
|