docs: reframe project-plan.md under VeriPath name lock
This commit is contained in:
@@ -1,13 +1,13 @@
|
|||||||
# Digital Operations Partner (DOP) - High-Level Project Plan
|
# VeriPath - High-Level Project Plan
|
||||||
|
|
||||||
Last Updated: August 10, 2026
|
Last Updated: August 17, 2026
|
||||||
Status: Pre-Build / Blueprint Phase
|
Status: Pre-Build / Blueprint Phase
|
||||||
Current Stage: Foundation Locked, Ready for Blueprinting
|
Current Stage: Foundation Locked, Ready for Blueprinting
|
||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 1. Project Objective
|
## 1. Project Objective
|
||||||
To build and launch a differentiated marketing and operating system for Digital Operations Partner (DOP) that solves "Silent Customer Loss" for local businesses. DOP will leverage a "Cold Audit → Threat Diagnosis → Focused PoC → Retainer" commercial motion, combining agent-assisted analysis with strict human oversight to improve upon the narrower, "done-for-you AI search visibility" model seen in competitors like Bizl.com.
|
To build and launch a differentiated marketing and operating system for VeriPath that solves "Silent Customer Loss" for local businesses. VeriPath will leverage a "Cold Audit → Threat Diagnosis → Focused PoC → Retainer" commercial motion, combining agent-assisted analysis with strict human oversight to improve upon the narrower, "done-for-you AI search visibility" model seen in competitors like Bizl.com.
|
||||||
|
|
||||||
## 2. Core Positioning (Locked)
|
## 2. Core Positioning (Locked)
|
||||||
* The Problem: Silent Customer Loss (Discovery Failure + Customer Path Leakage).
|
* The Problem: Silent Customer Loss (Discovery Failure + Customer Path Leakage).
|
||||||
@@ -30,7 +30,7 @@ To build and launch a differentiated marketing and operating system for Digital
|
|||||||
|
|
||||||
### Phase 1: Blueprint & Strategy Lock (Current Phase)
|
### Phase 1: Blueprint & Strategy Lock (Current Phase)
|
||||||
*Goal: Finalize the structural framing before any code or complex design work begins.*
|
*Goal: Finalize the structural framing before any code or complex design work begins.*
|
||||||
- [ ] Homepage Framing: Draft the remaining homepage sections (e.g., Proof/Social Proof, The DOP Difference/Methodology, Final CTA).
|
- [ ] Homepage Framing: Draft the remaining homepage sections (e.g., Proof/Social Proof, The VeriPath Difference/Methodology, Final CTA).
|
||||||
- [ ] Asset Strategy: Decide how the 5 completed live Cold Audits will be presented to prospects (e.g., gated PDF reports, interactive web dashboards, or narrative case studies).
|
- [ ] Asset Strategy: Decide how the 5 completed live Cold Audits will be presented to prospects (e.g., gated PDF reports, interactive web dashboards, or narrative case studies).
|
||||||
- [ ] Brand & Identity: Lock down the final brand name confirmation, visual direction, and design system fundamentals.
|
- [ ] Brand & Identity: Lock down the final brand name confirmation, visual direction, and design system fundamentals.
|
||||||
- [ ] Tech Stack Decision: Choose the implementation path (e.g., Next.js/React + Headless CMS, Webflow, Framer, or purely static HTML) that best supports the audit intake mechanism.
|
- [ ] Tech Stack Decision: Choose the implementation path (e.g., Next.js/React + Headless CMS, Webflow, Framer, or purely static HTML) that best supports the audit intake mechanism.
|
||||||
@@ -59,7 +59,7 @@ To build and launch a differentiated marketing and operating system for Digital
|
|||||||
---
|
---
|
||||||
|
|
||||||
## 5. Evidence Governance & Human Oversight
|
## 5. Evidence Governance & Human Oversight
|
||||||
*The DOP trust model — operationalized human supervision over agent-assisted findings.*
|
*The VeriPath trust model — operationalized human supervision over agent-assisted findings.*
|
||||||
* **The Evidence Hierarchy:** All findings are classified as either Tier 1 (Verified) or Tier 2 (Indicative).
|
* **The Evidence Hierarchy:** All findings are classified as either Tier 1 (Verified) or Tier 2 (Indicative).
|
||||||
* **The Fallback Protocol:** If a proposed Tier 1 classification is rejected by human review, it automatically defaults to Tier 2, *unless* the human reviewer explicitly discards the finding as noise or requests more evidence from the agent-assisted backend. No unverified or rejected finding is ever presented to a client as Tier 1.
|
* **The Fallback Protocol:** If a proposed Tier 1 classification is rejected by human review, it automatically defaults to Tier 2, *unless* the human reviewer explicitly discards the finding as noise or requests more evidence from the agent-assisted backend. No unverified or rejected finding is ever presented to a client as Tier 1.
|
||||||
* **Sign-off:** Every client-facing finding requires explicit human approval.
|
* **Sign-off:** Every client-facing finding requires explicit human approval.
|
||||||
|
|||||||
Reference in New Issue
Block a user