Standardization Pass: Added 00-09 core governance set (Arena Integration Pivot)

docs/08-CHANGE-REQUEST.md

@@ -1,33 +1,27 @@
-# Change Request
+# Change Request — CR-001: UI Strategy Pivot
 
 ## Summary
-
-- Proposed change: (none pending)
+- **Proposed change**: Abandon the creation of a standalone `stoned-web` server and instead implement Stoned.AI functionality as a new "Human-in-the-Loop" mode within the existing **Arena** project (`/home/svc-admin/ai-projects/projects/arena`).
 
 ## Reason
-
-- Why is the current governing plan insufficient or wrong?
+- The user explicitly requested to "use the existing Arena WebUI."
+- Reusing the Arena infrastructure (SSE, TTS, Agent Runners) reduces implementation time and maintenance overhead.
+- Centralizing multi-agent and human-vs-AI orchestration on a single port (8765) and domain (`arena.accursedbinkie.com`) provides a more cohesive operator experience.
 
 ## Requested Document Changes
-
-- Document:
-- Proposed revision:
+- **02-ARCHITECTURE-PLAN.md**: Update to reflect that Arena is the primary runtime, not a standalone server.
+- **03-IMPLEMENTATION-PLAN.md**: Pivot phases to "Arena Integration" rather than "Greenfield Build."
 
 ## Impact
-
-- Scope impact:
-- Architecture impact:
-- Risk impact:
-- Testing impact:
-- Timeline impact:
+- **Scope impact**: Low (Functionality remains the same, delivery method changes).
+- **Architecture impact**: High (Stoned.AI becomes a feature of Arena).
+- **Risk impact**: Medium (Changes to Arena could affect existing AI-vs-AI workflows).
+- **Testing impact**: Requires regression testing of Arena's standard mode.
+- **Timeline impact**: Positive (Faster delivery).
 
 ## Recommendation
-
-- Approve
-- Reject
-- Defer
+- **Approve**: This aligns with the user's preference for a unified interface.
 
 ## Approval
-
-- User decision:
-- Supervisor recommendation:
+- **User decision**: Pending
+- **Supervisor recommendation**: Approve