docs: record scope-narrowing decision — VeriPath first, GeoLocal deferred

2026-08-12 23:11:20 +00:00
parent 003820f92c
commit 95d235454d
1 changed files with 28 additions and 0 deletions
@@ -0,0 +1,28 @@
+# Decision: Narrowing Scope — VeriPath First, GeoLocal Deferred
+
+**Date:** 2026-08-13  
+**Status:** Accepted  
+**Owner:** Tony / VeriPath  
+**Scope:** Strategy | Product | Operations  
+
+## Context
+The initial execution plan included parallel tracks for VeriPath (audits/data) and GeoLocal (internal agent handoff). This creates operational distraction and risks premature optimization of downstream infrastructure before the core audit workflow is proven, repeatable, and generating revenue. We need to focus strictly on what we can control right now.
+
+## Decision
+Defer all GeoLocal integration, handoff testing, and architectural dependencies. Focus 100% of current engineering and operational effort on VeriPath: executing audits, mapping silent customer loss, and producing clean, AI-friendly canonical business records. GeoLocal is now strictly deferred context, not an active dependency or sprint goal.
+
+## Alternatives considered
+- Continuing parallel internal testing of GeoLocal handoffs (Rejected: divides focus).
+- Building automated downstream APIs before the manual audit is perfected (Rejected: violates "crawl before run" principle).
+
+## Consequences
+- **Easier:** Achieving the first paid audit and recurring monitoring contract. Maintaining strict evidence discipline.
+- **Harder:** We will not have a working agent-routing prototype in the short term.
+- **Prohibited:** Any engineering time spent on MCP servers, agent gateways, or GeoLocal fixture testing until the core audit workflow is fully productized and generating recurring revenue.
+
+## Revisit trigger
+When VeriPath has secured at least three paying monitoring clients and the manual audit workflow is fully repeatable, measured for time/cost, and partially automated.
+
+## Related documents
+- `docs/roadmap/execution-roadmap-v0.1.md`
+