rnd-buildinglisted

# R&D Building Implement ONE assigned task against its pre-registered success criteria. Write the test first. Watch it fail. Write minimal code to pass. Produce verification artifacts for the independent Verifier. ## The Iron Laws ``` 1. NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST 2. NO SILENT DEVIATIONS FROM THE PRE-REGISTERED APPROACH 3. DO NOT VERIFY YOUR OWN WORK 4. USE WRITE/EDIT TOOLS TO CREATE AND MODIFY FILES — NEVER BASH HEREDOCS 5. IF SLOP-GATE RETURNS WARN OR FAIL WITH ANY SEVERITY 3+ MATCH, RE-EDIT IMMEDIATELY — DO NOT DEFER 6. WHEN YOU HIT AN ISSUE (ERROR, WARNING, BROKEN TEST, BUG, GAP), FIX IT OR LOG IT TO found-issues.jsonl WITH decision="fixed"|"escalated" — SILENT DISMISSAL IS NOT AN OPTION 7. EXPLAIN BEFORE YOU WRITE — ONE LOGICAL CHANGE PER WRITE/EDIT, NOT WALLS OF CODE 8. DO NOT EMBED PIPELINE TASK IDs IN PROJECT CODE — NO TASK IDs IN COMMENTS, TEST NAMES, OR VARIABLE NAMES (RND ARTIFACT FILES IN $RND_DIR ARE EXEMPT) ``` ### 0. Resolve RND_DIR ```bash RND_DIR="$("${CLAUDE_PLUGIN_ROOT}/lib/rnd-dir.sh")" ``` ### 1. Read Your Assignment Find your task in `$RND_DIR/protocol.md`. Read its pre-registration — especially success criteria, approach, and the `fulfills` field (which links to specific VAL-AREA-NNN assertions in the Validation Contract). Also read: - **Environment Setup** — runtime, package manager, dependencies, install commands - **Testing Strategy** — test framework, baseline count, exact run commands for unit/integration/live tests - **