Merge pull request #2 from FocusedObjective:codex/update-verification-process-for-capabilities

Refresh website problem bullets to reflect prompt-driven capability drift

Author: PredictabilityAtScale

website/index.html

@@ -114,12 +114,10 @@ <h2>AI coding makes delivery faster. It also makes intent easier to lose.</h2>
           <div class="risk-list">
             <p>That creates a new kind of software risk:</p>
             <ul>
-              <li>Code is generated without clear product intent.</li>
-              <li>Requirements live in conversations instead of the repo.</li>
-              <li>Verification is added after the fact, if at all.</li>
-              <li>Product managers lose visibility into what the system can actually do.</li>
-              <li>Developers reverse-engineer intent from tickets and code.</li>
-              <li>AI agents optimize for producing code, not preserving capability.</li>
+              <li>Requirements now live in prompts instead of tickets, then drift into stale specs and plans.</li>
+              <li>As the codebase grows, it gets harder to verify that new and existing features still fulfill capabilities.</li>
+              <li>Humans can verify capabilities against intent, but intent is often lost after prompting and implementation.</li>
+              <li>In PR reviews, teams have to tease out how capabilities have grown, shrunk, or changed.</li>
             </ul>
           </div>
         </div>