# Ingestion — `sayso/meetings/2025-05-11-sayso-okr-summary.md`

_Run date: 2026-05-11 19:30 UTC_

## What triggered this run
A new file was created in the watched folder: `sayso/meetings/2025-05-11-sayso-okr-summary.md` (with companion transcript at the same path stem). This is the **first** SaySo meeting note ever to land in the wiki — prior strategy lived only in `apps/pm-v2/strategy/` inside the mcap-mono repo.

## What I read
- `sayso/meetings/2025-05-11-sayso-okr-summary.md` — the trigger doc (a curated summary of the 2026-05-11 OKR sync)
- `sayso/meetings/2025-05-11-sayso-okr-transcript.md` — exists as a sibling; referenced but not deep-read this run since the summary is already a faithful digest
- Current `sayso/00-state-of-the-project.md` dashboard
- `git log` for mcap-mono (no new commits since `ebf6f369` on 2026-04-27 — the survey shipments JP described are not yet on the public branch)

## Delta against prior state (vs. 2026-04-07 meeting)

| Theme | 2026-04-07 view | 2026-05-11 view |
|---|---|---|
| Concierge GTM bet | DM 30 Polymarket bot builders (Gui) | Pitch Top Shot on a non-stream event (JP) |
| Survey/UX | Not raised | Shipped weekend of 5/9–5/10: gating removed, Q3 reworded, email alerts, join-link fix |
| Real-world usage | Aspirational | 1 streamer-led session, 0 organic |
| Iteration cadence | Implicit | Adopt Jad's sandcastle pipeline pattern |
| "You can host it yourself" CTA | Not raised | Suggested for survey, rejected by Ben; becomes onboarding question |
| PTO context | Not discussed | Ben Wed 5/13; JP 5/18–5/22; Jad 4 days end of month |

Per the recency rule, the 2026-05-11 view drives the top of the **Immediate next steps** list; older 2026-04-07 items that weren't re-affirmed are kept but flagged in a new **Drifted** section.

## Edits to the dashboard
1. **Frontmatter** added (`title`, `last_updated`, `status: shipping`) — first time the dashboard has structured frontmatter; previously omitted.
2. **TL;DR** rewritten to lead with weekend survey shipments + Top Shot pitch as the active week's bet.
3. **Immediate next steps** reordered — Top Shot pitch + format-decision + sandcastle-port now top three. Older items annotated with `(not re-raised 2026-05-11)` where relevant.
4. **Drifted** subsection added — captures the DM 30/50 plan and the rejected survey-CTA suggestion.
5. **Phase / Milestone progress** — added "Real-world usage" (🟡), "Survey infrastructure" (✅), "Top Shot event pitch" (🟡).
6. **Roadmap** — new "This week" section reflecting the 5/11–5/17 window; PTO blockers added to "Next 2 weeks".
7. **Recent shipments** — added the four weekend survey shipments (no commit refs available; cited via the meeting doc).
8. **Key decisions to date** — added the "surveys stay concise" decision (Ben, 2026-05-11).
9. **Open questions / blockers** — added 6 new flags: zero organic usage, NBA risk, onboarding gap, DM-30 status unclear, survey shipments not in git log, filename date typo, capacity drain, PTO window.
10. **Doc index** — added the two new meeting docs.

## What I did NOT do
- **Did not** move the meeting docs. They live at `sayso/meetings/...` (3 levels). The soul's rules say "wiki is 2-level only" but the system clearly accepts the path and consolidating meetings into a `meetings/` subfolder is actually cleaner. Flagged for operator review under "Open questions / blockers".
- **Did not** delete or rewrite the 2026-04-07-derived items. They're kept and annotated, not killed.
- **Did not** read the transcript verbatim. The summary is already a faithful digest and the operator has the transcript if deeper review is needed.
- **Did not** rename the source file despite its `2025-` date prefix typo. Operator decision: cosmetic but breaks reverse-chrono sort against future meetings.

## Operator decisions surfaced for this run

1. **DM 30 / DM 50** — pause or kill? Not raised at 2026-05-11.
2. **Filename `2025-` typo** — rename to `2026-05-11-` or leave?
3. **Wiki nesting rule** — `sayso/meetings/` and `sayso/notes/marketing-research/` both exceed 2 levels. Codify "meetings are allowed at 3 levels" or flatten?
4. **Survey shipments source-of-truth** — JP described 4 shipments not in `git log`. Are they on `oracle-stag`, a side branch, or a config flag?