From 5fd1529e1ebfa5a5709df1b7ced4afef53342187 Mon Sep 17 00:00:00 2001 From: Ty Date: Mon, 3 Aug 2026 05:12:17 +0000 Subject: [PATCH] Amend Charter: validation client rule + Overcome exception; remove forced Phoenix --- docs/agents/agent-charter-v1.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/agents/agent-charter-v1.md b/docs/agents/agent-charter-v1.md index 9831898..ed2a1a2 100644 --- a/docs/agents/agent-charter-v1.md +++ b/docs/agents/agent-charter-v1.md @@ -1,4 +1,4 @@ -# DOP Agent Charter – Path Definition (v1) +# DOP Agent Charter — Path Definition (v1.1) ## Non-Negotiables - Mission: Prevent Silent Customer Loss for local service businesses. @@ -6,12 +6,15 @@ - 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. -- Phoenix Salon + Spa is the forced first real data source for economics and proof. +- **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 Phoenix data. +No inventing client numbers. Flag every placeholder that still requires real client data.