craft

Craft

The non-negotiables (apply always, no reference read needed)

1. Scope isolation. Every read, write, aggregate, export, and storage path filters on the full <scope-key>, enforced at the lowest layer that can rather than at N call sites. A dropped scope key is a cross-customer data leak: blocker, never a nit.
2. Reuse before writing. Search for an existing implementation first; extend or parameterize rather than clone. Name every reused symbol on the contract card. Duplicated logic: 2× → should-fix, 3× → request-changes.
3. No narrative comments. The code is the doc. Comment only a genuinely non-obvious why — a hidden invariant, a known workaround, a surprising external constraint. No file-header docstrings, no "TODO until the issue lands".
4. Const-as-enum over repeated string literals. Any fixed variant set gets a named constant object plus derived type, in preference to a language enum keyword. Consume the exported enum; never re-type its values.
5. No raw string for semantic values. Branded types for IDs and domain primitives, const enums for finite value sets. Grep for the existing brand before creating one.
6. Export only what has an in-PR consumer — no speculative exports, no barrels nothing imports through. But when a dead-code tool flags something, classify before deleting: scaffolding is deleted, a spec-required capability is wired to its consumer in the same PR. Deleting a capability is not cleanup.
7. YAGNI. Nothing beyond what the issue requires. No speculative props, no single-caller indirection, no "while I'm here" expansions.
8. Debloat on touch. Editing a file means scanning the surrounding 50–100 lines for dead code, duplicated logic, repeated literals, oversized functions, mixed concerns. Fix or flag in the same commit.
9. Deliberate before coding. Produce an edge-case checklist, then a one-paragraph plan stating what's guarded and what's deliberately not done — before implementation.
10. Tests define the product. A red test is fixed in product code, seed data, or config. Never re-pin an assertion — the only sanctioned edits to an assertion are compile-blocking typos, framework misuse that never caught a bug, and stripping banned patterns. Removing a test is a separate question with a separate bar: TEST-NODELETE.
11. Full unfiltered gates before push. Never scope the test run to changed files as the gate. If anything is red, don't push.
12. Docs ship in the same commit as the change they describe. No "docs follow-up later."
13. Raise and stop. Auto-merge is off by default: run the full review loop, then surface the PR for the owner to merge.
14. Evidence over assertion. Every claim of compliance carries the command and its actual output. A green suite is not evidence that nothing regressed — deleting or weakening a test to reach green is a blocker, and a comment explaining a removal is the tell, not the justification. references/verification.md carries the checks.