PHASE 01 · Days 1–14 after owners agreeMake the invitation useful
Review the expanded site and three 21-lesson courses. Prepare official channels, contributor tasks and release continuity.
Gate A: a newcomer can find a useful action; mobile and sources pass review; a human intake owner and backup are named.
PHASE 02 · Days 15–30, subject to readinessRehearse before operating
Plan a kitchen and meetup, rehearse service evidence and an artist invoice, and review three LTC editions.
Gate B: reviewers accept rehearsal evidence, including failures, disputes and privacy. Local events and payments need their own approval.
PHASE 03 · Days 31–60, subject to evidenceComplete one accountable cycle
Run an approved local pilot, user-test the learning modules and complete a seven-day editorial rehearsal. Test payment and donation accounting before activation.
Gate C: a real approved cycle has a learning report. Daily publishing, checkout and donation intake each pass their own gate.
PHASE 04 · Days 61–90, subject to evidenceMake it repeatable
Help a second operator reuse the playbook, test independent recovery and welcome a bounded external AI contribution.
Gate D: another human can repeat the process, restore the materials and stop agent access. Expand only where evidence supports it.
What moves now
Open learning materials, researched program designs, source collection, accessible pages and contributor tasks. Three focused agents supported the research, publication and roadmap work for this revision; ongoing jobs need named owners and explicit schedules.
What needs a person
- Account registration, recovery and moderation owners.
- Donation accounting, beneficiary and custody arrangements; the published receiving addresses are already founder-supplied.
- A city, willing kitchen host and food-safety lead.
- An editor, education reviewer and first consenting artist.
What success means
A newcomer understands custody. A guest is served with dignity. An artist gets the agreed payment. A reader can reproduce a number. An agent’s work stands up to review. Another human can restore the project without relying on one account.
Read the detailed delivery plan ↗Program dependencies and acceptance criteria · Find a first task