docs: add execution roadmap v0.1
This commit is contained in:
@@ -0,0 +1,100 @@
|
||||
# Execution Roadmap — v0.1
|
||||
|
||||
**Date:** 2026-08-13
|
||||
**Status:** Accepted
|
||||
**Owner:** Tony / VeriPath
|
||||
**Scope:** Strategy | Product
|
||||
|
||||
**Strategic objective:** Build VeriPath into a paid, human-supervised verification service that produces trusted, agent-readable local-business records.
|
||||
|
||||
GeoLocal is deferred. All active work focuses on audits and clean business data.
|
||||
|
||||
---
|
||||
|
||||
## Phase 0 — Governance Reset
|
||||
**Timeframe:** 1–2 days
|
||||
|
||||
- Record current company philosophy and product boundary
|
||||
- Establish decision-record convention
|
||||
- Document system-of-record boundaries
|
||||
|
||||
**Gate:** Philosophy recorded, roadmap accepted, next clients scoped.
|
||||
|
||||
---
|
||||
|
||||
## Phase 1 — Contract Layer
|
||||
**Timeframe:** Week 1
|
||||
|
||||
- Canonical Business Record v0.1.1
|
||||
- Evidence and Freshness Policy v0.1
|
||||
- Record storage and classification convention
|
||||
|
||||
**Gate:** Schema validates, evidence policy classifies real data, GeoLocal handoff described without GeoLocal changes.
|
||||
|
||||
---
|
||||
|
||||
## Phase 2 — Phoenix and Overcome Vertical Slice
|
||||
**Timeframe:** Weeks 2–3
|
||||
|
||||
- Canonical business record for Phoenix Salon + Spa
|
||||
- Canonical business record for Overcome Fitness
|
||||
- AI representation audit
|
||||
- Silent Customer Loss Map
|
||||
- Owner-review draft
|
||||
|
||||
**Gate:** Two complete draft records, findings mapped to evidence, delivery time measured.
|
||||
|
||||
---
|
||||
|
||||
## Phase 3 — Owner Review and Commercial Offer
|
||||
**Timeframe:** Weeks 3–4
|
||||
|
||||
- Deliver VeriPath Agent Readiness Review
|
||||
- Test paid engagement ($500–$2,000 range)
|
||||
- Document which findings the owner values
|
||||
- Record pricing feedback
|
||||
|
||||
**Gate:** At least one paid engagement or clear reason for non-payment documented.
|
||||
|
||||
---
|
||||
|
||||
## Phase 4 — Manual Monitoring Loop
|
||||
**Timeframe:** Weeks 4–6
|
||||
|
||||
- Track hours, booking links, NAP, services, AI answers, reviews
|
||||
- Deliver monthly or biweekly change report
|
||||
- Discover useful alerts versus noise
|
||||
|
||||
**Gate:** Three businesses monitored with the same workflow, recurring issue detected before owner notices.
|
||||
|
||||
---
|
||||
|
||||
## Phase 5 — Minimal Automation
|
||||
**Timeframe:** Weeks 6–10
|
||||
|
||||
- Automate proven repetition (extraction, diffing, freshness, report scaffolding)
|
||||
- No Postgres, Celery, or dashboard until client volume justifies
|
||||
|
||||
**Gate:** Workflow faster than manual baseline, accuracy maintained, failures visible.
|
||||
|
||||
---
|
||||
|
||||
## Phase 6 — GeoLocal Internal Handoff
|
||||
**Timeframe:** Deferred until proven
|
||||
|
||||
Use approved VeriPath records as fixtures. Test read-only retrieval, freshness display, and provenance. No commercial deployment, ownership transfer, or external access.
|
||||
|
||||
**Gate:** Internal agent retrieves approved records with correct freshness and action boundaries.
|
||||
|
||||
---
|
||||
|
||||
## First Milestone
|
||||
|
||||
Two local businesses, one repeatable audit method, one paid engagement, one maintained canonical record.
|
||||
|
||||
---
|
||||
|
||||
## Related documents
|
||||
|
||||
- `docs/decisions/2026-08-13-narrowing-scope-veripath-first.md`
|
||||
- `docs/decisions/2026-08-12-veripath-system-of-record-boundary.md`
|
||||
Reference in New Issue
Block a user