solpbc.org
open source is social v-it.org
docs: add YAGNI + verify-before-claim to development principles
Polish from the CIO AGENTS.md audit (2026-06-22) — fills the two coding
principles a hopper lode most often re-derives without.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
author
Jer Miller
co-author
Claude Opus 4.8 (1M context)
date
(Jun 22, 2026, 9:39 PM -0600)
commit
72f51a05
72f51a05eec1d2fa72f19fc1a29b97990594ca3b
parent
171d6cf7
171d6cf787996ff543dcd4cd5fb90b11c4c7483e
+3
-1
+3
-1
CLAUDE.md
+3
-1
CLAUDE.md
···
28
28
29
29
- **Simple code** - Prefer plain functions. Keep scripts self-contained.
30
30
- **DRY, KISS** - Extract common logic, prefer simple solutions.
31
-
- **Fail fast** - Validate inputs and external state early. Clear error messages.
31
+
- **YAGNI** - Don't build for cases that don't exist yet; no speculative flags, options, or abstractions. No backwards-compatibility shims — update call sites directly when you rename or move something.
32
+
- **Fail fast** - Validate inputs and external state early. Clear error messages. Surface failures, don't swallow them into a success-looking result.
33
+
- **Verify before you claim** - Recall is a hypothesis, not evidence. Verify atproto/Jetstream behavior, an API shape, or a dependency's defaults against the live source before it lands in code or a commit — a quick check beats a reversal. Contract tests round-trip the real serialization boundary, not a mock of both sides.
32
34
- **Vocabulary alignment** - `VOCAB.md` is the source of truth for all project terminology. All project descriptions, CLI help strings, documentation, and skill files must use terminology consistent with VOCAB.md. When VOCAB.md is updated, propagate changes to every file that references vit's vocabulary in the same commit.
33
35
34
36
## Testing Standards