Skip to content

Latest commit

 

History

History
24 lines (16 loc) · 2.42 KB

README.md

File metadata and controls

24 lines (16 loc) · 2.42 KB

Selected Concept

Status: Decided — concept selected 2026-09-12

The locked direction is a client-facing body record with a small coach session mode. Stephen records an explanation, reviews agent-proposed region updates and confirms them; the client explores and adds observations. Vite/React and the existing Node backend are the selected base; viewer expansion and real agent extraction are required. CopilotKit is conditional under ADR-006. Technical feasibility still needs the T-003 spike.

Concept file map

The detailed acceptance contract is the PRD. Architectural rationale lives in ADRs; proposed implementation interfaces are in technical contracts. This folder remains the concise concept and pitch reference.

Current demo loop: existing body record → Start session → record → Finish → agent proposes regional updates → coach reviews/confirms → client explores → client adds an observation.

This is the target consultation loop, not a claim about the current Vite prototype. The combined implementation status records the existing assessment, recovery, routine, WhatsApp and golf work preserved alongside this brief. P0 exclusions do not require deleting those existing features.

  1. 01-proposition.md — concise concept, problem, outcome, and non-goals.
  2. 02-users-and-environment.md — target users, setting, jobs, relationships, and contextual advantage.
  3. 03-agent-workflow.md — trigger, perception, reasoning, tools, action, state, and human control.
  4. 04-positioning.md — category, alternatives, differentiation, and “why here rather than ChatGPT.”
  5. 05-technical-architecture.md — chosen stack, components, data flow, integration boundaries, and failure handling.
  6. 06-scope-and-requirements.md — golden path, acceptance criteria, non-goals, and stretch scope.
  7. 07-risks-and-open-questions.md — product, technical, safety, demo, and evidence risks.
  8. 08-demo-story.md — two-minute narrative, prepared data, operator steps, and fallback.

Keep these files compact. Their purpose is to keep product, engineering, and pitch decisions aligned during a short build.