Jason Hall
fcd93ee0af
Stoned.AI — live-streamed human + AI conversation show, both sides voiced via local Kokoro TTS. Governance docs 00-09, README, .gitignore. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
66 lines
2.9 KiB
Markdown
66 lines
2.9 KiB
Markdown
# Project Charter
|
|
|
|
## Project Name
|
|
|
|
- Name: Stoned.AI
|
|
|
|
## Purpose
|
|
|
|
- Stoned.AI is a live-streamed, unscripted conversation show between a human host (Jason) and an AI.
|
|
- It fills a gap in the AI content space: instead of productivity tutorials, it is genuine, funny, and curious conversation — going wherever the discussion leads.
|
|
- It exists now because the concept was proven in a single conversation on April 1, 2026, and the local TTS and AI infrastructure to support it already exists on `svc-ai`.
|
|
|
|
## Goals
|
|
|
|
- Goal 1: Build a browser-based host interface where Jason types his side of the conversation and the AI responds, with both sides voiced via local Kokoro TTS.
|
|
- Goal 2: Provide a clean OBS-capturable broadcast view showing only the scrolling conversation feed — no controls, styled for streaming.
|
|
- Goal 3: Support at least one AI backend for responses (Codex or Gemini initially, Claude added after initial launch).
|
|
|
|
## Non-Goals
|
|
|
|
- Not an AI-to-AI debate tool. One human, one AI. That is the format.
|
|
- Not a productivity or workflow tool. The output is entertainment and conversation, not work product.
|
|
- Not a replacement for Arena. This is a separate project with a separate purpose.
|
|
- Not building a mobile app, desktop app, or browser extension. Web only for the initial version.
|
|
|
|
## Users / Stakeholders
|
|
|
|
- Primary user: Jason (host)
|
|
- Audience: YouTube live stream viewers
|
|
- Secondary stakeholders: none currently
|
|
|
|
## Constraints
|
|
|
|
- Must run on `svc-ai` (AMD Ryzen 5 3600, ~14 GiB RAM, no GPU).
|
|
- Must reuse the existing Kokoro TTS stack from the Arena project (`/opt/models/kokoro`, `pykokoro`).
|
|
- Must be capturable by OBS Studio as a browser source.
|
|
- No microphone dependency — both sides are text-in, voice-out.
|
|
- Host types their side; the system voices it. No speech-to-text.
|
|
|
|
## Deliverables
|
|
|
|
- Deliverable 1: A working `stoned-web` server with host input, AI response, and Kokoro TTS for both sides.
|
|
- Deliverable 2: A `/broadcast` view (no controls, OBS-ready) and a `/host` control view (input box, voice selection, session management).
|
|
- Deliverable 3: At least one wired AI backend capable of generating conversational responses.
|
|
- Deliverable 4: Per-speaker Kokoro voice assignment (host voice and AI voice are independently selectable).
|
|
|
|
## Success Definition
|
|
|
|
- Jason can type a message, hear it spoken in his chosen voice, the AI responds, and the AI response is spoken in its chosen voice.
|
|
- The broadcast view displays cleanly in OBS as a browser source.
|
|
- A full test conversation runs end to end without manual intervention.
|
|
- Jason can go live on YouTube using this as the audio and visual source.
|
|
|
|
## Authority
|
|
|
|
- User approval required: yes
|
|
- Supervisor revision required for charter changes: yes
|
|
|
|
## Signature
|
|
|
|
- Document role: governing
|
|
- Created by: Claude (supervisor)
|
|
- Created at: 2026-04-12
|
|
- Revision status: initial
|
|
- Future revision rule: this document may be revised only by the user or by an explicitly authorized supervisor revision
|