docs: rewrite PRD, Spec, and Implementation Plan for clarity

Plain-language rewrite of the three AIBook.fun planning docs, with a product review folded in: - Name one core loop (read -> run -> share) and a single North-Star metric (activation), reported ahead of the fundraising numbers. - Layer the product: v1 = the core loop; contributor economy, cohorts, agent-onboarding, and the ecosystem funnel become explicit later layers instead of co-equal launch goals. - Add the "Minimum Lovable Library" launch gate: seed 15-20 tested workflows ourselves before asking anyone to pay, rather than betting the launch on the crowd filling an empty shelf. - Reframe the contributor incentive honestly: today's mechanic is affiliate referral, not payment for writing workflows; make paid contribution a launch-blocking decision. - Force the subscription-vs-lifetime pricing tension into a reasoned decision. - Split the product-validation bar from the funding floor ("funded" != validated). - Lead the pitch with utility; make ownership the retention layer. - Trim governance to the two gates that matter (no-crypto scrub, truth in claims). - Turn the domain "decision" into a same-day chore. - Translate internal jargon, handles, and merge-history out of the doc bodies. Old versions preserved in git history; a field-by-field ID mapping can be produced on request.
2026-08-26 14:43:54 +01:00
parent cbcdccc889
commit 33c2af4359
3 changed files with 828 additions and 503 deletions
@@ -1,206 +1,392 @@
 ---
-title: "AIBook.fun — Product Requirements Document (CONSOLIDATED v1.0-DRAFT)"
+title: "AIBook.fun — Product Requirements Document"
 type: prd
-tags: [aibook, weown-ai, prj-031, prd, kickstarter, responsible-agentic-ai, social-education, okf, requirements]
 status: draft
-created: 2026-08-22
-source-of-truth: "https://github.com/CCCbotNet/fedarch/blob/main/_PROJECTS_/PRJ-031_WeOwnAI-Book.md"
-generated:
-  by: "AI:CCC-MAIT-S004-PAT-DeepSeek (SEAT-1 governance/OKF) + ProductBuzz [PAT] (Product Ops) — merged v0.2, amended v0.3"
-  at: "2026-08-22T15:36:00Z"
-verified:
-  - by: "curl github.com/CCCbotNet/fedarch (PRJ-031 SOT v3.2.1.3)"
-    at: "2026-08-22"
-  - by: "buzz channels list (relay) — bMAIT AiBook.fun channel desc"
-    at: "2026-08-22"
-sources:
-  - id: sot
-    resource: "https://github.com/CCCbotNet/fedarch/blob/main/_PROJECTS_/PRJ-031_WeOwnAI-Book.md"
-    note: "PRJ-031 v3.2.1.3 — tiers, goals, affiliate %, team, timing"
-  - id: spec
-    resource: "PLANS/AIBOOK_SPEC.md"
-    note: "Companion spec (merged v0.3) — pillars, scope, open decisions D-1..D-7"
-  - id: pb-prd
-    resource: "PLANS/AIBOOK/AIBOOK_PRD.md (ProductBuzz draft v0.1)"
-    note: "Parallel draft merged into this canonical — goals, personas, FR-1..FR-8, metrics, risks"
-  - id: pat-manual
-    resource: "AGENTS.md (PAT squad) + Product-Op Manual refs"
-    note: "4 actors (§3-4) · 3 floors · flyer rule · two-tab UX · ZDR stance · §8 claims register · §6.3 isolation · launch gates"
+owner: Patrick (Product)
+launch-target: 2026-09-26
+last-updated: 2026-08-26
 ---

 # 📚 AIBook.fun — Product Requirements Document
-**CONSOLIDATED v1.0-DRAFT** · 2026-08-22 · **ProductBuzz [PAT]** (Product Ops) + **CCC-MAIT-S004-PAT-DeepSeek** (SEAT-1 governance/OKF) · Owner: @pat · Commercial sign-offs: @GTM (R-011) · Companion: `AIBOOK_SPEC.md`, `AIBOOK_IMPLEMENTATION_PLAN.md`, PRJ-031 SOT v3.2.1.3 · **⛔ DRAFT — not a live claim. No R-011.** (v1.0-final naming reserved for R-011'd freeze.)
-> v1.0-DRAFT consolidation (2026-08-22T15:36:00Z, SEAT-1 after ProductBuzz self-review 15:22Z): trunk = v0.3. Folded R2 (FR-4.7 affiliate payout milestone ≤ W-2 of campaign end — restored from ProductBuzz v0.1 FR-5.3) · R3 (FR-3.4 WeOwn Chat ledger dogfooding note, CSV stays floor) · F1 (G0–G3 kept; no G4) · F2 (15/10/10/5 everywhere) + SEAT-1 S2 (FR-1.1 Risk #9 → Risk #4, refreshed register) · S3 (verified-block parity). v0.3 amendment history below:

-Legend: 🔴 must-have for 9/26 launch · 🟡 should-have (launch window) · 🟢 post-campaign.
+> **Status: DRAFT.** Dollar figures, dates past today, and commercial terms in this
+> document are planning assumptions, not commitments. Nothing here should be quoted
+> to backers or the public until the specific line is signed off (see
+> [§10 Open decisions](#10-open-decisions)). This revision rewrites the prior draft
+> for plain language and folds in a product review — see
+> [Appendix D](#appendix-d--what-changed-in-this-revision) for what moved and why.

 ---

-## 1. Background & problem
-WeOwnNet's Book pillar (PRJ-031, P0) lacked a product definition: what the Book *is*, whom it serves, how it educates, how it monetizes. SOT v3.2.1.3 (Mar 2026, APPROVED) carries the approved commercial skeleton and full campaign plan whose dates are superseded; the **9/26 relaunch** (relay-CONFIRMED) needs the product layer itself. This PRD keeps the SOT's approved commercial structure and adds content model, social education design, and requirements.
+## TL;DR

-**Problem statement:** Professionals drowning in AI hype have no shared, practice-grounded, community-owned place to learn Responsible Agentic AI — and WeOwnNet has no common literacy base to onboard its own humans and agents.
+AIBook.fun is a **crowd-written, practical field guide to using AI agents responsibly at
+work** — sold as an annual subscription, launched on Kickstarter on **September 26, 2026**.
+Its unit of content is not a chapter but a **workflow you can actually run**: a documented,
+tested recipe for getting a real job done with AI, complete with the guardrails.

-## 2. Goals & non-goals
-**Goals**
- **G-1** Stand up aibook.fun + Kickstarter live **9/26/2026**, funding ≥ $5K min / $35K target (DRAFT planning figures).
- **G-2** Define the Book as crowd-created, subscription, workflow-based artifact (Spec §4).
- **G-3** Launch with a demonstrable social-education loop (Read → Do → Share; Book Circles; Workflow-of-the-Week).
- **G-4** Every external claim claims-governed: nothing DRAFT/OPEN presented as final (§8 register).
- **G-5** Every backer enters the ecosystem funnel (AgencyPRO/PRJ-002) — backer→webinar→demo pipeline.
+The one thing that must work on day one: a reader opens a workflow, **runs it in ~15 minutes,
+and shares the result** with other readers. Everything else — the contributor economy, the
+cohort program, the agent-onboarding use case — is a layer we build *on top of* that loop
+after we've proven the loop works.

-**Non-goals (explicit)**
- No general-purpose AI chatbot or tool; this is a book/learning product.
- No regulated professional advice issued on the book's own authority.
- No NFT/token/Web3/blockchain/crypto language on any kickstarter-facing surface (hard constraint, KS policy).
- No building the eBookNFT platform yet (4 domains held; IDEA per SOT).
- No private multi-tenant infrastructure of any kind (not applicable; boundary preserved).
-
-## 3. Personas & actors (JTBD)
-| Persona | Core job | Success metric |
-|:--|:--|:--|
-| Reader/subscriber | Apply a documented RAAI workflow at work this week | Activation: reads 1 chapter + completes 1 Try-it within 14 days of backing |
-| Contributor | Publish a documented workflow, earn income/reputation | 1 accepted workflow within 90 days of joining |
-| Curator/co-author | Keep the quality bar | Curation SLA ≤ 10 working days per submission |
-| Affiliate | Refer backers, earn commission | First payout ≤ 1 cycle after referred payment (SOT/ops guardrail; dated milestone FR-4.7) |
-| Ecosystem prospect | Learn + take a stake | Backer → community join rate ≥ 40% of backers (DRAFT target) |
-| Agent (WeOwnNet-native) | Onboard via the Book corpus | Gate-0 completion = part of identity tier |
-
-## 4. Epics & functional requirements
-
-### EPIC 1 — Campaign system 🔴 (launch 9/26)
-| ID | Requirement | Pri | Acceptance |
-|:--|:--|:--|:--|
-| FR-1.1 | KS page per SOT sections: hero video (2–3 min, co-authors), problem, book, co-authors, 6 tiers ($10→$4,888), retreats, 5 stretch goals, FAQ ≥10, risks | 🔴 | Page passes **NFT-free scrub** (translation table; zero token/Web3/crypto) + KS category rules; final team review before submit (Risk #4 gate — PRD §7 refreshed register) |
-| FR-1.2 | Pre-launch engine: landing live on aibook.fun, email capture, 3-email sequence | 🔴 | **500+ emails before Day 1**; FluentCRM tags (`book-prelaunch`) via @LDC |
-| FR-1.3 | Affiliate live via Kickbooster.me (co-author 15% / community 10% / podcast 10% / press 5%; 30-day cookie, last-click) | 🔴 | Public signup page; widget on landing; co-authors invited Day 1 |
-| FR-1.4 | Launch playbook: Day-1 schedule, weekly cadence, dead-zone tactics, final-48h push (SOT) | 🔴 | Playbook reviewed @THY/@CEO pre-launch |
-| FR-1.5 | Campaign analytics: raised, backers, avg pledge, email list, CPC, affiliate share | 🔴 | Daily pulse vs SOT targets (Day-1 30% / 100 backers) |
-| FR-1.6 | Post-campaign: final update, backer comms, funds receipt (~14d), fulfillment announcement | 🟡 | Sequence staged pre-launch |
-
-### EPIC 2 — Content system 🔴
-| ID | Requirement | Pri | Acceptance |
-|:--|:--|:--|:--|
-| FR-2.1 | **Workflow Recipe schema** (Spec §4.1): problem/JTBD · actors · method with **visible tool returns** · safeguards · evidence · try-it · costs · author metadata | 🔴 | Schema + 3 filled examples pass QA + @pat review |
-| FR-2.2 | Chapter structure per vertical: RE · FA · Fractional C-Suite · Higher Ed · Communities · Tech/RAAI (SOT co-authors) | 🔴 | Outline + chapter owners confirmed |
-| FR-2.3 | Editorial pipeline: submission → co-author review → accept/revise → publish → updates tracked | 🔴 | Pipeline doc; first community submission processed end-to-end |
-| FR-2.4 | **2 sample chapters pre-launch** (backer preview) | 🔴 | Written + edited + verified (SOT PL-2) |
-| FR-2.5 | **3 learn-by-running kits** (clone-and-run; verified by actually running) | 🔴 | Kits run green before campaign |
-| FR-2.6 | Book = **OKF v0.2 knowledge bundle**; versioned annual editions; changelog per workflow | 🟡 | Bundle validates; renders to markdown + web |
-
-### EPIC 3 — Subscription & access 🔴/🟢
-| ID | Requirement | Pri | Acceptance |
-|:--|:--|:--|:--|
-| FR-3.1 | Digital access key post-campaign (SOT FAQ wording = approved copy base): key → PDF + web reader, 12 months, renew annually | 🟢 | Process + templates staged pre-launch |
-| FR-3.2 | Anchor tier $47/yr (DRAFT — @GTM relaunch re-sign) + hardcopy upcharge at cost | 🔴 | KS pricing row signed |
-| FR-3.3 | Lifetime-access tier decision (D-1) before KS copy freeze (W37). If approved: distinct SKU, price, renewals-off flag | 🟡 | Decision recorded; SKU spec |
-| FR-3.4 | Fulfillment ledger: backer ↔ key/upcharge tracked (CSV min; may reuse WeOwn Chat's ledger pattern — dogfooding, only if zero extra cost; CSV stays the floor) (R3) | 🟢 | Ledger template |
-
-### EPIC 4 — Contributor economy 🔴/🟡
-| ID | Requirement | Pri | Acceptance |
-|:--|:--|:--|:--|
-| FR-4.1 | Contribution intake (Recipe template + submit channel) | 🔴 | Public intake live at campaign |
-| FR-4.2 | Curation workflow w/ verification checklist (tool returns only — "REAL" is not proof, #203) | 🔴 | First 5 community Recipes processed w/ named curators |
-| FR-4.3 | Contributor credit + attribution (byline per Recipe; chapter credit; "Founding" page for VIP+) | 🔴 | Credit model published |
-| FR-4.4 | Affiliate onboarding (Kickbooster signup, links, leaderboard) | 🔴 | 15/10/10/5% live; weekly leaderboard to @CEO |
-| FR-4.5 | Royalty mechanics — **ONLY if @GTM signs D-2** | 🟡 blocked | Ledger spec + payout cadence; never assumed |
-| FR-4.6 | Claims-register hygiene: every income claim logged safe-to-say (§8) before any outreach | 🔴 | Register entries for lifetime/royalties/$47/affiliate/9/26 |
-| FR-4.7 | **Affiliate payout milestone**: payouts processed ≤ W-2 of campaign end (restored from ProductBuzz v0.1 FR-5.3 — R2) | 🟡 | Dated milestone in Ops calendar; maps to time-to-first-payout (Manual) |
-
-### EPIC 5 — Community & social education 🔴/🟡
-| ID | Requirement | Pri | Acceptance |
-|:--|:--|:--|:--|
-| FR-5.1 | Try-it feedback loop: readers post workflow results (bMAIT AiBook channel LIVE; Circle channels to create) | 🔴 | Loop documented + live |
-| FR-5.2 | **Book Circles**: 6-week cohort format; facilitator playbook; 1 pilot Circle within first campaign fortnight | 🟡 | Circle kit drafted; pilot = first 6 opt-in backers |
-| FR-5.3 | **Workflow-of-the-Week** showcase on aibook.fun + #FlowsBros/WeOwn.FM + email | 🟡 | Showcase cadence live W39+ |
-| FR-5.4 | **#FlowsBros standing series**: weekly live Recipe dissection | 🟡 | Episode format doc; 4 episodes across campaign |
-| FR-5.5 | Contributor onboarding doc (submit + affiliate signup) | 🔴 | Doc published |
-| FR-5.6 | Ownership markers: progress framed read → own → contribute → govern | 🟢 | Marker copy; identity tier tie-in |
-| FR-5.7 | Vertical learning paths (6 curated sets) | 🟢 | Structure published at launch |
-
-### EPIC 6 — Site & domain 🔴
-| ID | Requirement | Pri | Acceptance |
-|:--|:--|:--|:--|
-| FR-6.1 | aibook.fun production landing (Framer POC `217fbfc` → review → push by @GTM:ADMIN) | 🔴 | Hero, book, sample workflow, tiers, affiliate, CTA, FAQ |
-| FR-6.2 | SSL (existing cert fails — verified 08-21); keep GA continuity (UA-59154711-35) | 🔴 | HTTPS green 2 wks pre-launch |
-| FR-6.3 | **Auto-renew confirmation (exp 09-05) BEFORE any push — D-3, @GTM, W35** | 🔴 | Resolved W35; infra freeze 09-12 |
-| FR-6.4 | Sample-chapter delivery pre-launch (email-gated PDF via FluentCRM `book-prelaunch`) | 🔴 | Flow tested |
-
-### EPIC 7 — Email & CRM 🔴
-| ID | Requirement | Pri | Acceptance |
-|:--|:--|:--|:--|
-| FR-7.1 | FluentCRM tags: `book-prelaunch`, `book-backed`, `book-subscriber`, `affiliate` (@LDC, INT-P05) | 🔴 | Tags live |
-| FR-7.2 | 8-email sequence per SOT (3 pre, 1 launch, 2 mid, 2 final) — dates → 9/26 timeline; NFT-free scrubbed | 🔴 | Sequence staged |
-| FR-7.3 | Post-campaign sequence (funded, what's-next, fulfillment, renewal nudge) | 🟢 | Staged |
-
-### EPIC 8 — Ops, claims & metrics 🔴
-| ID | Requirement | Pri | Acceptance |
-|:--|:--|:--|:--|
-| FR-8.1 | Claims register: lifetime/royalties/$47-affiliate/9/26 entries + promotion rules (§8) | 🔴 | ProductBuzz opens; DRI sign-offs @GTM |
-| FR-8.2 | Metric events: `backer_signed`, `prelaunch_signup`, `affiliate_referral`, `sample_chapter_downloaded`, `workflow_submitted`, `workflow_published` — **instrument events, never content (§6.3)** | 🔴 | Events live |
-| FR-8.3 | Weekly metrics review ritual → campaign steering | 🔴 | Ritual scheduled |
-
-## 5. Non-functional requirements
-| ID | Requirement | Acceptance |
-|:--|:--|:--|
-| NFR-1 | **Truth in status:** zero DRAFT/OPEN/NOT-LIVE claims in external assets | Hard gate before publish |
-| NFR-2 | **KS compliance:** zero NFT/Web3/crypto terms on campaign surfaces | Translation table + scrub gate |
-| NFR-3 | **Privacy:** mailing-list per FluentCRM norms; no confidential client data in book/campaign (instrument events, never content) | Review |
-| NFR-4 | **Availability:** landing up through campaign; email on schedule; affiliate tracking live Day 1 (30-day cookie — every hour matters) | Monitoring |
-| NFR-5 | **Content quality:** every workflow passes Recipe template + ≥1 co-author review (anti-hallucination guarantee) | Editorial checklist |
-| NFR-6 | **Continuity:** aibook.fun must not lapse 09-05 (D-3); DNS/SSL before 09-12 (infra freeze) | D-3 resolved |
-| NFR-7 | **OKF conformance:** bundle validates per OKF v0.2 (frontmatter, `type`, `sources`, trust tiers) | Validation pass |
-| NFR-8 | **Trust posture:** ZDR claim stance ("documents stay on your instance" — never "ZDR is active"); 3-floor discipline per manual §5.3/§7.1 (F1 confidentiality · F2 cross-customer · F3 off-domain — DRI-ruled 08-22, all FLOOR 0); flyer rule + two-tab boundary UX | S5-Trust review |
-| NFR-9 | **Accessibility:** reader + landing mobile-readable, WCAG AA target | Design review (S2) |
-| NFR-10 | **Cost discipline:** launch burn ≤ SOT budget (~$6K pre-revenue); model spend tracked (W36 eval context) | Monthly review |
-
-## 6. Success metrics (SOT baseline + new Ops metrics)
-| Metric | Min | Target | Stretch | Owner |
-|:--|:--|:--|:--|:--|
-| Total raised | $5,000 | $35,000 | $54,000+ | @CEO dashboard |
-| Total backers | 300 | 700 | 1,000+ | @CEO |
-| Prelaunch email list | 500 | 1,000 | 2,000+ | @LDC |
-| Funded in days | 7 | 3 | 1 | team |
-| Ad ROAS | 3:1 | 5:1 | 10:1 | @CEO |
-| → AgencyPRO pipeline | 50 | 150 | 300+ | @CEO |
-| Affiliate % of total | — | ≥20% | 35% | @GTM |
-| **Backer→activation** (ch.1 + Try-it in 14d) | 20% | 35% | 50% | ProductBuzz (NEW) |
-| **Workflow submissions** (campaign window) | 10 | 25 | 50 | ProductBuzz (NEW) |
-| **Curation SLA ≤10 working days** | 80% | 95% | 100% | Curators (NEW) |
-| Renewal rate (year-1 cohort) | — | 60% | 75% | @GTM (NEW, post-campaign) |
-
-DRAFT targets — ratify at W35 metrics review before quoting anywhere.
-
-## 7. Dependencies & risk register
-### Top dependencies
-1. **D-1/D-2** (lifetime, royalties) → KS copy freeze (W37, 09-18). **Blocking.** @GTM R-011.
-2. **D-3** (domain auto-renew) → production push (W36). **Blocking.** @GTM registrar.
-3. @THY KS account + identity verification (SOT PL-1; W35).
-4. Co-author confirmations (D-6: Piper, Kerner).
-5. Sample chapters (FR-2.4): @THY + @CEO W36.
-6. Hero video (@LFG ~250h committed, SOT): script W35, shoot W36, edit W37.
-
-### Risks (SOT §Risk Matrix refreshed)
-| # | Risk | P | I | Mitigation | New? |
-|:--|:--|:--|:--|:--|:--|
-| 1 | < $5K minimum | Low | High | Conservative goal + prelaunch ≥500 | — |
-| 2 | Co-author manuscripts delayed | Med | High | Sample chapters pre-campaign; outline locked | — |
-| 3 | Low Day-1 momentum | Med | High | 500 emails + personal outreach + early bird | — |
-| 4 | KS rejection (NFT language) | Low | Crit | Translation table + scrub gate + final review | — |
-| 5 | **Domain lapse 09-05** | Med | Crit | D-3 confirm W35; 09-12 infra freeze | NEW |
-| 6 | **Commercial claims drift (lifetime/royalties)** | Med | High | Claims register + promotion rule | NEW |
-| 7 | **Unratified targets quoted externally** | Med | Med | Metrics labeled DRAFT until W35 sign | NEW |
-| 8 | Fulfillment delays | Med | Med | Print-on-demand; key issuance CSV | — |
-| 9 | Early-bird cannibalization of $47 tier | Med | Med | Cap 200; laddered tiers | NEW |
-| 10 | Post-campaign renewal work unstaffed | Med | High | Renewal owner assigned W35 (@GTM + @LDC) | NEW |
-| 11 | **Content pipeline thin (RAAI workflows need practitioners)** | Med | High | Community intake live at campaign; circles recruit; co-authors recruit | NEW |
-| 12 | Campaign-date confusion (SOT vintage vs 9/26) | Low | Med | All assets use 9/26; SOT note in every doc | NEW |
-
-## 8. Open questions (tracked in Spec §8, D-1..D-7)
-D-1 lifetime · D-2 royalties · D-3 domain auto-renew · D-4 SOT refresh → v3.3.0 · D-5 POC push · D-6 co-author confirmations · D-7 Product-Op Manual refs. **All are @GTM/@pat lanes; D-1/D-2/D-3 on the critical path to W37 copy freeze.**
-
-## 9. Approval & next step
-→ @pat: review Spec + PRD → @GTM: R-011 on D-1/D-2/D-3 (+ D-4 SOT refresh) — the only blockers to v1.0. Once signed: freeze v1.0, hand to implementation plan, open claims-register entries, brief KS copy writers.
+- **Who it's for:** busy professionals (real-estate, financial advisors, fractional
+  executives, higher-ed, community leaders, technologists) who want to apply an AI workflow
+  *this week*, not read AI theory.
+- **The ask:** fund the first edition on Kickstarter — **$5K minimum / $35K target**.
+- **The bet:** if the "run a workflow and share it" loop is genuinely useful, the same
+  people who read become the people who contribute — and the book stays alive.

 ---
-*CONSOLIDATED v1.0-DRAFT — single canonical version (v0.3 trunk + R2 + R3 + F1 + F2 + S2 + S3). Superseded drafts preserved at `PLANS/AIBOOK/` (v0.1 trio) pending @pat archive call. #LLMmodel: DeepSeek V4 Flash 0731.*
+
+## 1. The core loop and the one metric
+
+Everything in this product either serves this loop or waits its turn:
+
+```
+   READ a workflow  →  RUN the Try-it (~15 min)  →  SHARE the result
+        ▲                                                  │
+        └──────────  see others' results, come back  ──────┘
+```
+
+**North-Star metric — Activation:** *a backer reads at least one workflow and completes at
+least one Try-it within 14 days of getting access.*
+
+If activation is healthy, the product is alive and the rest (renewal, contribution,
+community) becomes possible. If activation is weak, no amount of funding, community
+scaffolding, or governance saves it. We report activation **first**, above the fundraising
+numbers, from the first day backers have access.
+
+---
+
+## 2. Background & problem
+
+**The problem:** Professionals are drowning in AI hype and have nowhere practical, trustworthy,
+and current to learn how to *actually use* AI agents in their real work — safely. Books go
+stale in months. Courses are generic. Twitter threads aren't accountable. And nobody's guide
+is written by, and kept current by, the practitioners doing the work.
+
+**Why us, why now:** WeOwnNet needs a shared, practical AI-literacy base for the people (and,
+later, the AI agents) it works with. A living book of *tested workflows* — contributed by
+practitioners, curated for quality — is that base. The Kickstarter both funds the first
+edition and assembles the founding community.
+
+**What makes it different (the claim we have to earn):** every workflow is *grounded in
+practice* — it shows the real steps and the real tool output, not a plausible-sounding
+description. "It works" is not a claim we make; it's something the reader can verify by
+running the Try-it themselves.
+
+---
+
+## 3. What the product is — and what it is *not yet*
+
+The prior draft treated five different products as one launch. They are not one product. Here
+is the honest layering:
+
+| Layer | What it is | When |
+|:--|:--|:--|
+| **Core (v1 — launch)** | A subscription book of tested AI workflows + the read→run→share loop | **9/26 launch** |
+| Layer 2 (post-launch) | Community contribution — readers submit their own workflows | After core loop proven |
+| Layer 3 (post-launch) | Cohort learning — "Book Circles," Workflow-of-the-Week showcase | After first content proves demand |
+| Layer 4 (later) | Agent onboarding — the same content, read by AI agents to onboard | Deliberate future use of the format |
+| Layer 5 (later) | Funnel into the wider WeOwnNet ecosystem (AgencyPRO) | Ongoing, low-effort |
+
+**This matters because** each layer has a different success metric and a different failure
+mode. Trying to build all five for 9/26 is how a small team ships none of them well. v1 is the
+**core loop, done excellently.** The other layers are designed-for but not built-for launch.
+
+### Explicit non-goals
+- Not a general-purpose AI chatbot or tool. It's a learning product.
+- Not regulated professional advice on the book's own authority.
+- No crypto / token / Web3 / NFT language on any public or Kickstarter-facing surface.
+  *(This is a hard Kickstarter-policy constraint — see [Appendix A](#appendix-a--kickstarter-compliance-the-nft-scrub).)*
+- Not building a separate "eBookNFT platform" — that's a future idea; this book is the first product.
+
+---
+
+## 4. Who it's for
+
+Personas are written as **jobs-to-be-done**. Note the buyer's job is *utility* ("help me do a
+thing this week"), which is how we should lead the pitch — ownership and community come later,
+as reasons to *stay*, not reasons to *buy*.
+
+| Persona | The job they're hiring us for | We've succeeded when… |
+|:--|:--|:--|
+| **Reader / subscriber** | "Apply one documented AI workflow in my real job this week." | They complete a Try-it within 14 days of getting access. |
+| **Contributor** *(Layer 2)* | "Publish a workflow I've proven, earn recognition (and, if we build it, income)." | Their first workflow is accepted within 90 days. |
+| **Curator / co-author** | "Keep the quality bar high; own a vertical." | Reviews turned around within ~10 working days. |
+| **Affiliate** | "Refer backers, earn commission." | First payout lands within one cycle of a referred pledge. |
+| **Ecosystem prospect** | "Learn responsible AI; maybe get more involved." | ≥40% of backers join the community *(draft target)*. |
+| **AI agent** *(Layer 4)* | "Onboard by reading the corpus." | *Designed-for, not a launch requirement — see §6.4.* |
+
+**Who it's *not* for:** people who want AI theory with no practice behind it; anyone seeking
+regulated professional advice from the book itself; teams wanting private hosted
+infrastructure (out of scope).
+
+---
+
+## 5. The content model — where the real risk is
+
+### 5.1 The unit of content: a Workflow Recipe
+Every entry follows one template. This template *is* the product's quality guarantee — it's
+the structural answer to "how do I know this AI advice isn't hallucinated?"
+
+| Field | What it captures |
+|:--|:--|
+| **Problem (the job)** | The real task or pain this solves |
+| **Actors** | Who runs it — a person, a role, or an AI agent |
+| **Method** | Ordered, reproducible steps — **showing the actual tool output**, not a description of it |
+| **Safeguards** | The responsible-AI guardrails: data handling, human oversight, failure modes, escalation |
+| **Evidence** | The documented result — artifacts or metrics |
+| **Try-it** | A ~15-minute exercise so the reader learns by doing |
+| **Costs** | Model/tool costs where known — honesty about the economics |
+| **Author & sources** | Who wrote it, when, for which vertical, with citations |
+
+**Chapters** are curated collections of these recipes, one set per vertical: Real Estate ·
+Financial Advisors · Fractional C-Suite · Higher Ed · Communities · Technology. **Editions**
+refresh annually — which is the honest justification for a *subscription* rather than a
+one-time purchase: the content genuinely goes stale as AI changes.
+
+### 5.2 The cold-start problem (this is the #1 product risk)
+The value proposition is "a rich living library." At launch, the prior plan has us with **2
+sample chapters and 3 runnable kits** — a pamphlet, not a library — and a hope that the crowd
+fills the rest. **Crowd-sourced libraries reliably die at cold-start.** We must not bet the
+launch on strangers showing up to write content for free.
+
+**Requirement — "Minimum Lovable Library":** before we ask anyone to pay, the founding
+co-authors and team produce a floor of **15–20 fully-tested workflows across at least 3
+verticals** *(recommended number — team to ratify)*. This is a **launch gate**, not a
+post-launch aspiration. Community contribution is **Layer 2** — an experiment we run *after*
+we've seeded a library worth subscribing to.
+
+### 5.3 Be honest: v1 is an *authored* book, not yet a *crowd* book
+The prior draft's "contributor economy" pays co-authors **15% affiliate commission** — which
+is a reward for *referring backers*, not for *writing workflows*. Writing a workflow currently
+earns a byline and nothing else. The mechanic that would actually pay contributors — royalties
+— is unresolved (see [D-2](#10-open-decisions)).
+
+So for v1, we state plainly: **the first edition is written by a founding set of co-authors and
+the team.** Open community contribution — with a real incentive attached — is the very next
+thing we build, and its incentive design ([D-2](#10-open-decisions)) is a **launch-blocking
+decision, not a nice-to-have**, because the entire "living book" thesis depends on it.
+
+---
+
+## 6. Requirements
+
+Priorities: 🔴 must-have for 9/26 · 🟡 should-have (launch window) · 🟢 post-launch.
+Requirements are grouped by the layer they serve; **most 🔴 items serve the core loop.**
+
+### 6.1 Campaign (Kickstarter) — 🔴
+| ID | Requirement | Pri |
+|:--|:--|:--|
+| C-1 | Kickstarter page: hero video (2–3 min), problem, the book, co-authors, 6 pledge tiers ($10→$4,888), stretch goals, FAQ (≥10), risks — **passes the NFT-language scrub** and Kickstarter category rules | 🔴 |
+| C-2 | Pre-launch landing page on aibook.fun with email capture + a 3-email warm-up sequence. **Target: 500+ emails before Day 1.** | 🔴 |
+| C-3 | Affiliate program live (Kickbooster): co-author 15% / community 10% / podcast 10% / press 5%; 30-day cookie, last-click | 🔴 |
+| C-4 | Launch playbook: Day-1 hour-by-hour schedule, weekly cadence, mid-campaign tactics, final-48h push | 🔴 |
+| C-5 | Campaign analytics dashboard: raised, backers, avg pledge, email list, cost-per-click, affiliate share — reviewed daily | 🔴 |
+| C-6 | Post-campaign comms staged before launch: final update, backer sequence, fulfillment announcement | 🟡 |
+
+### 6.2 Content (the core loop) — 🔴
+| ID | Requirement | Pri |
+|:--|:--|:--|
+| K-1 | Workflow Recipe template (§5.1), published, with **3 filled, reviewed examples** | 🔴 |
+| K-2 | **Minimum Lovable Library: 15–20 tested workflows, ≥3 verticals** (§5.2) — team/co-author authored | 🔴 |
+| K-3 | Chapter outline per vertical, with a named owner for each | 🔴 |
+| K-4 | 2 sample chapters delivered pre-launch as the backer preview | 🔴 |
+| K-5 | 3 "clone-and-run" kits, each **verified by actually running it** | 🔴 |
+| K-6 | Editorial pipeline: submit → co-author review → accept/revise → publish → track updates | 🔴 |
+| K-7 | Content stored in a structured, versioned, machine-readable format (frontmatter + provenance + trust tiers) so editions are diffable and, later, agent-readable | 🟡 |
+
+### 6.3 Access & subscription — 🔴 / 🟢
+| ID | Requirement | Pri |
+|:--|:--|:--|
+| A-1 | Post-campaign access: a digital key unlocks PDF + web reader for 12 months, renews annually | 🟢 |
+| A-2 | Anchor price **$47/yr** *(draft — needs commercial re-sign)* + hardcopy at-cost upcharge | 🔴 |
+| A-3 | Lifetime tier — **decision required before copy freeze** (see [D-1](#10-open-decisions)) | 🟡 |
+| A-4 | Fulfillment ledger: backer ↔ key/upcharge tracked (a spreadsheet is fine for v1) | 🟢 |
+
+### 6.4 The other layers — mostly 🟡 / 🟢
+| ID | Requirement | Pri |
+|:--|:--|:--|
+| L-1 | *(Layer 3)* Try-it feedback loop: readers post results in the community channel (pinned template) | 🔴 |
+| L-2 | *(Layer 3)* "Book Circles" — 6-week cohort format + facilitator playbook; **1 pilot cohort** post-launch | 🟡 |
+| L-3 | *(Layer 3)* Workflow-of-the-Week showcase (site + community + email) | 🟡 |
+| L-4 | *(Layer 2)* Public contribution intake + curation checklist — opens **after** the Minimum Lovable Library exists | 🟡 |
+| L-5 | *(Layer 4)* Agent-onboarding: the same content, structured for machine ingestion — **a property of the K-7 format, not a separate build for launch** (see decision in [D-5](#10-open-decisions)) | 🟢 |
+| L-6 | *(Layer 5)* Ecosystem funnel: backers flow into the wider WeOwnNet programs | 🟢 |
+
+### 6.5 Site, email, ops — 🔴
+| ID | Requirement | Pri |
+|:--|:--|:--|
+| S-1 | aibook.fun production landing (hero, the book, a sample workflow, tiers, affiliate, CTA, FAQ) | 🔴 |
+| S-2 | Working HTTPS (current cert fails — verified 08-21); keep existing analytics continuity | 🔴 |
+| S-3 | Email/CRM tags for the funnel: `prelaunch`, `backed`, `subscriber`, `affiliate` | 🔴 |
+| S-4 | 8-email campaign sequence (3 pre-launch, 1 launch, 2 mid, 2 final), dates aligned to 9/26, NFT-scrubbed | 🔴 |
+| S-5 | Instrument **events, not content** — track that a workflow was downloaded/submitted, never the confidential content itself (see [Appendix B](#appendix-b--trust--privacy-posture)) | 🔴 |
+
+---
+
+## 7. Non-functional requirements
+
+| ID | Requirement |
+|:--|:--|
+| NFR-1 | **Truth in status:** no draft/unconfirmed figure appears in any external asset. Hard gate before publish. |
+| NFR-2 | **Kickstarter compliance:** zero crypto/Web3/NFT terms on any campaign surface ([Appendix A](#appendix-a--kickstarter-compliance-the-nft-scrub)). |
+| NFR-3 | **Privacy:** no confidential client data in any workflow or campaign asset; track events, not content. |
+| NFR-4 | **Availability:** landing page up through the campaign; emails on schedule; affiliate tracking live from Day 1 (the 30-day cookie means every hour of Day 1 counts). |
+| NFR-5 | **Content quality:** every workflow passes the Recipe template + at least one co-author review. |
+| NFR-6 | **Domain continuity:** aibook.fun must not lapse (it currently expires 09-05 — see [§9](#9-immediate-next-steps)). |
+| NFR-7 | **Accessibility:** reader and landing page are mobile-readable, targeting WCAG AA. |
+| NFR-8 | **Cost discipline:** pre-revenue burn stays within the ~$6K budget ([Appendix C](#appendix-c--budget)). |
+
+---
+
+## 8. Success metrics
+
+**Product health first, fundraising second.** The prior draft led with fundraising vanity
+metrics; those measure the *campaign*, not the *product.* A funded campaign can still hide a
+dead product if nobody activates, renews, or contributes.
+
+### Product health (report these first)
+| Metric | Floor | Target | Why it matters |
+|:--|:--|:--|:--|
+| **Activation** — read 1 workflow + do 1 Try-it in 14 days | 20% | 35% | The North-Star. Is the core loop actually useful? |
+| **Workflow submissions** during campaign window | 10 | 25 | Early signal that Layer 2 (contribution) is real |
+| **Renewal rate** — year-1 cohort | — | 60% | Is a *subscription* the right model at all? |
+| **Curation turnaround** ≤ 10 working days | 80% | 95% | Can we keep quality without becoming the bottleneck? |
+
+### Campaign performance (the fundraise)
+| Metric | Min | Target | Stretch |
+|:--|:--|:--|:--|
+| Total raised | $5,000 | $35,000 | $54,000+ |
+| Total backers | 300 | 700 | 1,000+ |
+| Pre-launch email list | 500 | 1,000 | 2,000+ |
+| Days to fund | 7 | 3 | 1 |
+| Ad return on spend | 3:1 | 5:1 | 10:1 |
+| Affiliate share of total | — | ≥20% | 35% |
+| Backers → ecosystem pipeline | 50 | 150 | 300+ |
+
+> ⚠️ **Two bars, not one.** Hitting the **$5K funding floor** (~106 backers) proves people will
+> *pre-order*. It does **not** prove they'll *renew* or *contribute* — the two things this
+> business actually depends on. Treat the **product-health floors above as a separate,
+> equally-weighted validation bar.** "Funded" is not "validated."
+
+*All draft targets must be ratified before being quoted anywhere.*
+
+---
+
+## 9. Immediate next steps
+
+**This week — decisions and de-risking (before any copy or build locks):**
+1. **Renew aibook.fun today.** It expires 09-05; launch is 09-26. This is a chore, not a
+   strategic decision — do it now and delete it from the risk list. *(Owner: whoever holds the
+   registrar login.)*
+2. **Resolve the pricing spine together — lifetime ([D-1](#10-open-decisions)) *and* royalties
+   ([D-2](#10-open-decisions)).** They're linked, and both block copy freeze.
+3. **Ratify the North-Star + the product-health floors** (§8) so we're measuring the right
+   thing from Day 1.
+4. **Ratify the Minimum Lovable Library number and assign every workflow an author** (§5.2).
+5. **Confirm the two unconfirmed co-authors** (Higher Ed, Communities) or re-scope those
+   verticals out of v1.
+
+**Build phase (weeks to launch):**
+6. Landing page ships as a **hook A/B test** ("run this AI workflow today" vs. "own a
+   community-built AI guide") — we should *learn which message converts* before we spend ad
+   budget, not just capture emails.
+7. Author the Minimum Lovable Library to its floor number.
+8. Standard campaign build — hero video, email sequence, Kickstarter page — **after** 1–5.
+9. Keep two governance gates sharp and drop the ceremony from the rest ([Appendix B](#appendix-b--trust--privacy-posture)):
+   the **NFT-language scrub** (existential — Kickstarter will reject us otherwise) and
+   **truth-in-claims** (no draft figures go public).
+
+**Launch → fulfillment:** run the campaign, then fulfill (manuscript → edit → layout → proof →
+issue access keys → print/ship hardcopies), then turn on the renewal system and open Layer 2
+contribution. Detailed timeline lives in the Implementation Plan.
+
+---
+
+## 10. Open decisions
+
+These are the *genuinely open* strategic decisions. Each carries a **recommendation** so the
+decision-maker has a starting point — but the recommendation is not yet a decision.
+
+| # | Decision | Recommendation | Blocks |
+|:--|:--|:--|:--|
+| **D-1** | **Lifetime tier — offer it, and at what price?** A ~$97–147 lifetime breaks even against $47/yr in ~2–3 years, which *undercuts the recurring-revenue thesis.* | **Pick a spine.** Keep $47/yr as the anchor. If you want a lifetime option, frame it *only* as a bounded early-bird instrument to capitalize the community fund (capped quantity), not the default SKU. Don't ship recurring + lifetime as equals. | KS copy freeze |
+| **D-2** | **Contributor payment — how do people earn for *writing workflows* (not just referring)?** Today the only paid mechanic is affiliate referral. | **Resolve before launch.** This is the engine of the "living book." Decide: royalty pool, per-accepted-workflow bounty, or an explicit "v1 is authored, paid contribution ships in Q1" — but decide, don't leave blank. | The core value prop |
+| **D-3** | **Co-author confirmations** (Higher Ed, Communities verticals). | Confirm within the week or cut those verticals from v1 and add post-launch. | Chapter outline, scope |
+| **D-4** | **Refresh the source-of-truth plan** to the 9/26 dates and re-signed terms (depends on D-1/D-2). | Do after D-1/D-2 land. | Copy freeze |
+| **D-5** | **Human-first or agent-first for v1?** Writing for human motivation and for machine ingestion are different jobs. | **Human-first.** Build the content format so agents *can* read it later (K-7), but optimize v1 for human learners. Agent onboarding is Layer 4. | Content design |
+| **D-6** | **Does "you own a stake" survive the NFT-scrub as a *true* claim?** If the ownership model was fundamentally token mechanics, stripping them for Kickstarter may leave "ownership" as marketing over an ordinary subscription. | **Audit the claim.** Either define what ownership concretely means without tokens (governance rights? revenue share? credited authorship?) or stop using the word publicly. Add it to the claims register. | Public messaging integrity |
+
+> *Resolved and removed from this list:* the domain "decision" — it's a chore (renew it, §9),
+> not a strategic gate.
+
+---
+
+## Appendix A — Kickstarter compliance (the NFT scrub)
+
+Kickstarter bans NFT/crypto/Web3 language. Any internal terms rooted in that model must be
+translated on every public surface **before** submission, e.g. an internal "subscription NFT"
+becomes, publicly, an **"annual digital subscription."** A single scrub gate reviews *every*
+asset (page, emails, landing, video captions) against a translation table before anything
+ships. **This is the single most existential compliance requirement** — a rejection here kills
+the launch date.
+
+## Appendix B — Trust & privacy posture
+
+Kept deliberately lightweight for this stage; two rules are load-bearing, the rest is
+proportionate:
+- **Confidential material never appears in public content.** Workflows are illustrative and
+  use non-confidential examples.
+- **Instrument events, not content.** We record *that* a workflow was downloaded or submitted —
+  never the private content of what a user did.
+- **Honest data-handling language.** Describe what's actually true ("your documents stay on
+  your instance"); never claim a security property we haven't verified is switched on.
+- Heavier governance ceremony (formal sign-off registers, isolation-floor audits, corpus
+  conformance) scales up *with the product* — it doesn't precede a pre-revenue, unvalidated
+  launch.
+
+## Appendix C — Budget
+
+Pre-revenue, ~$6K, matching the source plan:
+
+| Item | Cost |
+|:--|:--|
+| LinkedIn ads (campaign wks 2–4) | $1,300 |
+| Meta ads | $700 |
+| Google ads | $280 |
+| Cover / video edit | $0–500 |
+| Kickstarter fees (~8% on $35K) | ~$2,800 |
+| Kickbooster (10% on referred pledges) | ~$700 |
+| Domain renewal | ~$15–20 |
+| **Pre-revenue total** | **~$6,000** |
+| Projected revenue | $35,000–$54,000 |
+
+## Appendix D — What changed in this revision
+
+This revision is a **plain-language rewrite with a product review folded in.** Substantive
+changes from the prior draft, and the reasoning:
+
+1. **Named one core loop + one North-Star** (read→run→share; activation). The prior draft
+   marked ~half of 40 requirements "must-have" — no real prioritization.
+2. **Layered the product** (§3) so v1 = the core loop; contribution, cohorts, agents, and the
+   funnel are explicitly later layers.
+3. **Elevated the content cold-start** to the #1 risk and added the *Minimum Lovable Library*
+   launch gate (§5.2).
+4. **Told the truth about incentives** (§5.3): v1 is an authored book; the "contributor
+   economy" is currently a referral scheme; paid contribution (D-2) is now launch-blocking.
+5. **Forced the subscription-vs-lifetime tension** into a real decision (D-1).
+6. **Split the validation bar from the funding floor** (§8) so a funded-but-dead outcome can't
+   hide.
+7. **Reframed the pitch as utility-first** (§4, §9 hook test) — the buyer wants a workflow, not
+   an ownership philosophy.
+8. **Demoted governance to proportionate** (Appendix B), keeping only the NFT-scrub and
+   truth-in-claims as active gates.
+9. **Turned the domain "decision" into a same-day chore** (§9).
+10. **Translated the jargon out.** Internal codes, handles, and merge-history are gone from the
+    body; a who's-who / glossary can be maintained separately if the team wants traceability
+    back to the source-of-truth IDs.
+
+*(A field-by-field mapping from the old FR-x IDs to these can be produced on request.)*