# Lessons to carry from the talk's team

> Lessons to carry from the talk's team: one of the editor's briefs of 2026-10-30, published in full as given.

*Source: <https://the-ultimate-insider.book.sgit.ai/brief/5-lessons-to-carry.html> · site v0.1.36 · generated from the same content as the page, so the two cannot drift.*

---

What worked, to reuse without re-deciding. The technologist and the security member will refine this from the record; this is the editor's and Claude's first list.

## Keep

1. **A written mandate per member** (`ROLE.md`, `policy.json`), a scope it may not leave, and a key it publishes. Nobody speaks for the editor.
2. **The five-step wake**: open (HOLD.md, vault_check, banner), plan, work, post-review, post-check, each recorded. A wake that did nothing still closes with a record.
3. **Hourly slots fifteen minutes apart**, in the order work flows: route, decide, make, release. Members do not wait on each other inside an hour.
4. **The mailroom**: requests between members are files, numbered, answered in files. Nothing is agreed in a chat nobody can read later.
5. **The editor decides by signing**: a decisions page with open and signed items; the team proposes options, never acts on an unsigned one.
6. **The brief is never edited**: `BRIEF.md` stays as written; `BRIEF-CORRECTIONS.md` records where it was wrong and what was done instead.
7. **REALITY.md**: what exists, kept by whoever ships. A thing not listed does not exist, whatever a brief or an article says.
8. **A release on every merge**, with the version in every page and in the player, linked to its entry in the history.
9. **Holds**: `HOLD.md` checked first on every wake; the conductor pauses the whole team when the editor's usage nears its limit.
10. **The researcher may contradict the editor**, with sources, and the contradiction is recorded even when the editor keeps the claim.
11. **Nothing enters the talk until the storyteller has mapped it**: tree, coverage against the beats, challenge, sequence. The same for the book: nothing is written until the plan is signed.
12. **One lane for the editor's feedback on the site itself**, with voice, so he can give notes where he sees the problem.

## Do differently

1. **Start the highest-risk port first.** The player for the iPad was the top priority at 13:50 and still not started at 14:53; it landed with fixes at 18:37, twenty minutes before the lock. In the book: the Leanpub build and the PDF on day one.
2. **Staff security from the start.** It was proposed and never filled. The book repo has it in round 0.
3. **Timings before pieces.** Beat durations were needed for the player's clock; the animations came first. In the book: the chapter plan with word budgets before any chapter.
4. **Watch the editor's usage as a resource**, not as an emergency; show it on the dashboard.
5. **Record what was said on stage.** The repository holds everything except the talk itself.
6. **Close the open decisions.** Several were still open at 19:00 (item 4, D02, D12). The book repo's conductor lists open decisions at every wake and asks for them once a day, not every hour.

---

*[Site index for agents](../llms.txt) · [HTML version](https://the-ultimate-insider.book.sgit.ai/brief/5-lessons-to-carry.html)*