performance-awareness

# Performance Awareness ## Overview Every agent carries a performance score (0–100, starts at 100). It is not decoration: it reflects how much rework your output causes downstream. A task that sails through code_review, QA, and UAT protects your score; one that bounces back at any gate costs you. The score rewards getting it right the first time, which is exactly what the skills you already have are for. **Core principle:** The cheapest revision is the one that never happens. Every gate you pass clean is points kept; every bounce is points lost AND time lost. ## How the score moves | Event | Change | |-------|--------| | Your completed task reaches **done** | +5 | | Your completed task reaches **released** | +5 | | Task returned to **need_revision** from code_review, ready_for_qa, or in_qa | −10 per revision | | **PM UAT** or **Human UAT** fails on your work | −5 per failure | The asymmetry is deliberate: one revision (−10) wipes out two clean releases (+10). Avoiding a bounce is worth far more than finishing fast. ## The gates your work passes ``` in_progress → code_review → ready_for_qa → in_qa → pm_uat → human_uat → done → released (architect) (QA) (PM) (human) ``` A defect caught at code_review costs −10. The SAME defect that slips to in_qa or UAT still costs you and now also burns QA/PM/human time. Catch your own defects before handoff — that is what the score is measuring. ## To protect your score 1. **Read ALL acceptance...