# 📚 AiBook.fun

**An authored field guide of runnable AI workflows for work.**

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 + 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**.


## Content

- [Content management guide](workflows/content-management.md) — write, review, QA, and ship chapters
- [Chapter blank](workflows/chapter-structure.md) — copy per vertical; leave the blank untouched

## The idea in one loop

The one thing the product must do well:

```
READ a workflow  →  RUN the Try-it (~15 min)  →  SHARE the result  →  (come back)
```

If readers run workflows and share results, the guide is alive. Everything else — community
contribution, cohort learning, onboarding for AI agents — is a layer built on top of that loop.

## Who it's for

Busy professionals — in real estate, financial advice, fractional executive roles, higher
education, community leadership, and technology — who want to **apply an AI workflow this week**,
not read AI theory.

## What's in this repository

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. Path from now to launch and fulfillment |
| [Content management](workflows/content-management.md) | How chapters are written, reviewed, QA’d, and kept current |
| [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. Writers start at the **[content management guide](workflows/content-management.md)** and the **[chapter blank](workflows/chapter-structure.md)**.

## How it works (the short version)

- **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.
- **Currency:** recipes are updated as tools and models change (often weekly or monthly). The
  `$47/yr` subscription funds that work. “2026 edition” is catalog framing, not a once-a-year reprint.
- **Contribution:** the first edition is written by a founding set of co-authors; open community
  contribution follows once the library is worth browsing.
- **Responsible by design:** the guardrails (data handling, human oversight, failure modes) are
  part of every workflow, not an appendix.

## Project status & roadmap

| Stage | Focus |
|:--|:--|
| **Now → launch** | Seed the founding library, build the campaign, crowdfund the first edition |
| Post-launch | Fulfill the first edition; open community contribution |
| Later | Cohort learning, annual editions, deeper ecosystem integration |

AiBook.fun is part of the **WeOwnNet** ecosystem.

## License

Released under the [MIT License](LICENSE) · © 2026 WeOwnAI.