diff --git a/AiBook_Implementation_Plan.md b/AiBook_Implementation_Plan.md index ed14817..fc92da9 100644 --- a/AiBook_Implementation_Plan.md +++ b/AiBook_Implementation_Plan.md @@ -4,7 +4,7 @@ type: implementation-plan status: draft owner: Patrick (Product) launch-target: 2026-09-26 -last-updated: 2026-08-26 +last-updated: 2026-08-31 companions: [AiBook_PRD.md, AiBook_Spec.md] --- @@ -16,12 +16,11 @@ companions: [AiBook_PRD.md, AiBook_Spec.md] > [Appendix — What changed](#appendix--what-changed-in-this-revision) for how this revision > differs from the prior draft. -**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 clock:** today is 31 Aug 2026; **launch is 26 Sep 2026**. Domain and price are signed. +Content is the remaining critical path. **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` +`assign MLL authors + D-3 co-authors → write the library → freeze copy → no-crypto scrub → submit to Kickstarter → launch 9/26` --- @@ -31,17 +30,16 @@ Before any copy or build locks, close these. Most are decisions or de-risking, n | # | 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.1 | **~~Renew aibook.fun~~ Done 2026-08-31.** | Registrar owner | Closed. | +| 0.2 | **~~Pricing spine~~ Done 2026-08-31.** **$47/yr** is the product. No lifetime SKU as an equal. Founding writers on **contract** (v1 authored). | Commercial + Product | Copy freeze unblocked on price. | +| 0.3 | **~~Ratify the North-Star + product-health floors~~ Done 2026-08-29.** Activation 20/35 from access date; campaign waitlist 50/100; post-key submissions 10/25 in 90 days; renewal 40/60 excluding lifetime; curation is an ops SLA, not a launch bar. See PRD §8. | Product (@pat) | Locked. Don't quote 60% renewal publicly. | | 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.* +**✅ Gate 0 — decisions closed.** **Pricing spine signed ($47/yr; writers on contract)** · **targets ratified (2026-08-29)** · Minimum Lovable +Library scoped with authors · **domain renewed (2026-08-31)** · claims register open. *Until the library has named authors and D-3 is closed, don't treat content as on track. Copy freeze still waits on claims + co-author scope.* --- @@ -53,8 +51,8 @@ campaign around an empty library fails. ### 1A · Content — seed the Minimum Lovable Library (critical path) | Task | Owner | |:--|:--| -| Lock the chapter outline (chapters per vertical, a named owner each) | Co-authors | -| Publish the Workflow Recipe template + 3 filled examples | Product | +| Lock the chapter outline (chapters per vertical, a named owner each). Blank is [`workflows/chapter-structure.md`](workflows/chapter-structure.md) | Co-authors | +| Review and freeze the chapter blank, then 3 filled examples | Product + authors | | **Seed the Minimum Lovable Library to its floor number** (team + co-authors write & test the workflows) | Co-authors + team | | 3 "clone-and-run" kits, each **verified by actually running it** | Dev + QA support | | 2 sample chapters (the backer preview) | Two lead co-authors | @@ -75,7 +73,7 @@ campaign around an empty library fails. | 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) | +| **Copy freeze** (price already signed: $47/yr, writers on contract; still freeze claims + NFT scrub) | 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 | diff --git a/AiBook_PRD.md b/AiBook_PRD.md index 09d4f07..7cf2e5f 100644 --- a/AiBook_PRD.md +++ b/AiBook_PRD.md @@ -4,7 +4,7 @@ type: prd status: draft owner: Patrick (Product) launch-target: 2026-09-26 -last-updated: 2026-08-26 +last-updated: 2026-08-31 --- # 📚 AIBook.fun — Product Requirements Document @@ -142,8 +142,9 @@ the structural answer to "how do I know this AI advice isn't hallucinated?" | **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** +**Chapters** are substantial essays, one per vertical (Real Estate · Financial Advisors · +Fractional C-Suite · Higher Ed · Communities · Technology), with full Workflow Recipes +**nested in the argument**. See [§5.4](#54-the-reading-surface-locked-2026-08-31). **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. @@ -160,15 +161,61 @@ post-launch aspiration. Community contribution is **Layer 2** — an experiment 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)). +The prior draft's "contributor economy" pays co-authors **15% affiliate commission**, which +is a reward for *referring backers*, not for *writing workflows*. -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. +**Signed 2026-08-31 (D-2):** founding writers are paid **on contract**. v1 is an authored book. +Affiliate referral can still pay for referring backers. It is not how writing is paid. Open +contribution with royalties or bounties waits for Layer 2. + +So we state plainly: **the first edition is written by a founding set of co-authors and the +team.** Layer 2 is the next thing we build, after the library is worth subscribing to. + +--- + +### 5.4 The reading surface (locked 2026-08-31) + +People read **chapters**, not a shelf of detached cards. A chapter is a substantial essay +for one vertical: it argues a way of working, then **nests full workflows inside that +argument** as the proof. + +This is a deliberate break from treating the workflow as the only page. The workflow is +still the unit of *practice* (and of activation). The chapter is the unit of *reading*. + +**Chapter page** +- Title, vertical, edition, authors +- Opening promise (what this chapter is for) plus a **Skip to a Try-it** control — activation + must not require finishing the essay +- Essay body: sections that teach the practice (stakes, constraints, how we work here) +- Nested **Workflow blocks** at the points in the argument they earn — not bunched in an appendix +- End matter: further workflows in this vertical, sources, last updated + +**Nested workflow block** (the recipe, in full — not a teaser) +1. Chrome: recipe ID, version, time, cost +2. Title as the job +3. Problem +4. Actors +5. Setup (tools, sample files, cost) +6. **Safeguards before the steps** so data-handling is read before anyone pastes a client list +7. Method, with real tool output *in* the steps +8. Evidence +9. Try-it (~15 min, sample data, mark complete — fires Activation) +10. Share result (community template; events, not content) +11. Author, sources, last updated + +**Addressability** +- Every workflow has a stable ID (e.g. `RE-01`) and a URL that opens the chapter scrolled to + that block (and a focused/print view of the same block). Campaign samples, clone-and-run + kits, and Workflow-of-the-Week link here — never to an essay with no way in. +- PDF matches this stack: chapter essay + in-place recipes. Print and web must not drift. + +**Non-goals for the reader** +- No chatbot on the chapter page +- No crypto/Web3 language +- Nested recipes are not collapsed “click to reveal” cards that hide the Method + +**Writing drafts** live in [`workflows/chapter-structure.md`](workflows/chapter-structure.md). +Copy that blank into a vertical file (`workflows/real-estate.md`, etc.) when a chapter is assigned. --- @@ -202,8 +249,8 @@ Requirements are grouped by the layer they serve; **most 🔴 items serve the co | 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-2 | Anchor price **$47/yr** *(signed 2026-08-31)* + hardcopy at-cost upcharge. No lifetime SKU as an equal product. | 🔴 | +| A-3 | Lifetime tier — **not offered as a v1 SKU** (D-1 signed 2026-08-31: $47/yr only). Revisit only as a capped early-bird later, not as an equal product. | 🟢 | | A-4 | Fulfillment ledger: backer ↔ key/upcharge tracked (a spreadsheet is fine for v1) | 🟢 | ### 6.4 The other layers — mostly 🟡 / 🟢 @@ -236,7 +283,7 @@ Requirements are grouped by the layer they serve; **most 🔴 items serve the co | 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-6 | **Domain continuity:** aibook.fun must not lapse (**renewed 2026-08-31**). | | 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)). | @@ -249,12 +296,18 @@ metrics; those measure the *campaign*, not the *product.* A funded campaign can 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? | + +**Ratified 2026-08-29 (Product).** These are the numbers we run. Do not quote the 60% renewal target on Kickstarter or any public surface. + +| Metric | Floor | Target | Clock / notes | Why it matters | +|:--|:--|:--|:--|:--| +| **Activation** — read 1 workflow + finish 1 Try-it | 20% | 35% | **14 days from access-key date, not pledge date.** North-Star. | Is the core loop actually useful? | +| **Contributor waitlist** during the campaign | 50 | 100 | People who *say* they will contribute a workflow. Not written recipes. | Early Layer-2 signal without betting launch on cold-start writing | +| **Workflow submissions** | 10 | 25 | First **90 days after keys go out** | Is paid/open contribution real once the library exists? | +| **Renewal rate** — year-1 **paid** cohort | 40% | 60% | **Exclude lifetime SKUs** from the denominator. 60% is internal. | Is a *subscription* the right model at all? | +| **Curation turnaround** ≤ 10 working days | 80% | 95% | **Ops SLA after Layer 2 is on** — not a launch health bar | Can we keep quality without becoming the bottleneck? | + +Leading indicator before fulfillment: % of the pre-launch list who run the *sample* Try-it. ### Campaign performance (the fundraise) | Metric | Min | Target | Stretch | @@ -279,13 +332,13 @@ dead product if nobody activates, renews, or contributes. ## 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. +1. **~~Renew aibook.fun~~ Done.** Domain renewed (confirmed 2026-08-31). Launch remains 09-26. +2. **~~Resolve the pricing spine (D-1 / D-2)~~ Done 2026-08-31.** Anchor is **$47/yr**. No + lifetime SKU as an equal product. Founding writers are engaged **on contract** — v1 is an + authored book; open royalties are not the v1 mechanic. Copy freeze is unblocked on price. +3. **~~Ratify the North-Star + the product-health floors~~ Done 2026-08-29.** Locked in §8: + activation 20/35 from access date; campaign waitlist 50/100; post-key submissions 10/25 in + 90 days; renewal 40/60 excluding lifetime; curation SLA not a launch bar. 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. @@ -313,8 +366,8 @@ decision-maker has a starting point — but the recommendation is not yet a deci | # | 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-1** | ~~Lifetime tier~~ **Signed 2026-08-31.** Product price is **$47/yr**. No lifetime SKU as an equal v1 product. | Locked. Don't quote a lifetime price. Hardcopy remains an at-cost upcharge. | — | +| **D-2** | ~~Writer payment~~ **Signed 2026-08-31.** The first set of writers is engaged **on contract**. v1 is an authored book. Affiliate referral can still pay for *referring backers*; it is not how writing is paid. Open contribution + any royalty/bounty is post-v1 (Layer 2), not a launch mechanic. | Locked for v1. Revisit royalties before opening Layer 2. | — | | **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 | @@ -375,16 +428,17 @@ changes from the prior draft, and the reasoning: 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). +4. **Told the truth about incentives** (§5.3). **D-2 signed 2026-08-31:** founding writers on + contract; v1 authored; royalties wait for Layer 2. Affiliate still pays referrals, not writing. +5. **Forced the subscription-vs-lifetime tension** into a real decision. **D-1 signed 2026-08-31:** + **$47/yr** only. No lifetime SKU as an equal v1 product. 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). +9. **Turned the domain into a same-day chore** (§9). **Done 2026-08-31:** `aibook.fun` renewed. 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. diff --git a/AiBook_Spec.md b/AiBook_Spec.md index eca52de..c2e3a46 100644 --- a/AiBook_Spec.md +++ b/AiBook_Spec.md @@ -4,7 +4,7 @@ type: spec status: draft owner: Patrick (Product) launch-target: 2026-09-26 -last-updated: 2026-08-26 +last-updated: 2026-08-31 companions: [AiBook_PRD.md, AiBook_Implementation_Plan.md] --- @@ -56,7 +56,8 @@ ambition — but an engine needs one cylinder firing before you add the rest. He 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).) +a reader run at least one workflow and finish one Try-it within 14 days of getting access +(access key, not pledge)?* Floors/targets ratified 2026-08-29 — full set in [PRD §8](AiBook_PRD.md). ### The product in layers | Layer | What | When | @@ -95,7 +96,7 @@ These are gates, not preferences — a workflow or a claim either clears them or | Actor | Who | Their job | The boundary | |:--|:--|:--|:--| -| **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*) | +| **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** — signed) | | **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 / 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 | Commission rates below | @@ -146,9 +147,11 @@ answer to "how do I know this isn't hallucinated AI advice?" | **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 — +**Chapters** are the reading unit: a substantial essay per vertical, with **full workflows +nested in the argument** (not a table of contents of cards). **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. +goes stale, so the value is in staying current. Reading IA locked 2026-08-31; see +[PRD §5.4](AiBook_PRD.md). ### 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 @@ -179,7 +182,7 @@ around and after launch, not gating it: ### 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 09-05, renew immediately** | +| `aibook.fun` domain | Public home: pitch, sample workflows, affiliate signup, campaign link | **Renewed 2026-08-31** | | Landing page (built) | A staged proof-of-concept, ready to review and push live | Staged locally, not yet public | | Subscription access | Digital key → PDF + web reader + annual updates | Not built yet (post-campaign) | | Community | Team channel live; cohort spaces not built | Partial | @@ -218,9 +221,9 @@ from the core loop.* | Item | Value | Status | |:--|:--|:--| -| Anchor subscription | $47/yr digital + hardcopy upcharge | **Draft** — needs commercial re-sign for the 9/26 relaunch | -| Lifetime access | Proposed; ~$97–147 one-time *(figures illustrative — do not quote)* | **Open decision** ([D-1](#8-open-decisions)) | -| Contributor royalties | None documented today; current mechanic is affiliate referral only | **Open decision** ([D-2](#8-open-decisions)) | +| Anchor subscription | **$47/yr** digital + hardcopy at-cost upcharge | **Signed 2026-08-31** | +| Lifetime access | Not a v1 SKU | **Signed D-1:** $47/yr only | +| Founding writers | Paid **on contract** (v1 is authored). Affiliate still pays referrals, not writing. | **Signed D-2 2026-08-31.** Royalties/bounties wait for Layer 2. | | Projected revenue | ~$53,600 at 706 backers | Draft planning figure | | Pre-revenue budget | ~$6,000 (ads + KS fees + affiliate fee) | Draft planning figure | | "eBookNFT platform" | A future idea; this book is the first product | Not in scope | @@ -274,8 +277,8 @@ 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-1** | ~~Lifetime~~ **Signed 2026-08-31:** **$47/yr** only. No lifetime SKU as an equal product. | Locked. | +| **D-2** | ~~Writer pay~~ **Signed 2026-08-31:** founding writers on **contract**. v1 authored. Layer 2 royalties later. | Locked for v1. | | **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. | diff --git a/README.md b/README.md index 68e8e14..a41206e 100644 --- a/README.md +++ b/README.md @@ -2,14 +2,14 @@ **A living, crowd-written field guide to using AI agents responsibly at work.** -AIBook.fun's unit of content isn't a chapter — it's a **workflow you can actually run**: a -documented, tested recipe for getting a real job done with AI, guardrails included. It's written -and kept current by the practitioners who use it, and it launches as an annual subscription, -crowdfunded on Kickstarter. +People read **chapters**. Each chapter is a substantial essay for one vertical, with full +workflows nested in the argument. The workflow is the unit of practice: a documented, tested +recipe for a real job, guardrails included. The first edition is written on contract by founding +authors. It launches as a **$47/yr** subscription, crowdfunded on Kickstarter. -> **Status: planning stage.** This repository holds the product's planning documents. The product -> is not yet live, and everything here is a working draft — figures, dates, and commercial terms -> are planning assumptions, not commitments. Public launch is **targeted for September 26, 2026**. +> **Status: planning + writing.** Planning docs and the chapter blank live here. The product is +> not yet live. **$47/yr** is signed. Domain `aibook.fun` is renewed. Other figures and unsigned +> terms are still planning assumptions, not for public quote. Launch target **26 Sep 2026**. ## The idea in one loop @@ -30,22 +30,23 @@ not read AI theory. ## What's in this repository -This is a documentation and planning repo. Three companion documents define the product: +This is a documentation and writing repo. | Document | What it covers | |:--|:--| -| [Product Requirements (PRD)](AiBook_PRD.md) | What we're building and why — scope, requirements, success metrics, open decisions | -| [Product Specification (Spec)](AiBook_Spec.md) | The thinking behind it — vision, principles, content model, business model | -| [Implementation Plan](AiBook_Implementation_Plan.md) | How and when — the path from now to launch and fulfillment | +| [Product Requirements (PRD)](AiBook_PRD.md) | What we're building and why. Scope, requirements, success metrics, open decisions | +| [Product Specification (Spec)](AiBook_Spec.md) | The thinking behind it. Vision, principles, content model, business model | +| [Implementation Plan](AiBook_Implementation_Plan.md) | How and when. Path from now to launch and fulfillment | +| [Chapter structure](workflows/chapter-structure.md) | The blank chapter for review. Copy it into a vertical file when writing starts | New here? Start with the **[Spec](AiBook_Spec.md)** for the vision, then the **[PRD](AiBook_PRD.md)** -for the specifics. +for the specifics. Writers start at **[chapter structure](workflows/chapter-structure.md)**. ## How it works (the short version) -- **Content:** every entry follows one *Workflow Recipe* template — problem, method (showing the - real tool output), safeguards, evidence, a ~15-minute Try-it, and costs. The template is the - quality guarantee — the structural answer to "how do I know this AI advice isn't made up?" +- **Content:** readers get a chapter essay. Nested in it, every workflow follows one recipe: + problem, actors, setup, safeguards, method (real tool output), evidence, a ~15-minute Try-it, + share, costs, author. Safeguards sit before the steps. The template is the quality guarantee. - **Editions:** the guide refreshes annually — which is why it's a subscription. AI moves fast, and stale advice is worthless. - **Contribution:** the first edition is written by a founding set of co-authors; open community diff --git a/marketing-site/README.md b/marketing-site/README.md index c62f499..ac68652 100644 --- a/marketing-site/README.md +++ b/marketing-site/README.md @@ -33,3 +33,14 @@ Note: Framer Sites don't run Next.js natively. For a live site with routing (A/B - 3 sample tiers shown ($10 / $47yr / $4,888) - No NFT/crypto/Web3 language (Kickstarter compliance scrubbed) - Event tracking only (not content) — PostHog/Cloudflare Analytics slot available + +## Reading demo + +A sample reading environment is wired into this Next.js app (pages router). + +```bash +npm install +npm run dev +``` + +Then open [http://localhost:3000/read](http://localhost:3000/read). One chapter is filled (Real Estate, with nested RE-01 and RE-02). This is a demo, not the live book. diff --git a/marketing-site/components/Nav.jsx b/marketing-site/components/Nav.jsx index 00e1d0b..e197218 100644 --- a/marketing-site/components/Nav.jsx +++ b/marketing-site/components/Nav.jsx @@ -1,12 +1,29 @@ import { useEffect, useRef, useState } from "react"; +import Link from "next/link"; const LINKS = [ { href: "#recipe", label: "A recipe" }, { href: "#contents", label: "Contents" }, { href: "#letter", label: "Why" }, { href: "#faq", label: "FAQ" }, + { href: "/read", label: "Library" }, ]; +function NavItem({ href, label, onClick }) { + if (href.startsWith("/")) { + return ( + + {label} + + ); + } + return ( + + {label} + + ); +} + export default function Nav() { const [scrolled, setScrolled] = useState(false); const [open, setOpen] = useState(false); @@ -39,16 +56,14 @@ export default function Nav() { return (