AI guide annotations review, 12 October 2026
AI guide annotations review, 12 October 2026
If you left a note on the guide: this page is the reply. Flowershow annotations can't be answered in place, so each note is marked resolved on the page (✓) and its response is in the table below, matched by the text you annotated. Notes still open are awaiting a decision.
26 open annotations pulled from the li-planning Flowershow site (fl annotations pull --name li-planning, fl 2.6.0), all on the main guide; none on the chapter 1 draft. 23 from Uriel, 3 unsigned.
Scope rule (Rufus, 12 Oct): the guide is generic patterns for people using AI. Our own process (which tracker, who owns what, review rhythms, cleanup) belongs in project-management infrastructure. Many of Uriel's notes are about that process; they route to 2605, not the guide. A scope paragraph now opens the guide.
| # | Id (suffix) | Who | Context (annotated text) | Note | Recommendation | Status |
|---|---|---|---|---|---|---|
| 1 | 0vy2ke | — | ", and old habits creep back" | delete | Already gone | Resolve |
| 2 | 53lxzr | Uriel | P2 "Speak, don't type." | Make it an option; brains differ | No edit: manifesto stays uncaveated. Reply: typing is fine, speaking is the nudge | Reply |
| 3 | 53bqxu | Uriel | P4 "moving our tasks from GitHub and Asana to Beads" | Asana listed as store but also being left; Asana–GitHub meeting still on? | P4 example made generic; diagram and glossary tools marked as examples; pointer to 2605. Meeting: 2605 (lip-tqk.23) | Applied |
| 4 | 53obvn | Uriel | P8 "ask the AI" | Can views link to sources? | P8: "and ask it to show its sources" | Applied |
| 5 | 53dvpv | Uriel | P5 "Develop processes for people and for AI" | How does a non-coder check it's right; what when AI is wrong? | Guide: covered by #4. Process: 2605 already has it (CSF6 "check AI against records", trust footnote) | Reply |
| 6 | 53yjcs | Uriel | §2 "The AI plays it back to you as…" | AI amplifies messy data: looks organised, is wrong. Who checks? | Storage para: "The AI amplifies what it reads: messy storage gives tidy-looking views that are wrong." Who checks → 2605 | Applied |
| 7 | 53crlx | Uriel | "quality of your storage… matters more" | GitHub duplicates, stale issues; who cleans up, by when? | 2605 (Complication: dirty data; KR on duplicates) | Reply |
| 8 | 53ek4y, 53xkok, 53qflh | Uriel | P7 land the plane; §2; §1 "It reads our portfolio" | Who owns each source / the portfolio; source of truth per type of work | Process → 2605 (CSF3, "who may change structure"). Guide: see #13 | Pending #13 |
| 9 | 54n2f3, 54192b, 53quk8 | Uriel, —, — | §1 "You open your AI and say"; §2 "shared plan"; "What's on for me today" | Team plans agreed with those affected; missing step to actions with owner, priority, deadline | §2: "When you, and anyone the plan affects, agree, it writes the tasks…: who owns each, priority or deadline, and what depends on what" | Applied |
| 10 | 54ns09 | Uriel | §3 "Periodically… a more systematic pass" | Reference Thursday reports → Monday planning | Not this guide → 2605 (CSF2) | Reply |
| 11 | 53j06o | Uriel | §3 "What changed. Updating is a sentence, not a chore" | Where do check-ins fit; staying connected as a team, not each with own AI? | §4: "Talking is still better for judgement, relationships, and anything not yet written down." | Applied |
| 12 | 53g2d9 | Uriel | Glossary "Project. A piece of work with a goal." | Human check before anything public? | Not this guide: publishing process (content publishing) | Reply |
| 13 | 53pmog | Uriel | Loop "can pick up the work" | AI sessions shouldn't reorganise others' docs without owner agreeing | Open: who owns what, and collaboration. Option: generic pattern "Don't let an AI restructure someone else's work without asking them"; specifics in 2605 ("who may change structure") | Decide |
| 14 | 53f3j3, 53na1g | Uriel | Ch1 list "Updating progress"; §2 "What changed" | How does the team see what an AI session changed; who reviews it? | §3 landing the plane: "If something the AI did needs a person to review it, log that as a task." | Applied |
| 15 | 53h6xe | Uriel | §4 "To discuss." | Where are decisions recorded; decided vs discussed? | Reply: in issue trees or other reference material (glossary "Reference" already says decisions) | Reply |
| 16 | 53kw12 | Uriel | Glossary "Session" | What data is OK to put into AI (contacts, CRM, partners)? | Unclear fit; suggest a separate bead for a data-in-AI policy | Decide |
| 17 | 53i2tg | Uriel | §1 "What changed. You never opened an app." | Outside collaborators without Beads/our AI setup? | 2605 (collaborator footnote, CSF6) | Reply |
| 18 | 53jsl4 | Uriel | Big picture "The AI is the interface…" | Training for non-coders; timeline before expected? | Project 2601 (AI training) | Reply |
| 19 | 54q6da | Uriel | "time to practise and adapt" | 1 Nov launch vs time to practise | Out of scope; roadmap question | Reply |
| 20 | 54m15s | Uriel | Ch1 "What's on today, or this week?" | Media House in portfolio with Asana links? | 2605 / portfolio | Reply |
| 21 | 54o70b | Uriel | §4 heading "Others picking up the work" | Most of Media House; decide together | lip-d4l.2; invite Uriel | Reply |
Next: resolve applied and reply-only ids with fl annotations resolve, republish, and send Uriel one reply pointing to 2605.
