21 lines
1.7 KiB
Markdown
21 lines
1.7 KiB
Markdown
# DOP Agent Charter — Path Definition (v1.1)
|
||
|
||
## Non-Negotiables
|
||
- Mission: Prevent Silent Customer Loss for local service businesses.
|
||
- V1 Scope Exclusions remain absolute (no social production, paid ads, website redesign, branding, full SEO campaigns, CRM/email as core offerings).
|
||
- Evidence Model: Tier 1 (Verified) vs Tier 2 (Indicative). Agents may propose; humans approve final tier before client-facing use.
|
||
- Operating Rule: Agents detect and draft. Humans approve before any client-facing publish.
|
||
- Order of work: Users → Problems → Requirements → Workflows → Agents → Tools. Do not invert.
|
||
- **First validation client:** Any local service business that completes Layers 1–3 with real (owner-provided or otherwise non-invented) data may serve as the economics and proof anchor. No single named client is forced.
|
||
- All lasting outputs must be proposed as files under the existing docs/ structure.
|
||
|
||
## Documented exception (2026-07 / 2026-08)
|
||
Earlier Charter language named Phoenix Salon + Spa as the forced first real data source. That requirement is **superseded**. Overcome Fitness was opened as the first non-Phoenix Draft Benchmark for cold-audit tooling and Layer 1a/2 practice. Phoenix remains a valid future validation client if economics access is obtained; it is not a sequencing gate.
|
||
|
||
## Current Goal of This Agent Mixture
|
||
Produce a clean, layered path from the current definition state into a completed first Proof-of-Concept, with explicit entry/exit criteria for each layer and clear data requirements.
|
||
|
||
## Role Discipline
|
||
Each agent stays strictly inside its assigned layer. No jumping ahead to tools or full agent team design until workflows are explicit.
|
||
No inventing client numbers. Flag every placeholder that still requires real client data.
|