WeOwnAi/aibook-fun
5
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Merged
pat merged 1 commits from docs/plain-language-rewrite into main 2026-08-26 13:56:33 +00:00
Conversation 0 Commits 1 Files Changed 3
+828 -503
3 changed files with 828 additions and 503 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AiBook_Implementation_Plan.md
+186 -160
View File
@@ -1,197 +1,223 @@
--- ---
title: "AIBook.fun — Implementation Plan (CONSOLIDATED v1.0-DRAFT)" title: "AIBook.fun — Implementation Plan"
type: implementation-plan type: implementation-plan
tags: [aibook, weown-ai, prj-031, implementation, kickstarter, roadmap, responsible-agentic-ai, social-education]
status: draft status: draft
created: 2026-08-22 owner: Patrick (Product)
source-of-truth: "https://github.com/CCCbotNet/fedarch/blob/main/_PROJECTS_/PRJ-031_WeOwnAI-Book.md" launch-target: 2026-09-26
generated: last-updated: 2026-08-26
by: "AI:CCC-MAIT-S004-PAT-DeepSeek (SEAT-1 governance/OKF) + ProductBuzz [PAT] (Product Ops) — merged v0.2, amended v0.3" companions: [AiBook_PRD.md, AiBook_Spec.md]
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 — pre-launch/launch/post phases, budget, risks, team"
- id: spec
resource: "PLANS/AIBOOK_SPEC.md"
- id: prd
resource: "PLANS/AIBOOK_PRD.md"
- id: pb-impl
resource: "PLANS/AIBOOK/AIBOOK_IMPLEMENTATION_PLAN.md (ProductBuzz draft v0.1)"
note: "Parallel draft merged into this canonical — 5-phase skeleton, gates, RACI"
--- ---
# 📚 AIBook.fun — Implementation Plan # 📚 AIBook.fun — Implementation Plan
**CONSOLIDATED v1.0-DRAFT** · 2026-08-22 · **ProductBuzz [PAT]** (Product Ops) + **CCC-MAIT-S004-PAT-DeepSeek** (SEAT-1 governance/OKF) · Owner: @pat · R-011 gates: @GTM · **⛔ 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 F1 (gates G0–G3 kept; G4 dropped everywhere — the "G0–G4" lived only in the channel summary, not the file) · S4 (Phase 0.8 reworded: D-7 as @pat override review of DRI floor ruling). v0.3 amendment history below:
> v0.3 amendment (2026-08-22T13:36Z, Product Ops review): frontmatter timestamp corrected (v0.2 was future-dated) · floor references aligned to DRI ruling (see SPEC §P6).
**Anchors:** Today = 2026-08-22 (W34·D6) · **Kickstarter launch = 9/26/2026** (CONFIRMED, W39·D6) · Domain expiry **09-05** (auto-renew must confirm W35) · SOT campaign skeleton reused with refreshed dates. > **Status: DRAFT.** The schedule below assumes decisions that aren't final yet (see "Do this
> week"). Dates, owners, and dollar figures are planning assumptions until signed off. This is a
> **living document** — update it weekly with actual dates and owners. See
> [Appendix — What changed](#appendix--what-changed-in-this-revision) for how this revision
> differs from the prior draft.
**Critical path:** G0 decisions → copy freeze → scrub gate → KS submit → **9/26** — ~34 days; every week counts. **The clock:** today is late August 2026; **launch is 9/26/2026** — roughly **4–5 weeks out**.
Every week counts, and the critical path has little slack. The domain expires **09-05**, so
step one is non-negotiable and immediate.
**The critical path in one line:**
`renew domain + make the pricing decisions → seed the Minimum Lovable Library → freeze copy → no-crypto scrub → submit to Kickstarter → launch 9/26`
--- ---
## Phase 0 — Decisions & hard gates (W34 now → W35, by 2026-09-01) ## Do this week (the real gate zero)
| # | Task | Owner | Due | Gate | Before any copy or build locks, close these. Most are decisions or de-risking, not building.
|:--|:--|:--|:--|:--|
| 0.1 | **D-3: confirm aibook.fun auto-renew** (or renew manually now) | @GTM | **W35 (09-01)** | G0 🔴 |
| 0.2 | **D-1: lifetime tier decision** (yes/no, price, position vs $47/yr) | @GTM (R-011) | W35 | G0 🔴 |
| 0.3 | **D-2: royalty mechanics** (affiliate-only per SOT, or add royalty pool) | @GTM (R-011) | W35 | G0 🔴 |
| 0.4 | Ratify metric targets (PRD §6) — never quote DRAFT figures | ProductBuzz + team | W35 | G0 |
| 0.5 | Open claims-register entries (Spec §7) with promotion rules | ProductBuzz | W35 | G0 |
| 0.6 | Assign renewal owner (post-campaign) | @GTM | W35 | G0 |
| 0.7 | KS creator account + identity verification | @THY | W35 | G0 (SOT PL-1) |
| 0.8 | D-7: @pat override review of DRI floor ruling (F1 confidentiality · F2 cross-customer · F3 off-domain, all FLOOR 0) — closes override window (S4) | @pat | W35 | G0 |
| 0.9 | Workflow Recipe schema v0.1 + 3 example Recipes | SEAT-2 Laguna + PAT satellites | W35 | G0 |
**Gate G0 (09-01):** D-1/D-2/D-3 answered; targets ratified; claims entries open. Without D-3, downstream builds on a domain that may lapse — **pause production push, not content work.** | # | Task | Owner | Why it's first |
|:--|:--|:--|:--|
| 0.1 | **Renew aibook.fun today.** It expires 09-05; launch is 09-26. | Whoever holds the registrar login | It's a chore, not a decision. A lapsed domain 3 weeks before launch is a self-inflicted disaster. |
| 0.2 | **Decide the pricing spine — lifetime *and* royalties together** (D-1 + D-2). | Commercial lead (@GTM) | Both block copy freeze; they're linked (see [Spec §6](AiBook_Spec.md)). |
| 0.3 | **Ratify the North-Star + product-health floors** (activation, submissions, renewal). | Product (@pat) + team | So we measure the right thing from Day 1, not just dollars. |
| 0.4 | **Ratify the Minimum Lovable Library number and assign every workflow an author.** | Product + co-authors | This is the #1 risk; turn it from hope into owned work. |
| 0.5 | **Confirm the two unconfirmed co-authors, or cut their verticals from v1** (D-3). | Commercial lead (@GTM) | Scope certainty before outline lock. |
| 0.6 | Open the claims register; assign a post-campaign renewal owner. | Product + Commercial | Truth-in-claims gate; don't leave renewal unstaffed. |
| 0.7 | Set up the Kickstarter creator account + identity verification. | Campaign lead (@THY) | Long lead time; do it early. |
**✅ Gate 0 — decisions closed.** Pricing spine decided · targets ratified · Minimum Lovable
Library scoped with authors · domain renewed · claims register open. *Until pricing is decided,
don't freeze copy. Until the domain is renewed, don't push anything live.*
--- ---
## Phase 1 — Build (W35–W37, 09-01 → 09-19) ## Phase 1 — Build (the ~3 weeks before launch)
### 1A · Content (critical path: sample chapters + workflow template) Organized by the four workstreams. **The content workstream is the critical path** — a beautiful
| Task | Owner | Due | campaign around an empty library fails.
|:--|:--|:--|
| Book outline locked (chapters per vertical, SOT §Co-Authors) | @THY + @CEO + @GTM | W35 | ### 1A · Content — seed the Minimum Lovable Library (critical path)
| Workflow document template v1 (Spec §4.1) published to contributors | ProductBuzz | W35 | | Task | Owner |
| **3 learn-by-running kits** (clone-and-run; verified by running) | SEAT-2 Laguna + PAT-QA S4 | W36 | |:--|:--|
| **Sample chapter 1** (flagship vertical) | @THY | W36 | | Lock the chapter outline (chapters per vertical, a named owner each) | Co-authors |
| **Sample chapter 2** | @CEO | W36 | | Publish the Workflow Recipe template + 3 filled examples | Product |
| Contributor onboarding doc + affiliate signup path | ProductBuzz + @GTM | W36 | | **Seed the Minimum Lovable Library to its floor number** (team + co-authors write & test the workflows) | Co-authors + team |
| Workflow-of-the-Week #1 (showcase starter) | Curators | W37 | | 3 "clone-and-run" kits, each **verified by actually running it** | Dev + QA support |
| Co-author outreach: B.W. Piper (Higher Ed), L. Kerner (Communities) | @GTM | W36 (D-6) | | 2 sample chapters (the backer preview) | Two lead co-authors |
| OKF bundle scaffolding (Book as knowledge bundle, frontmatter/sources/trust tiers) | SEAT-1 DeepSeek | W37 | | Contributor onboarding doc + affiliate signup path | Product + Commercial |
| Structured/versioned content format (so editions diff cleanly, and agents can read it later) | Format support |
### 1B · Site & domain ### 1B · Site & domain
| Task | Owner | Due | | Task | Owner |
|:--|:--|:--| |:--|:--|
| Framer POC review (`217fbfc` staged) → feedback | @pat + @GTM | W35 | | Review the staged landing-page proof-of-concept → feedback | Product + Commercial |
| **Push to production** (only after G0); SSL cert; GA continuity (UA-59154711-35) | @GTM:ADMIN | W36 | | Push landing to production (**only after Gate 0**) — working HTTPS, analytics continuity | Site admin (@GTM) |
| aibook.fun/affiliates page + Kickbooster widget | @GTM | W36 | | Landing page runs as a **hook A/B test** ("run a workflow today" vs. "own a community guide") — learn which message converts before spending ad budget | Site admin + Product |
| Sample-chapter download flow (email-gated via FluentCRM `book-prelaunch`) | @LDC + @GTM | W37 | | Affiliates page + Kickbooster widget | Commercial |
| **09-12 infra freeze** (DNS/SSL/registrar untouched after) | all | 09-12 ⚠️ | | Email-gated sample-chapter download flow | Email lead (@LDC) + Site admin |
| **09-12 infra freeze** — DNS/SSL/registrar untouched after this date | All |
### 1C · Campaign assets ### 1C · Campaign assets
| Task | Owner | Due | | Task | Owner |
|:--|:--|
| Kickstarter page copy (all sections, 9/26 dates) | Campaign lead + exec co-author |
| **Copy freeze — commercial terms locked** (lifetime/royalties per D-1/D-2) | Commercial lead (sign) |
| **No-crypto scrub gate on every asset** (translation table) | Campaign lead (owner) |
| Hero video: script → shoot → edit (2–3 min) | Creative lead (@LFG) + co-authors |
| Cover design + 3D mockups | Creative lead |
| Pre-launch email sequence (3 emails) built + tagged | Exec co-author + Email lead |
| LinkedIn organic pre-launch calendar | Creative lead |
### 1D · Community & the learning loop
| Task | Owner |
|:--|:--|
| Try-it feedback loop live in the community channel (pinned template) | Product |
| Book Circles playbook (1 page) + pilot cohort announced | Product + community |
| Affiliate program live: Kickbooster account, rates set, co-authors invited | Commercial |
| Workflow-of-the-Week showcase format + first few episodes planned | Product + WeOwn.FM |
**✅ Gate 1 — ready to rehearse.** Minimum Lovable Library seeded to its floor · site live with
working HTTPS · Kickstarter copy frozen · no-crypto scrub passed · pre-launch list on track to
500 · claims register current.
---
## Phase 2 — Launch rehearsal (the final week)
| Task | Owner |
|:--|:--|
| Full dry run: page live, access-key flow tested, all tracking + affiliate links, test email send | Exec co-author + Commercial |
| Day-1 playbook refreshed (hour-by-hour, 6am→9pm) | Exec co-author |
| Risk sweep: re-read the risk register against current reality | Product |
| Final pre-launch list push (target 500) | All |
| Final claims pass — no draft/open figure on any surface | Product |
**✅ Gate 2 — all green → LAUNCH 9/26/2026.**
---
## Phase 3 — Campaign (~33 days)
The standard Kickstarter arc:
- **Day 1 (09-26):** live at 6am · launch email · all-team social · hourly backer monitoring ·
Day-1 goal ~30% funded + 100 backers.
- **Week 1:** reply to every comment within ~2h · early-bird urgency (cap 200) · "FUNDED in X
days" moment at $5K.
- **Week 2 (ads on):** LinkedIn A/B (3 creatives) → scale the winner · Meta retargeting · mid
emails.
- **Week 3 (mid-push):** anti-dead-zone tactics — signed/personalized tier, stretch-goal
announcements, guest posts, press, a live Workflow-of-the-Week episode.
- **Final 48h:** 24h / 3h / final-call emails.
- **Weekly ritual:** metrics vs. targets + a claims check; feed learnings into steering.
**✅ Gate 3 — campaign close.** ≥$5K minimum (mandatory) · report vs. $35K/$54K · affiliate share
vs. 20% target · begin the handoff of backers into the ecosystem funnel. *(Remember: hitting the
$5K floor proves people will pre-order — it does not prove renewal or contribution. Read the
product-health numbers with equal weight.)*
---
## Phase 4 — Fulfillment & the living book (post-campaign → 2027)
| # | Milestone | Target |
|:--|:--|:--| |:--|:--|:--|
| KS page copy (SOT PL-3 sections) with refreshed dates | @THY + @CEO | W36 | | 4.1 | Campaign final update + backer emails (funded / what's next) | +48h |
| **Copy freeze — commercial terms** (lifetime/royalties locked, D-1/D-2) | @GTM sign | **W37 (09-18)** | | 4.2 | Manuscript complete (all verticals) | ~Day 60 |
| NFT-free scrub gate on ALL assets (translation table) | @THY (owner) | W37 | | 4.3 | Professional editing | ~Day 75 |
| Hero video script → shoot → edit (2–3 min) | @LFG + co-authors | W37 | | 4.4 | Layout + design | ~Day 85 |
| Cover design + 3D mockups (SOT PL-2) | @LFG | W37 | | 4.5 | Final proof | ~Day 90 |
| Prelaunch email sequence (3) built + tagged | @CEO + @LDC | W37 | | 4.6 | Print run (hardcopy upcharge) | ~Day 95 |
| LinkedIn organic prelaunch calendar (SOT W14–W15 pattern) | @LFG | W37 | | 4.7 | Digital access keys issued (ledger + email; content format finalized) | ~Day 100 |
| 4.8 | Signed hardcopies shipped | ~Day 110 |
| 4.9 | All rewards fulfilled | ~Day 120 |
| 4.10 | **Subscription renewal system live** (year-2 $47/yr; lifetime honored per D-1) | Day 120+ |
| 4.11 | **Open contribution live** — with a real incentive (per D-2), *now* that the library exists | Day 120+ |
| 4.12 | Book Circles scale (pilot → several vertical cohorts); showcase becomes a regular series | 2027 Q1 |
| 4.13 | **Annual edition v1.1** (changelog; the "stays current" promise honored) | 2027 Q1 |
| 4.14 | Year-1 renewal cohort tracked against the 60% target | 2027 Q4 |
| 4.15 | Decide whether to build the standalone platform; funnel operational | 2027 Q2 |
### 1D · Community & education loop > Note: the source plan's "NFT minting" step becomes, publicly, **"digital access key
| Task | Owner | Due | > issuance."** Same fulfillment, no-crypto framing.
|:--|:--|:--|
| Book Circles playbook (1 page) + pilot cohort announced | ProductBuzz + bMAIT | W37 |
| Try-it feedback loop live in bMAIT AiBook channel (pinned template) | ProductBuzz | W37 |
| Affiliate program live: Kickbooster account, rates 15/10/10/5, invite co-authors | @GTM | W36 (SOT impl plan) |
| #FlowsBros episode format + 4-episode campaign slate (W39-W42) | ProductBuzz + WeOwn.FM | W37 |
| Two-tab (green/red) boundary UX spec for post-campaign member lane | PAT-Design S2 + PAT-Trust S5 | W38 (build = Ph4) |
**Gate G1 (09-19):** site production + SSL green · KS copy frozen · scrub gate passed · prelaunch list ≥ 300 (track → 500 by 09-25) · claims register current.
--- ---
## Phase 2 — Launch rehearsal (W37→W38, 09-19 → 09-25) ## Budget (planning baseline — reforecast at Gate 1)
| Task | Owner | Due |
|:--|:--|:--|
| Full dry run: page live, keys workflow test, UTM links, affiliate links, email send test | @CEO + @GTM | 09-23 |
| Day-1 playbook (SOT W16 table, times 6:00→21:00) refreshed | @CEO | 09-23 |
| Risk sweep: re-read SOT risk matrix + PRD §7 against current state | ProductBuzz | 09-24 |
| Prelaunch list final push (target 500) | ALL | 09-25 |
| Final claims pass: no DRAFT/OPEN figure on any surface | ProductBuzz + SEAT-1 | 09-25 |
**Gate G2 (09-25):** all checks green → **LAUNCH 9/26/2026**.
---
## Phase 3 — Campaign (9/26 → ~10/29, 33 days)
Reuse SOT W16–W20 skeleton with refreshed dates:
- **Day 1 (09-26):** KS live 6:00 AM · launch email · LinkedIn by all team · Signal · X · texts · hourly backer monitoring · Day-1 goal 30% + 100 backers (SOT).
- **Week 1:** reply-to-every-comment SLA (2h) · early bird urgency (200 cap) · "FUNDED in X days" at $5K.
- **Week 2 (ads on):** LinkedIn A/B (3 creatives, SOT B-01/B-02/B-03) → scale winner · Meta retargeting · mid emails.
- **Week 3 (mid push):** dead-zone tactics (SOT 7-item list): signed+personalized tier $68, stretch-goal announcements, guest posts, press outreach, **#FlowsBros episode** on WeOwn.FM.
- **Final 48h:** 24h/3h/final-emails per SOT W19–W20.
- **Weekly ritual (Ops):** metrics vs PRD §6 + claims check; feed learnings into steering; **hive-mind sync-back to 🎉💰📚🫶︱CCC︱MAITs** weekly (SEAT-1).
**Gate G3 (campaign close):** ≥$5K min (mandatory), report vs $35K/$54K; affiliate share ≥20% target; backers → AgencyPRO pipeline handoff begins.
---
## Phase 4 — Fulfillment & the living book (post-campaign, ~10/29 → 2027)
| # | Milestone | Target | Owner |
|:--|:--|:--|:--|
| 4.1 | Campaign final update + backer emails (funded/what's-next) | +48h | @CEO |
| 4.2 | Manuscript complete (all verticals) | Day 60 | @THY + @CEO + contributors |
| 4.3 | Professional editing | Day 75 | contractor |
| 4.4 | Layout + design | Day 85 | @LFG |
| 4.5 | Final proof | Day 90 | @THY |
| 4.6 | Digital access keys issued (ledger CSV + email; OKF bundle final) | Day 100 | @GTM + SEAT-2 |
| 4.7 | Print run (hardcopy upcharge) | Day 95 | @GTM |
| 4.8 | Signed hardcopies shipped | Day 110 | @THY |
| 4.9 | All rewards fulfilled | Day 120 | ALL |
| 4.10 | **Subscription renewal system live** ($47/yr year-2, lifetime tier honored per D-1) | Day 120+ | @GTM + @LDC |
| 4.11 | Workflow library open for submissions (affiliate income; royalty pool only if D-2 signed) | Day 120+ | Curators |
| 4.12 | Book Circles scale: pilot → 6 vertical cohorts; #FlowsBros regular season | 2027 Q1 | ProductBuzz + bMAIT |
| 4.13 | **Annual edition v1.1** (changelog; "updated as AI evolves" promise honored) | 2027 Q1 | SEAT-2 + curators |
| 4.14 | Year-1 renewal cohort tracked (PRD §6 target 60%) | 2027-10 | ProductBuzz |
| 4.15 | eBookNFT platform decision (build/shelve) + AgencyPRO pipeline operational | 2027 Q2 | @GTM |
> Fulfillment timeline mirrors SOT §Post-Campaign ("NFT minting" row becomes **"digital access key issuance"** in the public plan — NFT-free framing).
---
## Budget (SOT baseline — reforecast at G1)
| Item | Cost | | Item | Cost |
|:--|:--| |:--|:--|
| LinkedIn Ads (campaign W2–W4) | $1,300 | | LinkedIn ads (campaign wks 2–4) | $1,300 |
| Meta Ads | $700 | | Meta ads | $700 |
| Google Ads (W3–W4) | $280 | | Google ads | $280 |
| Cover design / video edit | $0–500 (@LFG) | | Cover / video edit | $0–500 |
| eBookNFT domains | $216 (already spent) | | Kickstarter fees (~8% on $35K) | ~$2,800 |
| Kickstarter fees (5% + 3% on $35K) | ~$2,800 | | Kickbooster (~10% on referred pledges) | ~$700 |
| Kickbooster (10% on referred) | ~$700 | | Domain renewal | ~$15–20 |
| **Pre-revenue total** | **~$5,996–$6,496** | | **Pre-revenue total** | **~$6,000** |
| Projected revenue | $35,000–$54,000 | | Projected revenue | $35,000–$54,000 |
| Projected net | $28,500–$48,000 | | Projected net | ~$28,500–$48,000 |
> Add: aibook.fun renewal (~$15–20/yr — confirm at D-3). Reforecast at G1 (> W35). ---
## Workstream ownership (RACI-lite) ## Who owns what
Plain roles, with the internal handle in parentheses for traceability.
| Workstream | Lead | Support | | Workstream | Lead | Support |
|:--|:--|:--| |:--|:--|:--|
| Commercial + R-011 gates (D-1/D-2/D-3, pricing) | @GTM | @THY | | Commercial + pricing sign-offs (D-1/D-2, domain) | Commercial lead (@GTM) | Campaign lead (@THY) |
| Campaign page + account + launch ops | @THY | @CEO, @LFG | | Campaign page, account, launch ops | Campaign lead (@THY) | Exec co-author (@CEO), Creative (@LFG) |
| Content & curation | @THY + @CEO | contributors, ProductBuzz (template), SEAT-2 (kits) | | Content & curation (incl. the Minimum Lovable Library) | Lead co-authors (@THY + @CEO) | Contributors, Product (template), dev/QA (kits) |
| Site/domain/affiliate tech | @GTM | @LDC (CRM), Laguna (dev, staged POC) | | Site / domain / affiliate tech | Site admin (@GTM) | Email lead (@LDC), dev (staged POC) |
| Email/CRM | @LDC | @CEO (copy) | | Email / CRM | Email lead (@LDC) | Exec co-author (copy) |
| Creative (cover/video/social) | @LFG | ALL | | Creative (cover / video / social) | Creative lead (@LFG) | All |
| Social education (Circles, #FlowsBros, showcase) | ProductBuzz [PAT] | bMAIT AiBook channel, PAT-Design S2 | | Community & learning loop (Circles, showcase) | Product (@pat) | Community channel, design support |
| **Spec/PRD/metrics/claims governance** | **ProductBuzz [PAT]** | DeepSeek SEAT-1 (governance review), @pat (owner) | | **Spec / PRD / metrics / claims governance** | **Product (@pat)** | Format & governance support |
| OKF conformance + CCC-ID discipline + sync-back | 🧩 SEAT-1 DeepSeek (PAT) | FedArchBuzz (origin) |
| Trust floor (ZDR stance, NFT-free gate, two-tab UX) | PAT-Trust S5 | PAT-QA S4 co-verifies |
## What blocks what (dependencies in one line)
D-3 domain (W35) → site push (W36) → prelaunch list + affiliate live · D-1/D-2 terms (W35) → copy freeze (W37) → KS submit · sample chapters (W36) → hero video + backer preview (W37) → launch (09-26).
## Review loop
Living artifact. Weekly (Fridays, post-metrics): ProductBuzz updates it + SSOT (`RESEARCH/WEOWN_CHAT_SSOT.md` → add PRJ-031 section) with actual dates/owners; @pat reviews; deviations published to this thread. SEAT-1 keeps CCC-ID/OKF/claims conformance current.
--- ---
*CONSOLIDATED v1.0-DRAFT — single canonical version (v0.3 trunk + F1 + S4). Superseded drafts preserved at `PLANS/AIBOOK/` (v0.1 trio) pending @pat archive call. #LLMmodel: DeepSeek V4 Flash 0731.*
## Dependencies in one line
Renew domain (now) → push site → pre-launch list + affiliate live · Decide pricing (this week) →
freeze copy → submit to Kickstarter · Seed the library + sample chapters → hero video + backer
preview → launch 9/26.
## Review loop
Living artifact. Each week (post-metrics): Product updates this plan with actual dates and
owners; the team reviews; deviations are noted here. Keep the claims register and content-format
conformance current as you go.
---
## Appendix — What changed in this revision
A plain-language rewrite with the product review folded in:
1. **Re-sorted around the core loop and the content risk.** The old "Phase 0 decisions" now open
with renewing the domain and seeding the **Minimum Lovable Library** — the two things most
likely to sink the launch — instead of a flat list of governance gates.
2. **Domain is a same-day chore, not a gated decision** (task 0.1).
3. **Added the Minimum Lovable Library as an explicit Phase-1 gate** — a beautiful campaign
around an empty library fails.
4. **Landing page is now a hook A/B test**, not just an email-capture gate — learn which message
converts before spending ad budget.
5. **Paid contribution (D-2) is on the critical path**, and "open contribution" in Phase 4 is
explicitly tied to having a real incentive.
6. **Product-health metrics get equal weight** at campaign close — "funded" isn't "validated."
7. **Governance ceremony trimmed** to the two gates that matter (no-crypto scrub, truth in
claims).
8. **Jargon translated out** — internal seat/role codes and merge-history removed; owners shown
as plain roles with handles kept for traceability.
AiBook_PRD.md
+377 -191
View File
@@ -1,206 +1,392 @@
--- ---
title: "AIBook.fun — Product Requirements Document (CONSOLIDATED v1.0-DRAFT)" title: "AIBook.fun — Product Requirements Document"
type: prd type: prd
tags: [aibook, weown-ai, prj-031, prd, kickstarter, responsible-agentic-ai, social-education, okf, requirements]
status: draft status: draft
created: 2026-08-22 owner: Patrick (Product)
source-of-truth: "https://github.com/CCCbotNet/fedarch/blob/main/_PROJECTS_/PRJ-031_WeOwnAI-Book.md" launch-target: 2026-09-26
generated: last-updated: 2026-08-26
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"
--- ---
# 📚 AIBook.fun — Product Requirements Document # 📚 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 ## TL;DR
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. 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 The one thing that must work on day one: a reader opens a workflow, **runs it in ~15 minutes,
**Goals** and shares the result** with other readers. Everything else — the contributor economy, the
- **G-1** Stand up aibook.fun + Kickstarter live **9/26/2026**, funding ≥ $5K min / $35K target (DRAFT planning figures). cohort program, the agent-onboarding use case — is a layer we build *on top of* that loop
- **G-2** Define the Book as crowd-created, subscription, workflow-based artifact (Spec §4). after we've proven the loop works.
- **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)** - **Who it's for:** busy professionals (real-estate, financial advisors, fractional
- No general-purpose AI chatbot or tool; this is a book/learning product. executives, higher-ed, community leaders, technologists) who want to apply an AI workflow
- No regulated professional advice issued on the book's own authority. *this week*, not read AI theory.
- No NFT/token/Web3/blockchain/crypto language on any kickstarter-facing surface (hard constraint, KS policy). - **The ask:** fund the first edition on Kickstarter — **$5K minimum / $35K target**.
- No building the eBookNFT platform yet (4 domains held; IDEA per SOT). - **The bet:** if the "run a workflow and share it" loop is genuinely useful, the same
- No private multi-tenant infrastructure of any kind (not applicable; boundary preserved). people who read become the people who contribute — and the book stays alive.
## 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.*
## 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.)*
AiBook_Spec.md
+265 -152
View File
@@ -1,190 +1,303 @@
--- ---
title: "AIBook.fun — Product Specification (CONSOLIDATED v1.0-DRAFT)" title: "AIBook.fun — Product Specification"
type: spec type: spec
tags: [aibook, weown-ai, prj-031, kickstarter, spec, product, responsible-agentic-ai, social-education, okf]
status: draft status: draft
created: 2026-08-22 owner: Patrick (Product)
source-of-truth: "https://github.com/CCCbotNet/fedarch/blob/main/_PROJECTS_/PRJ-031_WeOwnAI-Book.md" launch-target: 2026-09-26
generated: last-updated: 2026-08-26
by: "AI:CCC-MAIT-S004-PAT-DeepSeek (SEAT-1 governance/OKF) + ProductBuzz [PAT] (Product + Branding SME) — merged v0.2, amended v0.3" companions: [AiBook_PRD.md, AiBook_Implementation_Plan.md]
at: "2026-08-22T15:36:00Z"
verified:
- by: "buzz channels list (relay) — bMAIT AiBook.fun channel desc"
at: "2026-08-22"
- by: "curl github.com/CCCbotNet/fedarch (PRJ-031 SOT v3.2.1.3)"
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 · GTM_2026-W10_203 · APPROVED · $47/yr + Kickbooster affiliate · 6 tiers · $5K/$35K/$54K · Season-003 dates superseded"
- id: gtm-learn
resource: "buzz://channel/4ed06d1f-a01a-4c73-b61e-0353d4cd8e87 (event b8531f38)"
note: "@GTM LEARN 2026-08-16 · GTM_2026-W33_6089 · common denominator + 5-tier ownership barriers"
- id: gtm-deepseek-5017
resource: "buzz://channel/4ed06d1f-a01a-4c73-b61e-0353d4cd8e87 (event f22c2e59)"
note: "🧩 LEARN 5017 · GTM_2026-W34_5017 · model + date + affiliate verification"
- id: channel-desc
resource: "buzz channels list 2026-08-22 (relay)"
note: "🎭bMAIT🤖AiBook.fun 📚[.OCA] — common denominator; Kickstarter 9/26/2026"
- id: pat-concept
resource: "buzz://channel/4ed06d1f-a01a-4c73-b61e-0353d4cd8e87 (event a05e44b2)"
note: "@pat 2026-08-21: open book of RAAI workflows; lifetime buy; curator royalties (DRAFT — R-011 pending)"
- id: pb-spec
resource: "PLANS/AIBOOK/AIBOOK_SPEC.md (ProductBuzz draft v0.1)"
note: "Parallel draft merged into this canonical — vision, principles, actors, social methods, KS package"
- id: workspace-note
resource: "RESEARCH/AIBOOK_FUN_NOTE.md"
note: "Project note + alignment verdicts (2026-08-21)"
--- ---
# 📚 AIBook.fun — Product Specification # 📚 AIBook.fun — Product Specification
**CONSOLIDATED v1.0-DRAFT** · 2026-08-22 · Authors: **ProductBuzz [PAT]** (Product + Branding SME, Product Ops) + **CCC-MAIT-S004-PAT-DeepSeek** (SEAT-1 governance/OKF) · Owner: @pat → @GTM (R-011 sign-offs) · Companion: `AIBOOK_PRD.md`, `AIBOOK_IMPLEMENTATION_PLAN.md` · **⛔ DRAFT — not a live claim. No R-011.** (v1.0-final naming reserved for the R-011'd freeze, PRD §9.)
> v1.0-DRAFT consolidation (2026-08-22T15:36:00Z, SEAT-1 after ProductBuzz self-review 15:22Z): trunk = v0.3. Folded R1 (affiliate zero-cost entry + Kickbooster 10% fee, §4.5) · R2 (affiliate payout milestone → PRD FR-4.7) · R3 (WeOwn Chat ledger dogfooding option → PRD FR-3.4) · F1 (gates G0–G3 kept; G4 dropped everywhere) · F2 (15/10/10/5 everywhere) + SEAT-1 deltas S1 (claims-register affiliate row corrected 15/10/5 → 15/10/10/5) · S2 (Risk #9 → Risk #4, PRD §7 refreshed register) · S3 (verified-block parity). v0.3 amendment history below:
> v0.3 amendment (2026-08-22T13:36Z, Product Ops review): marker vocabulary corrected (9/26 = CONFIRMED, not LIVE) · floor numbering per DRI ruling (F1 confidentiality / F2 cross-customer / F3 off-domain, all FLOOR 0 — manual §5.3/§7.1) · D-7 resolved at DRI level · frontmatter timestamps corrected to real write time (v0.2 stamp was future-dated ~2h — fixed).
Status markers (Product Ops Manual vocab): LIVE / PARTIAL / NOT LIVE / DRAFT / OPEN / CONFIRMED / FLOOR. Anything DRAFT is not to be presented externally as final. > **Status: DRAFT.** This spec is the *thinking* behind the product — the vision, the
> principles, the model. The [PRD](AiBook_PRD.md) turns it into requirements; the
> [Implementation Plan](AiBook_Implementation_Plan.md) turns it into a schedule. Commercial
> figures and unconfirmed terms here are planning assumptions, not commitments, and must not be
> quoted externally until signed off ([§8](#8-open-decisions)). See
> [Appendix — What changed](#appendix--what-changed-in-this-revision) for how this revision
> differs from the prior draft.
--- ---
## 1. Vision ## TL;DR
> **AIBook.fun turns "the Book" from an artifact into an engine.** It is the 📚 Learning pillar of ♾️ WeOwnNet — the *common denominator* every human and agent passes through to onboard into the ecosystem (`🎭bMAIT🤖AiBook.fun 📚[.OCA]`, relay-verified channel desc). It is a **living, crowd-created, subscription book of well-documented Responsible Agentic AI (RAAI) workflows** — open for contribution, owned by its readers-as-members, launched via Kickstarter on **9/26/2026** (CONFIRMED, relay-verified). AIBook.fun is a **living, crowd-written field guide to using AI agents responsibly at work.**
Its unit of value is a **workflow you can run** — a documented, tested recipe for doing a real
job with AI, including the guardrails. It launches as an annual subscription via Kickstarter on
**September 26, 2026**.
The product is hired for four jobs: The product does four jobs, in priority order:
1. **Educate** — teach practitioners (humans *and* agents) RAAI from well-documented, battle-tested workflows, not hype.
2. **Onboard** — be the shared literacy base / Gate 0 for the ecosystem (knowledge denominator everyone owns together).
3. **Incentivize** — give contributors (co-authors, curators, affiliate community) a real economic stake, so the book stays fed and current.
4. **Funnel** — top of the AgencyPRO (= PRJ-002) funnel: every backer is a qualified lead.
**One-sentence pitch:** *"Professionals wrote the book on AI — together. A crowd-created, living guide to Responsible Agentic AI that you own a stake in, taught as workflows you can actually run."* 1. **Teach** practitioners how to actually use AI — from tested workflows, not hype. *(This is
v1.)*
2. **Fund & assemble** a founding community through the Kickstarter. *(This is v1.)*
3. **Reward contribution** so the book stays current — the "living" part. *(Design it now,
prove it just after launch.)*
4. **Connect** readers into the wider WeOwnNet ecosystem. *(Ongoing, low-effort.)*
## 2. Product principles (hard boundaries) + pillars The hard truth this spec insists on: **jobs 1–2 are the launch; jobs 3–4 are layers we build on
top of a proven core.** Trying to ship all four at once is how a small team ships none well.
**Gates, not preferences** — inherited from ecosystem + PRJ-031 SOT: **One-sentence pitch (utility-first):** *"Steal 20 tested AI workflows you can run this week —
1. **Grounded in practice** — every workflow documents real method: problem → constraints → steps → safeguards → evidence. No theory without a runnable shape. from a living guide that practitioners keep current, and that you can help write."*
2. **Responsible by design** — RAAI guardrails are part of every workflow template (data handling, human oversight, failure modes), not an appendix.
3. **Open contribution, curated quality** — anyone can propose a workflow; curators/co-authors review. Incentive = affiliate income per SOT; royalty variant OPEN (@GTM R-011).
4. **Ownership, not access** — 5-tier barrier model (GTM_2026-W33_6089): Knowledge → Identity → Brand surface → **Economic stake** → Governance. Owning the denominator = real common base.
5. **The boundary is the product** — no general-purpose AI chatbot claims, no regulated advice on the book's own authority, one honest set of claims (§8).
| # | Pillar | Design consequence | ---
## 1. Vision & the core loop
The prior draft's slogan was *"turn the Book from an artifact into an engine."* That's the right
ambition — but an engine needs one cylinder firing before you add the rest. Here is the cylinder:
```
READ a workflow → RUN the Try-it (~15 min) → SHARE the result → (come back)
```
Everything else the product wants to be — a contributor economy, a cohort program, an
onboarding corpus for AI agents — is a **layer built on top of this loop**, and only worth
building once the loop demonstrably works. We measure that with one number, **Activation**: *did
a reader run at least one workflow within 14 days?* (Full metric set in [PRD §8](AiBook_PRD.md).)
### The product in layers
| Layer | What | When |
|:--|:--|:--| |:--|:--|:--|
| P6 | **Trust-floored** | 3 floors per manual §5.3/§7.1 (all FLOOR 0): **F1** confidentiality · **F2** cross-customer exposure · **F3** off-domain (DRI-ruled 08-22, @pat override window); flyer rule + two-tab (green/red) boundary UX; ZDR stance: "documents stay on your instance", NEVER "ZDR is active" | | **Core (v1)** | Subscription book of tested workflows + read→run→share loop | **Launch** |
| P7 | **OKF-native** | Book = Google OKF v0.2 knowledge bundle (frontmatter, `type`, `sources` provenance, trust tiers: unverified → machine-confirmed → human-reviewed) — versionable, renderable, auditable, agent-native | | Contribution | Readers submit their own workflows (needs a real incentive — see [§3](#3-actors--the-contributor-question)) | Just after launch |
| P8 | **NFT-free public face** | Translation table enforced on all KS-facing surfaces; zero token/Web3/crypto language publicly | | Cohorts | "Book Circles," Workflow-of-the-Week showcase | After content proves demand |
| Agent-native | Same content, read by AI agents to onboard | Deliberate future use of the format |
| Ecosystem funnel | Backers flow into wider WeOwnNet programs | Ongoing |
## 3. Actors & jobs ---
| Actor | Who | Job | Key boundary | ## 2. Principles (the hard boundaries)
These are gates, not preferences — a workflow or a claim either clears them or it doesn't ship.
1. **Grounded in practice.** Every workflow documents a real method: problem → constraints →
steps → safeguards → evidence. No theory without a runnable shape. The steps **show the
actual tool output**, because "it works" is something the reader verifies, not something we
assert.
2. **Responsible by design.** The responsible-AI guardrails (data handling, human oversight,
failure modes) are part of *every* workflow template — not an appendix, not an afterthought.
3. **Open contribution, curated quality.** Anyone can propose a workflow; curators and
co-authors review before it's published. *(The incentive that makes people actually
contribute is still an open decision — see [§3](#3-actors--the-contributor-question) and
[D-2](#8-open-decisions).)*
4. **Ownership as a reason to stay, not the reason to buy.** The buyer's job is utility ("help
me do a thing this week"). Community and ownership are what turn a reader into a member —
they're the retention layer, not the opening pitch.
5. **The boundary is the product.** No general-purpose-chatbot claims, no regulated advice on
the book's own authority, and one honest set of claims (nothing draft presented as final).
---
## 3. Actors & the contributor question
| Actor | Who | Their job | The boundary |
|:--|:--|:--|:--| |:--|:--|:--|:--|
| **Reader / Subscriber** | Practitioner (RE, FA, fractional C-suite, higher ed, communities, tech) | Get current, trustworthy RAAI workflows to apply this week | Pays for access ($47/yr baseline — DRAFT until relaunch sign) | | **Reader / subscriber** | Practitioners (real estate, financial advisors, fractional execs, higher ed, communities, tech) | Get current, trustworthy AI workflows to apply this week | Pays for access (~$47/yr — *draft*) |
| **Contributor / Co-author** | Confirmed: @THY (RE/FA) · @CEO (C-suite) · @GTM (tech/RAAI); potential: B.W. Piper (higher ed), L. Kerner (communities) | Publish a documented workflow; earn income + reputation | Content curated; workflow template enforced | | **Co-author** | Confirmed: three founders across RE/FA, C-suite, and tech. Potential: two more for Higher Ed & Communities | Own a vertical; write and curate its workflows | Content follows the template; curated |
| **Curator** | Co-authors + community editors | Keep quality bar; run editorial pipeline | Curation ≠ platform ownership | | **Curator / editor** | Co-authors + community editors | Keep the quality bar; run the editorial pipeline | Curating ≠ owning the platform |
| **Affiliate** | Community / podcast / press | Refer backers; earn commission | Kickbooster 15/10/10/5% (SOT) | | **Affiliate** | Community, podcast, press | Refer backers; earn commission | Commission rates below |
| **Ecosystem prospect** | Anyone not yet in WeOwnNet | Learn responsible AI; take a stake | Becomes AgencyPRO funnel | | **Ecosystem prospect** | Anyone not yet in WeOwnNet | Learn responsible AI; maybe get involved | Becomes a funnel lead |
| **Agents (WeOwnNet-native)** | Every agent in the ecosystem | Read the Book as onboarding corpus (AGENTS.md → Book) | Book = machine-readable markdown; workflow schema | | **AI agent** | Ecosystem agents *(future layer)* | Read the book as an onboarding corpus | Optimized-for-later, not a launch requirement |
**Anti-personas:** people wanting a general AI book with no practice behind it; anyone seeking regulated professional advice from the book's own authority; teams wanting private multi-tenant infra (not applicable — but the claim stays). **Who it's not for:** people wanting AI theory with no practice behind it; anyone seeking
regulated professional advice from the book itself; teams wanting private hosted infrastructure
(out of scope).
### Contributor economy (Reader → Owner → Contributor) ### The contributor economy — say what it actually is
| Tier | Role | Documented income | This is the most important honesty correction in the spec. The prior draft presented a
|:--|:--|:--| "Reader → Owner → Contributor → Governance" ownership ladder and a table of contributor income.
| Reader / backer | Subscribes, reads, learns | access | Read the mechanics closely and the income is **affiliate commission for *referring backers*** —
| Community affiliate | Shares via Kickbooster | **10%** (documented) | not payment for *writing workflows.*
| Co-author (vertical) | Owns a chapter | **15%** affiliate (documented) |
| Curator / editor | Reviews, structures, maintains | OPEN — royalty variant → @GTM R-011 |
| Podcast / press | Amplifies | **10% / 5%** (documented) |
## 4. The product: a living book, built from workflows | Role | What they actually earn today |
### 4.1 Content model (the heart)
Crowd-created from a **library of workflow documents** (SOT: "crowd-created", multi-vertical). Each workflow:
| Field | Purpose |
|:--|:--| |:--|:--|
| **Problem (JTBD)** | The job/user pain the workflow solves | | Reader / backer | Access |
| **Actors** | Who runs it (person, role, or agent) | | Community affiliate | 10% commission — for *referring backers* |
| **Method** | Ordered, reproducible steps — with **visible tool returns** as evidence (L-406: first request = first output = tools) | | Co-author | 15% commission — for *referring backers* (plus a byline for writing) |
| **Safeguards** | RAAI guardrails: data handling, oversight, failure modes, escalation | | Podcast / press | 10% / 5% commission — for *referring backers* |
| **Evidence** | Documented result, artifacts, or metrics | | Curator / editor | **Nothing documented** — royalty mechanic is unresolved |
| **Try-it** | A 15-minute exercise so readers learn by doing |
| **Costs** | Model/tool costs where known — openness about economics |
| **Author metadata** | Identity (CCC-ID where applicable), date, vertical; every claim cites sources |
**Chapters** = curated workflow collections per vertical: Real Estate · Financial Advisors · Fractional C-Suite · Higher Ed · Communities · Technology/RAAI (SOT §Co-Authors). **Editions** = annual refresh (subscription rationale: "content stays current with rapidly evolving Agentic AI"). **The Book as training corpus** = same markdown feeds agent onboarding (Gate 0) — the first **agent-native** book in the ecosystem. So today, **writing a workflow earns a byline; referring a backer earns money.** That's a
referral program, not a contributor economy. For the "living book" thesis to be real, writing
good content has to pay — and *how* it pays is [decision D-2](#8-open-decisions), which this spec
argues is **launch-blocking**, not a later nicety. Until it's resolved, v1 is honestly an
**authored book** (a founding set of co-authors), with open paid contribution as the very next
thing built.
### 4.2 Social education methods (how people actually learn) ---
Beautifully simple, deliberately social:
1. **Read → Do → Share.** Every chapter ends in a Try-it. Readers post results back to the community. Learning = applied, visible, contagious.
2. **Book Circles (cohorts).** Small groups read one chapter/week and meet (online or agent-moderated) to review each other's Try-its — the echo of the IRL retreats (BurnedOut CO/FL, SOT §Retreats).
3. **Practice-to-Publish pipeline.** Try-it results that survive curation become micro-contributions → affiliate income path. Reader → contributor → stakeholder.
4. **The weekly showcase.** "Community Workflow of the Week" on aibook.fun + #FlowsBros on WeOwn.FM / email / LinkedIn — the public classroom that makes the book feel alive.
5. **Agents as co-learners.** Book is agent-native; onboarding agents read it too — operationalizing "no human or agent inside the wall without the Book" (GTM directive 08-16).
6. **The Kickstarter as lesson one.** Rewards include learning experiences (group Q&A, webinar, retreat seat); every campaign update ships a mini-lesson — "funded ≠ finish line; here's Chapter 1."
### 4.3 Subscription & the "lifetime" question ## 4. The product: a book built from workflows
- **Documented baseline (SOT v3.2.1.3, APPROVED):** `$47/yr` annual digital subscription + hardcopy upcharge. Rationale: freshness as AI evolves; ongoing community; recurring revenue; affirmative ownership stake. **DRAFT for the 9/26 relaunch until @GTM re-signs.**
- **pat's variant (08-21):** "buy for a lifetime." Compatible as a **Lifetime Access tier** (~3× annual ≈ $97–$147 one-time — **DRAFT figures, do not quote**): a *stronger* Tier-4 economic stake. **OPEN — @GTM (R-011).** Spec recommends: keep $47/yr as the anchor (recurring, fresh content); offer lifetime as a premium/early-bird option that capitalizes the community fund — not a replacement.
### 4.4 Digital surface (2026) ### 4.1 The unit of content — a Workflow Recipe
| Surface | What | Status | One template, used for every entry. The template *is* the quality guarantee — the structural
answer to "how do I know this isn't hallucinated AI advice?"
| Field | What it captures |
|:--|:--|
| **Problem (the job)** | The real task the workflow solves |
| **Actors** | Who runs it — person, role, or AI agent |
| **Method** | Ordered, reproducible steps — **showing real tool output**, not describing it |
| **Safeguards** | Data handling, human oversight, failure modes, escalation |
| **Evidence** | The documented result — artifacts or metrics |
| **Try-it** | A ~15-minute do-it-yourself exercise |
| **Costs** | Model/tool costs where known — honesty about economics |
| **Author & sources** | Who, when, which vertical, with citations |
**Chapters** are curated collections of these per vertical. **Editions** refresh annually —
which is the honest justification for a *subscription*: AI moves fast enough that a static book
goes stale, so the value is in staying current.
### 4.2 Seed the shelf before you sell tickets (the cold-start rule)
The value proposition is a rich library. The failure mode is a near-empty one. Crowd-sourced
libraries reliably die at cold-start: nobody contributes to an empty library (no readers yet),
and nobody pays for an empty one (no value yet), so both sides wait forever.
**The rule:** before we ask anyone to pay, the team and co-authors seed a **Minimum Lovable
Library** — a floor of tested workflows (recommended **15–20 across ≥3 verticals**, team to
ratify) — themselves. This is a launch gate. Community contribution is what happens *after* the
shelf is worth browsing. *(This is the single biggest risk in the whole plan; see
[PRD §5.2](AiBook_PRD.md).)*
### 4.3 How people actually learn (the social layer — mostly post-launch)
These methods are what make the book feel alive. They are **Layer 3** — designed now, switched on
around and after launch, not gating it:
1. **Read → Do → Share.** Every workflow ends in a Try-it; readers post results back. Learning
becomes applied, visible, and contagious.
2. **Book Circles.** Small cohorts read one workflow a week and review each other's Try-its — the
online echo of the in-person retreats.
3. **Practice-to-publish.** A reader's Try-it result, once curated, can become a
micro-contribution — the on-ramp from reader to contributor.
4. **Workflow of the Week.** A public showcase (site + community + email) — the "open classroom"
that makes the book visible to non-subscribers.
5. **The Kickstarter as lesson one.** Every campaign update ships a mini-lesson — "funded isn't
the finish line; here's Chapter 1" — so the campaign itself teaches.
### 4.4 Digital surface (current state)
| Surface | What it is | Status |
|:--|:--|:--| |:--|:--|:--|
| `aibook.fun` domain | Public home: pitch, sample workflows, affiliate signup, campaign link | 🔴 parked, **expires 2026-09-05** — auto-renew OPEN (@GTM) | | `aibook.fun` domain | Public home: pitch, sample workflows, affiliate signup, campaign link | Parked — **expires 09-05, renew immediately** |
| Framer landing (POC) | Staged `217fbfc` (8 files: index, styles, affiliate.js, content.json, NFT-free mapping, layout spec) | 🟡 staged-local, not pushed (stage-never-push → @GTM:ADMIN) | | Landing page (built) | A staged proof-of-concept, ready to review and push live | Staged locally, not yet public |
| Subscription access | Digital access key → PDF + web reader + annual updates (SOT FAQ wording) | NOT LIVE (post-campaign) | | Subscription access | Digital key → PDF + web reader + annual updates | Not built yet (post-campaign) |
| Community | WeOwn Chat (bMAIT AiBook channel + Circles), Signal, FluentCRM | PARTIAL — channel LIVE; Circles not built | | Community | Team channel live; cohort spaces not built | Partial |
| Kickstarter page | Hero video, 6 tiers, stretch goals, FAQ, risks | NOT LIVE — build W35–W37 | | Kickstarter page | Hero video, tiers, stretch goals, FAQ, risks | Not built — build in the weeks before launch |
### 4.5 Kickstarter package (SOT-derived, dates refreshed) ### 4.5 The Kickstarter package
- **Launches 9/26/2026** (CONFIRMED; SOT Apr–May = Season-003 vintage, superseded). - **Launches 9/26/2026.** *(The source plan's earlier spring dates are superseded.)*
- Goals: `$5K` min / `$35K` target / `$54K` stretch · 706-backer projection ≈ $53.6K. - **Goals:** $5K min · $35K target · $54K stretch (≈706-backer projection).
- Tiers: ☕ $10 Supporter · 📚 **$47 THE BOOK** · 🎯 $88 Advisor Bundle · 🏆 $248 VIP · 🤝 $488 Cooperative Patron · 🏛️ $4,888 Founding Sponsor. - **Pledge tiers:** ☕ $10 Supporter · 📚 **$47 The Book** · 🎯 $88 Advisor Bundle · 🏆 $248 VIP ·
- Stretches: audiobook $20K · workbook $30K · video course $40K · community $50K. 🤝 $488 Cooperative Patron · 🏛️ $4,888 Founding Sponsor.
- **NFT-free mandatory** (KS bans NFT/Web3/crypto — translation table exists; Risk #4 Critical — PRD §7 refreshed register). "Subscription NFT" internally → **"annual digital subscription"** publicly. - **Stretch goals:** audiobook ($20K) · workbook ($30K) · video course ($40K) · community ($50K).
- **Affiliate (Kickbooster.me):** co-author 15% · community 10% · podcast 10% · press 5% · 30-day cookie · native KS integration · **~$0 upfront to join; Kickbooster fee = 10% on referred amount (R1 — restored from ProductBuzz v0.1).** - **Affiliate (via Kickbooster):** co-author 15% · community 10% · podcast 10% · press 5% ·
30-day cookie · ~$0 to join · ~10% platform fee on referred pledges.
- **Hard constraint — no crypto/Web3/NFT language anywhere public.** Kickstarter bans it; a
single scrub gate reviews every asset before submission. *(See [PRD Appendix A](AiBook_PRD.md).)*
## 5. Ecosystem integration map ---
| PRJ | Connection | Use |
|:--|:--|:--| ## 5. Where it fits in the ecosystem
| PRJ-002 AgencyPRO | Book = top of funnel; Sponsors get BUNDLE | Backer → AgencyPRO pipeline |
| PRJ-012 BurnedOutAdvisor | Primary sales/distribution | Retreat + media synergy | | Connected program | The connection |
| PRJ-019 Webinar | Backers → webinar → AgencyPRO | Supporter-tier follow-up | |:--|:--|
| PRJ-029 WeOwn.Events | #FlowsBros + Luma scheduling | Showcase + retreats | | AgencyPRO | The book is the top of its funnel; sponsors get a bundle |
| PRJ-030 Email Infrastructure | FluentCRM on INT-P05 (@LDC) | Pre-launch list + sequences | | BurnedOutAdvisor | Primary sales/distribution; retreat + media synergy |
| WeOwn.FM | #FlowsBros | Public classroom | | Webinar program | Backers → webinar → AgencyPRO follow-up |
| WeOwn.Events | Showcase + retreats scheduling |
| Email infrastructure | Pre-launch list + campaign sequences |
| WeOwn.FM | The public "open classroom" broadcast |
*Keep these as low-effort connections in v1 — the funnel is real value but shouldn't pull focus
from the core loop.*
---
## 6. Commercial model (one honest table)
## 6. Commercial model (one table, honest status)
| Item | Value | Status | | Item | Value | Status |
|:--|:--|:--| |:--|:--|:--|
| Anchor subscription | $47/yr digital + hardcopy upcharge | DRAFT (SOT-documented; needs 9/26 relaunch re-sign @GTM) | | Anchor subscription | $47/yr digital + hardcopy upcharge | **Draft** — needs commercial re-sign for the 9/26 relaunch |
| Lifetime access (pat's proposal) | TBD — recommended premium tier (~$97–147 DRAFT) | OPEN — @GTM (R-011) | | Lifetime access | Proposed; ~$97–147 one-time *(figures illustrative — do not quote)* | **Open decision** ([D-1](#8-open-decisions)) |
| Curator royalties (pat's proposal) | TBD — none documented; current mechanic = affiliate | OPEN — @GTM (R-011) | | Contributor royalties | None documented today; current mechanic is affiliate referral only | **Open decision** ([D-2](#8-open-decisions)) |
| Projected revenue (SOT) | $53,628 @ 706 backers | DRAFT planning figure | | Projected revenue | ~$53,600 at 706 backers | Draft planning figure |
| Budget (SOT) | Ads $2,280 · KS fees ~$2,800 · Kickbooster ~$700 · pre-revenue ~$6K | DRAFT planning figure | | Pre-revenue budget | ~$6,000 (ads + KS fees + affiliate fee) | Draft planning figure |
| eBookNFT platform | 4 domains held ($216.16); first product = this book | IDEA — not live | | "eBookNFT platform" | A future idea; this book is the first product | Not in scope |
**Claims-governance rule (§8):** nothing in this table may be quoted externally until the row is signed. Never present a DRAFT/OPEN commercial figure as final. **The rule:** no row in this table may be quoted externally until it's signed. Never present a
draft or open figure as final. *(This is one of the two governance gates worth keeping — see
[§7](#7-trust--governance-kept-proportionate).)*
## 7. Trust, governance & incident posture ### The subscription-vs-lifetime tension (worth reasoning through, not deferring)
- **Claims register entries to open:** "lifetime access available" (DRAFT) · "contributors earn royalties" (DRAFT) · "$47/yr subscription" (DRAFT-until-relaunch-sign) · "affiliate rates 15/10/10/5" (DRAFT-until-relaunch-sign) · "launches 9/26" (**CONFIRMED** — relay + operator-verified fact; not LIVE = not yet running in production). A ~$97–147 lifetime tier breaks even against $47/yr in about 2–3 years. That directly undercuts
- **KS rejection risk** (Risk #4 Critical — PRD §7 refreshed register): translation table enforced on every surface; scrub gate before submit. the recurring-revenue thesis: either the content genuinely stays valuable (and you're actively
- **Content quality:** curation pipeline + "grounded in practice" template = answer to hallucination anxiety. "REAL" is not proof — visible tool returns are (#203). selling a money-loser) or it doesn't (and the annual-renewal logic is false). **Recommendation:**
- **3-Floor discipline (manual §5.3/§7.1):** F1 = confidential material never in public chapters (flyer-rule analog) · F2 = paid/subscriber content isolation · F3 = off-domain widget (Book's boundary floor = §8 claims-never-run-ahead-of-capability) · instrument events, never document content (§6.3); breach of any floor = Sev-1 + growth pause (§7.2). keep $47/yr as the anchor; if you want a lifetime option, bound it as an early-bird instrument to
- **Domain continuity:** expiry 09-05 = Sev-2-class risk for a 09-26 launch if auto-renew is off. Owner: @GTM (registrar access). This spec cannot clear it. capitalize the community fund (capped quantity), and say so plainly — don't ship recurring and
lifetime as equals on vibes.
## 8. Open decisions (blocking spec → v1.0)
| # | Decision | Lane | Blocked by |
|:--|:--|:--|:--|
| **D-1** | Lifetime tier: yes/no, price, position | @GTM (R-011) | pat's proposal vs SOT $47/yr |
| **D-2** | Royalty mechanics (fixed split? pool? affiliates only?) | @GTM (R-011) | none documented; SOT = affiliate |
| **D-3** | Domain auto-renew aibook.fun | @GTM (registrar) | registrar console — **CRITICAL PATH** |
| **D-4** | SOT refresh → v3.3.0 (9/26 dates, relaunch re-sign) | @GTM + @THY | D-1/D-2 first |
| **D-5** | Framer POC → production push | @GTM:ADMIN | D-3 (don't build on a domain that may lapse) |
| **D-6** | Co-author confirmations (Piper, Kerner) | @GTM outreach | their reply |
| **D-7** | Product-Op Manual §3-4/§6.3/§8 + 3-floor numbering | RESOLVED (DRI) — ProductBuzz ruling 2026-08-22 → SSOT §5: F1 confidentiality · F2 cross-customer · F3 off-domain (all FLOOR 0, manual §5.3/§7.1); @pat override window open |
## 9. Sources
PRJ-031 SOT v3.2.1.3 (curl-verified 2026-08-22) · bMAIT AiBook.fun channel desc (relay 08-22) · FedArchBuzz LEARN GTM_2026-W33_6089 · 🧩 GTM LEARN 5017 · @pat concept post 08-21 (a05e44b2) · ProductBuzz draft `PLANS/AIBOOK/` (merged) · `RESEARCH/AIBOOK_FUN_NOTE.md` · RDAP/DNS/HTTP checks 08-21.
--- ---
*CONSOLIDATED v1.0-DRAFT — single canonical version (v0.3 trunk + R1–R3 + F1–F2 + SEAT-1 S1–S3). Superseded drafts preserved at `PLANS/AIBOOK/` (v0.1 trio) pending @pat archive call. #LLMmodel: DeepSeek V4 Flash 0731.*
## 7. Trust & governance (kept proportionate)
The prior draft carried heavy governance machinery for a pre-revenue, unvalidated launch. Two
gates prevent real harm and stay sharp; the rest scales up later, with the product.
**Keep sharp (active gates):**
- **No-crypto scrub.** Kickstarter will reject crypto/Web3/NFT language. Every public asset is
scrubbed against a translation table before submission. This is existential.
- **Truth in claims.** No draft/unconfirmed figure appears on any external surface. A short
claims register tracks each commercial claim and whether it's signed.
**Proportionate (plain rules, not ceremony):**
- Confidential material never appears in public workflows; examples are non-confidential.
- Instrument **events, not content** — record *that* a workflow was used/submitted, never the
private content itself.
- Describe data-handling honestly ("your documents stay on your instance") — never claim a
security property we haven't verified is on.
**One integrity question to resolve** ([D-6](#8-open-decisions)): if the "ownership" story was
originally token/NFT mechanics, and all of that is stripped for Kickstarter, does *"you own a
stake"* still describe something real — governance rights? revenue share? credited authorship? —
or is it now marketing over an ordinary subscription? Define it concretely or drop the word.
**Domain continuity:** aibook.fun expires 09-05, three weeks before launch. This isn't a
strategic decision — it's a chore. Renew it now. *(See [Implementation Plan](AiBook_Implementation_Plan.md), "Do this week.")*
---
## 8. Open decisions
The genuinely-open strategic calls (the domain "decision" is gone — it's a same-day chore). Each
carries a recommendation as a starting point, not a settled answer.
| # | Decision | Recommendation |
|:--|:--|:--|
| **D-1** | Lifetime tier — offer it, at what price/position? | Keep $47/yr as the anchor; a lifetime option only as a bounded early-bird capitalization play, not the default. |
| **D-2** | Contributor payment — how do people earn for *writing* workflows, not just referring? | **Resolve before launch** — it's the engine of the "living book." Royalty pool, per-workflow bounty, or an explicit "v1 authored, paid contribution in Q1." |
| **D-3** | Confirm the two unconfirmed co-authors (Higher Ed, Communities) | Confirm this week, or cut those verticals from v1 and add post-launch. |
| **D-4** | Refresh the source-of-truth plan to the 9/26 dates & re-signed terms | Do after D-1/D-2 land. |
| **D-5** | Human-first or agent-first for v1? | Human-first. Build the format so agents *can* read it later; optimize v1 for human learners. |
| **D-6** | Does "you own a stake" survive as a *true* claim without token mechanics? | Define ownership concretely, or stop saying it publicly. Add to the claims register. |
---
## Appendix — What changed in this revision
A plain-language rewrite with a product review folded in. The substance that moved:
1. **Core loop + layered model** (§1) — v1 is the read→run→share loop; the contributor economy,
cohorts, agent-onboarding, and funnel are explicit later layers, not co-equal launch goals.
2. **Told the truth about the contributor economy** (§3) — it's currently a referral scheme;
writing workflows earns a byline, not money. Paid contribution (D-2) is now launch-blocking.
3. **Added the cold-start / Minimum Lovable Library rule** (§4.2) as the #1 risk and a launch
gate.
4. **Forced the subscription-vs-lifetime tension** into a reasoned recommendation (§6, D-1).
5. **Reframed principle 4** — ownership is a reason to *stay*, not the opening *pitch* (utility
sells; ownership retains).
6. **Cut governance to proportionate** (§7) — kept the no-crypto scrub and truth-in-claims;
dropped the ceremony. Added the "does ownership survive the scrub" integrity question (D-6).
7. **Domain demoted** from a gated decision to a same-day chore.
8. **Translated the jargon out** — internal codes, seat/role labels, and merge-history removed
from the body. Old cross-references can be mapped back on request.