Files
aibook-fun/AiBook_PRD.md
T
2026-08-23 10:11:41 +00:00

17 KiB
Raw Blame History

title, type, tags, status, created, source-of-truth, generated, verified, sources
title type tags status created source-of-truth generated verified sources
AIBook.fun — Product Requirements Document (CONSOLIDATED v1.0-DRAFT) prd
aibook
weown-ai
prj-031
prd
kickstarter
responsible-agentic-ai
social-education
okf
requirements
draft 2026-08-22 https://github.com/CCCbotNet/fedarch/blob/main/_PROJECTS_/PRJ-031_WeOwnAI-Book.md
by at
AI:CCC-MAIT-S004-PAT-DeepSeek (SEAT-1 governance/OKF) + ProductBuzz [PAT] (Product Ops) — merged v0.2, amended v0.3 2026-08-22T15:36:00Z
by at
curl github.com/CCCbotNet/fedarch (PRJ-031 SOT v3.2.1.3) 2026-08-22
by at
buzz channels list (relay) — bMAIT AiBook.fun channel desc 2026-08-22
id resource note
sot https://github.com/CCCbotNet/fedarch/blob/main/_PROJECTS_/PRJ-031_WeOwnAI-Book.md PRJ-031 v3.2.1.3 — tiers, goals, affiliate %, team, timing
id resource note
spec PLANS/AIBOOK_SPEC.md Companion spec (merged v0.3) — pillars, scope, open decisions D-1..D-7
id resource note
pb-prd PLANS/AIBOOK/AIBOOK_PRD.md (ProductBuzz draft v0.1) Parallel draft merged into this canonical — goals, personas, FR-1..FR-8, metrics, risks
id resource note
pat-manual AGENTS.md (PAT squad) + Product-Op Manual refs 4 actors (§3-4) · 3 floors · flyer rule · two-tab UX · ZDR stance · §8 claims register · §6.3 isolation · launch gates

📚 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.


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.

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.

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.

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.


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.