Stories A promise's telling
messages
Anyone watching a meeting in /in understands what each agent said, who said it and what it touched, without knowing ONE's words first.
The seven beats
- World
- the meeting thread in /in
- Cast
- Tony, a newcomer, the chairman, the CEO, the heads
- Knock
- watch the messages coming in and understand them in plain english
- Want
- a thread a stranger can read
- Way
- one house style in, hover and click out
- Turn
- the parts existed; the instructions and the words did not
- Lesson
- Open
This story carries its beats but no written telling yet — text/messages.md has no “The story” section.
Connected to
Every link here was checked against the repo when the page was built. 5 names the story uses could not be found and are shown without a link.
People
- tony
- anyone watching a meeting
Skills
Each opens the skill's page.
- meeting
- writer
Paths
The flows this story walks — trigger → step → step.
- trigger (thread:append) → tool (/api/chat/watch nudge) → the panel renders summary, body, chips, speaker
Tools
Receivers and scripts it signals.
- thread:append
- agent:run
- /api/chat/watch
- /api/things
- a GitHub read route under pages/api/
Promises
What it holds; a told promise opens its own story.
- messages
- oneie-message — the tag glossary row task:01a0ee99e83d9e5c8f907f14 is shared, not copied
Events
Every event is a signal; each names the path it marks or warns.
- thread:append · from chairman · ceo · each head marks when summary, chips and speaker all resolve; warns when a post lands with no summary tags: messages, meeting
Transactions
- TTS credits — each spoken chunk is one billed /api/tts call, about two a post; a GitHub read is free
Analytics
- posts with a summary ÷ posts, per meeting thread
- chip hovers that answered unavailable
- agent posts with meta.voice ÷ agent posts
- refine findings per post, by rule
- TTS calls per post played