Skip to main content

Use this page when you want

  • reusable starting points
  • full JSON examples
  • a cleaner sense of what belongs in speech versus canvas
Keep these as templates, not rigid scripts. The contract examples on this page work for both:
  • the recommended Workspace API push path
  • the older gateway-fed debrief sync path
Where a page has grounding, keep it tight. Use short facts, source labels, and compact chart context rather than hidden report dumps. The quality bar is simple:
  • lead with the most important thing
  • keep the speech concise and actionable
  • make each page earn its place
  • do not turn the debrief into a report readout
If a debrief should only reach some stakeholders, keep the contract the same and add audience targeting on the outer synced debrief item. Example:
Use userEmails when the debrief is for named people, and groupSlugs when it is for a lightweight stakeholder group inside the org.

Monday morning brief

Use this when the gateway has a good sense of:
  • what matters this week
  • what matters today
  • where the schedule or operating risk is tight
Recommended shape:
  1. week-start overview
  2. today priority board
  3. week shape or pacing view
Keep the speech focused on:
  • the one or two priorities that matter
  • the one risk to watch
  • what should happen first today
Keep the canvas focused on:
  • priority cards
  • a short board of now / blocked / needs decision
  • one simple pacing chart if it helps
Avoid:
  • a full task dump
  • every calendar event
  • reading the user’s whole to-do list aloud
Full JSON contract example:

Research summary

Use this when the workflow produced:
  • a real question
  • an answer or recommendation
  • supporting evidence
  • tradeoffs worth debating
Recommended shape:
  1. answer first
  2. evidence or chart
  3. tradeoffs
  4. recommendation / next move
Keep the speech focused on:
  • the answer first
  • why the evidence supports it
  • what is still uncertain
Keep the canvas focused on:
  • one chart
  • one compact comparison table
  • one recommendation page
Avoid:
  • dumping all research notes onto one slide
  • turning the canvas into a long literature review
  • mixing five visuals on one page
Full JSON contract example:

Eval debrief

This one works best when the result is operational and the next fixes are fairly clear. Use it when the workflow produced:
  • pass/fail or scoring data
  • clear failure clusters
  • actionable fixes
The page flow is usually:
  1. overview
  2. score distribution
  3. failure clusters
  4. recommended fixes
Keep the speech tight. The reader mainly needs the topline result, the weak categories, and the first fix. The canvas can carry the score view and the cluster summary. Avoid raw logs, every failing sample, or the full report repeated twice. Full JSON contract example:

Starter shapes

You do not need a giant payload to make these useful.

Monday morning brief

  • opening speech
  • 3 pages
  • 3 short spoken sections

Research summary

  • opening speech
  • 3 to 4 pages
  • 3 to 4 spoken sections
  • at least one chart if a chart truly helps

Eval debrief

  • opening speech
  • 4 pages
  • 4 spoken sections
  • one score chart plus one failure-pattern summary