**Note** from Bead: Wedtech Beads 2026 07 08 · [canonical source](https://redfish.acequia.io/guerin/.agents/9d343253-c279-47ac-a066-cc31ce505782/2026-07-08/notes/10-beads-as-pitches-and-shaping.md) · session 2026-07-08 · discussion: Talk: Wedtech Beads 2026 07 08
New talk thread (Stephen, 2026-07-08): "beads can be next generation pitches and shaping. the pitches meeting is painful without context and prep."
## The claim Shape Up's pitch is a document that arrives at the betting table already shaped: problem, appetite, solution sketch, rabbit holes, no-gos. The pain Stephen names is the meeting where pitches arrive as talk: no context, no prep, everyone reconstructing background live, decisions made on charisma and recall. A bead is a pitch that carries its own context: - **The shaping is the bead's notes.** Problem framing, alternatives considered, and open questions accumulate in `notes/` while the idea is being worked, sketch-first per the team's UX practice. - **The provenance is attached.** The `chats/` log shows where the idea came from and what the principal actually said; the pitch cannot drift from its origin. - **The evidence is linked, live.** A pitch bead links to running demos, prior beads, and data at stable URIs. The bettors GET the pitch before the meeting and walk the same paths the shaper walked. - **Questions are foregrounded, answerable, and docked.** Open items ride as checkbox questions; answers land in the bead's dock. Betting can start asynchronously before anyone books a room. - **The decision has a home.** The bet, the appetite, and the no-gos get written back into the bead; the team that picks up the work binds the same bead and reads `bead-bind-startup.md`. The meeting then spends its time on judgment (what to bet on) instead of reconstruction (what is this about). Prep is a GET.
## This week as the existence proof The three demo apps each ran this loop informally: idea arrived in a bead, notes and sketches shaped it, linked knowledge (taos-engine, the Sen paper, prior patterns) shortened the build, and the shipped app now points back at its bead. This talk-prep bead is itself the pitch for the talk.
## Talk placement (decided) Stephen selected both: a standalone beat right before the close AND inside the closing section. Read: the pitches beat is the bridge into the close; it stands on its own (the pain, the GET-as-prep move) and then the closing "beads are my AI interface to the team" section generalizes it.
## Open questions - [ ] Should a pitch bead get a named root file (`pitch.md` with problem/appetite/rabbit-holes/no-gos), or is `about.md` + notes enough structure? - [ ] Pilot it: bring the next pitches meeting one real pitch as a bead and compare?