Mark applicability and provenance on entries that do not apply everywhere #1

New Issue

Closed

opened 2026-08-17 22:51:04 -05:00 by null · 0 comments

null commented

2026-08-17 22:51:04 -05:00

Owner

This template is copied into every project, and some of what Batch 01 adds will not apply to all of them: a static site has no refunds, a library has no uptime.

Establish two markers, on different axes, and use them consistently:

Applicability — (only where money moves), (only for a deployed service). Answers whether this project has to do it at all.
Provenance — (precautionary). Answers whether the rule was earned in this portfolio or borrowed from outside it.

They are independent: rate limiting is universally applicable and precautionary; refund handling is conditional and thoroughly proven elsewhere. Collapsing them into one word loses the distinction that tells a reader whether to argue with a rule or simply delete it.

The instruction that goes with the marker is ClaudeQAPlan.md's own rule generalised: if it does not apply, delete it. A pass that never applies is noise; a pass that is always skipped is a lie. The same is true of a checklist row and of a whole document.

Do this first — the other issues in this batch use the vocabulary.

Verify: docs/DOC_TRUST_MAP.md explains both markers, and at least one entry in docs/security/SECURITY_CHECKLIST.md and one in docs/qa/ClaudeQAPlan.md carries each kind.

This template is copied into every project, and some of what Batch 01 adds will not apply to all of them: a static site has no refunds, a library has no uptime. Establish two markers, on different axes, and use them consistently: - **Applicability** — *(only where money moves)*, *(only for a deployed service)*. Answers whether this project has to do it at all. - **Provenance** — *(precautionary)*. Answers whether the rule was earned in this portfolio or borrowed from outside it. They are independent: rate limiting is universally applicable and precautionary; refund handling is conditional and thoroughly proven elsewhere. Collapsing them into one word loses the distinction that tells a reader whether to argue with a rule or simply delete it. The instruction that goes with the marker is ClaudeQAPlan.md's own rule generalised: **if it does not apply, delete it.** A pass that never applies is noise; a pass that is always skipped is a lie. The same is true of a checklist row and of a whole document. Do this first — the other issues in this batch use the vocabulary. Verify: docs/DOC_TRUST_MAP.md explains both markers, and at least one entry in docs/security/SECURITY_CHECKLIST.md and one in docs/qa/ClaudeQAPlan.md carries each kind.