Add/Update docs/project-plan.md (Qwen+Leonard collab; evidence governance + static stack)
This commit is contained in:
+17
-8
@@ -37,12 +37,13 @@ To build and launch a differentiated marketing and operating system for Digital
|
|||||||
- [ ] Website Copy Expansion: Draft all remaining pages (Services/Methodology, About/Trust Model, Contact/Request Audit).
|
- [ ] Website Copy Expansion: Draft all remaining pages (Services/Methodology, About/Trust Model, Contact/Request Audit).
|
||||||
- [ ] Audit Workflow Definition: Document the internal operational flow for how a requested Cold Audit is processed, agent-assisted, human-verified, and delivered.
|
- [ ] Audit Workflow Definition: Document the internal operational flow for how a requested Cold Audit is processed, agent-assisted, human-verified, and delivered.
|
||||||
|
|
||||||
### Phase 3: Development & Integration
|
### Phase 3: Build & Integration (v1: Static + Tailwind)
|
||||||
*Goal: Build the public-facing presence and the internal delivery engine.*
|
*Focus: Rapid deployment of the marketing engine and Live Teardowns.*
|
||||||
- [ ] Scaffold Repo: Initialize the website codebase and establish deployment pipelines (CI/CD).
|
- [ ] Scaffold Static Site: Initialize HTML/Tailwind structure (`/web` directory) with #b8402c brand config.
|
||||||
- [ ] Frontend Build: Implement the homepage and secondary pages based on approved copy and design.
|
- [ ] Build Homepage: Implement the blueprint sections (Hero, Problem, Proof in Action, 3 Domains, Engagement Ladder).
|
||||||
- [ ] Audit Request Mechanism: Build the frontend form and backend routing for prospects to request a Layer 1a Cold Audit.
|
- [ ] Build Live Teardown Pages: Create the interactive scrollable pages for the 5 foundational audits (Gilmore, Martel, CPFD, Gordon, Above the Gate).
|
||||||
- [ ] Internal Tooling: Set up the internal dashboard/process for AI agents to generate findings and humans to review/approve them.
|
- [ ] Form & Backend Integration: Wire the Layer 1a Cold Audit intake form to Formspree or the VPS (74.208.111.99) Node/Flask endpoint.
|
||||||
|
- [ ] Deploy: Push to production via the static-site-sandbox-deploy workflow.
|
||||||
|
|
||||||
### Phase 4: Launch & GTM Execution
|
### Phase 4: Launch & GTM Execution
|
||||||
*Goal: Soft launch, execute outreach, and secure initial PoCs/Retainers.*
|
*Goal: Soft launch, execute outreach, and secure initial PoCs/Retainers.*
|
||||||
@@ -53,7 +54,15 @@ To build and launch a differentiated marketing and operating system for Digital
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 5. Governance & Operational Rules
|
## 5. Evidence Governance & Human Oversight
|
||||||
|
*The DOP 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 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.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 6. Governance & Operational Rules
|
||||||
To maintain the core differentiator, the following rules apply across all phases of build and execution:
|
To maintain the core differentiator, the following rules apply across all phases of build and execution:
|
||||||
1. No "AI Fluff": Every claim on the website and every finding in an audit must map to a specific evidence tier.
|
1. No "AI Fluff": Every claim on the website and every finding in an audit must map to a specific evidence tier.
|
||||||
2. Human-in-the-Loop: No automated report is sent to a prospect without a human partner reviewing and approving the findings.
|
2. Human-in-the-Loop: No automated report is sent to a prospect without a human partner reviewing and approving the findings.
|
||||||
@@ -61,7 +70,7 @@ To maintain the core differentiator, the following rules apply across all phases
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 6. Next Immediate Actions
|
## 7. Next Immediate Actions
|
||||||
1. Commit this plan: Add docs/project-plan.md to the repository to lock the project skeleton.
|
1. Commit this plan: Add docs/project-plan.md to the repository to lock the project skeleton.
|
||||||
2. Homepage Blueprint: Begin drafting the copy and structure for the remaining homepage sections (Proof, Differentiators, Footer).
|
2. Homepage Blueprint: Begin drafting the copy and structure for the remaining homepage sections (Proof, Differentiators, Footer).
|
||||||
3. Tech Stack Huddle: Evaluate and select the web framework/CMS that best supports the "Cold Audit" intake and delivery mechanism.
|
3. Tech Stack Huddle: Evaluate and select the web framework/CMS that best supports the "Cold Audit" intake and delivery mechanism.
|
||||||
|
|||||||
Reference in New Issue
Block a user