A
AIOS Wiki
read-only · public mirror
Open AIOS
Wikisaysomeetingssayso/meetings/2025-05-11-sayso-okr-summary.md

SaySo OKR Sync — 2026-05-11 (Summary)

Hand-authored·4 min read·6 sections·Last edited May 12 by initial import·View history
TL;DR

> Distilled from `sayso/meetings/2025-05-11-sayso-okr-transcript.md`. Roughly the first ~10 minutes were SaySo-specific; the remainder of the call covered the AZ website refresh, Ben's runner-agent skill, Jad's "sandcastle" build-pipeline, and PTO. Non-SaySo items are captured at the bottom for completeness because they pull team capacity.

TL;DR (SaySo)

JP shipped survey + UX fixes on the SaySo app over the weekend and this morning. The platform has had one real-world session so far (run by a team member of the streamer "Paul"); no organic sessions yet. The week's main SaySo bet is pitching Top Shot on a non-stream event — JP is waiting on a reply from Matt (and Guy/Gee on the Top Shot side) before scheduling a formal pitch. Naim's earlier branding feedback suggests NBA approval may not be required if SaySo branding is kept off the event surface.

SaySo shipments this cycle (JP)

  • Survey gating removed. Surveys now auto-trigger on any session with 8+ participants (previously gated to JP's user only).
  • Survey question #3 rewritten. Changed from open-ended "was anything off about this session?" to the more positive-framed "what could have made this better?".
  • Email alert wired up. JP gets pinged whenever a session qualifies for a survey.
  • Join-link bug fixed. New users following a join link no longer bug out and get forced into the join-code fallback.

SaySo immediate next steps (decided in this meeting)

  • Pitch Top Shot on a SaySo-powered event (not a stream — a one-off event Top Shot can promote). Owner: JP. Status: waiting on Matt's reply; JP will poke again ~3:30pm if no response today.
  • Decide pitch format — casual chat vs. formal team pitch — once Top Shot responds. If formal, Ben + Simon join JP to "hone the value prop". Owner: JP to schedule once direction is known.
  • Port Jad's sandcastle pipeline pattern over to SaySo for "small wins" iteration (JP, alongside Top Shot prep). Jad's recommendation: copy mains + prompt files, run the review-finding skill repeatedly. Owner: JP.
  • (Deferred / declined) Adding "you can host this yourself" copy to the survey was discussed (Simon's suggestion) but rejected by Ben — surveys must stay concise; if users don't realize they can self-host, that's a product-UX fix, not a survey fix. Implied action: this becomes a discovery / onboarding question for the product.

Open questions / risks

  • Real-world usage is still essentially zero. JP: "I haven't actually seen any sessions run on here besides the ones that we've tested yet." One streamer-led session has occurred; no organic ones. The survey infrastructure now exists, but it's only useful once sessions actually happen.
  • NBA approval risk on the Top Shot event. Top Shot indicated NBA may be a blocker; Ben's hypothesis is that removing SaySo branding sidesteps NBA's involvement entirely. Unconfirmed.
  • Onboarding gap: users invited to a session may not realize they can host their own. Surfaced but explicitly deferred from the survey channel.

Non-SaySo items (capacity context)

These pulled team time during the same call and affect what JP / Simon / Ben / Jad can spend on SaySo this week.

  • AZ website refresh (Sam, urgent). Sam asked Simon + Jad to do a quick brush-up of axiomzen.co (logo missing, dead Hammer & Tusk link, spam-form problem, plus a Next.js port discussion). Sam wants something better-than-current shipped in "a few days, a week" because new sites going live will drive traffic to AZ. Simon pivots to this today.
  • Ben's runner-agent skill (Toby-focused). Ben built an orchestrator skill that wakes on a cron, reads bets/research from the repo, spawns coding sub-agents on a branch, reviews them, then follows up on metrics. Integrating into Toby first; conceptually could compose with Jad's pipeline.
  • Jad's sandcastle pipeline (cross-project; SaySo will inherit). End-to-end deterministic build pipeline running on the Toby MCP server: 10-step orchestrator → adversarial review cycles → multiple gates (lint, tests, build, secret scan) → resume on crash. Jad will ship it for the team to experiment with this week. Plans next: add Codex as a second adversarial reviewer (different model, different weaknesses) and add a headless-Chrome end-to-end gate. JP plans to copy this pattern into SaySo.
  • PTO: Ben off Wed 2026-05-13. JP off the week of 2026-05-18 → 2026-05-22 (cabin at Watcom — laptop available "just in case"). Jad has a 4-day Eid holiday end of month.

Memory hooks for the dashboard

  • The meeting's two SaySo-shaped delta-vs-2026-04-07 are: (a) survey/UX shipments, (b) Top Shot event becomes the primary GTM bet this week, replacing the older "DM 30 Polymarket bot builders" item as the active focus. The DM 30 / DM 50 plan from 2026-04-07 was not discussed at all this meeting — flag as drifted.
  • The kill criterion (Day-14 agent return < 10% after 30 agents) still applies but is moot until session volume exists. The Top Shot event is the bet on volume.
  • "Internal team test run" from 2026-04-07 was not raised this meeting — still open.