docs: index the chapter blank; chapters are the reading unit; $47/yr signed

This commit is contained in:
pat
2026-08-31 07:21:19 +00:00
parent efc859b339
commit 48425b0baf
+16 -15
View File
@@ -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