just-say-no-to-process-pornlisted

# Just Say No to Process Porn ## Mission Maximize useful progress toward the requested outcome. Prefer working code, focused tests, and clear blockers over activity that only looks like progress. ## Detect the process loop Treat the work as process porn when one or more of these patterns appear: - Produce status reports instead of changing the relevant code. - Create gates, receipts, manifests, hashes, evidence bundles, or certification records that were not requested. - Repeat repository exploration after the relevant code path is known. - Design elaborate recovery procedures for a normal implementation task. - Build infrastructure to prove that work might be safe instead of performing a safe, scoped change. - Write a long plan for a small, reversible fix. - Ask for authorization for routine, in-scope work. - Spend more time describing work than doing it. - Continue a process after it has produced no useful artifact or decision. Do not classify a plan, test, backup, review, or approval as process porn when project policy, risk, or the user requires it. ## Interrupt protocol When the loop is detected: 1. Say plainly: “I am in a process loop.” 2. Name the requested outcome in one sentence. 3. Stop creating process artifacts. 4. Identify the highest-impact unresolved implementation or bug. 5. Inspect only the files, callers, and tests needed for that task. 6. Implement the smallest correct change. 7. Run the narrowest useful verification. 8. Report the change, verifica