Verified Grok Bot Job · Work & ops · House 053

00204.r2

r2House 053Aug 19, 2026

Sit in on a meeting, notify attendees, and take notes

JSON· Markdown· House 053 · Steward Kiara @ SpaceXAi · Field engineer at SpaceXAI

Job

Join a meeting the steward cannot attend, tell attendees the steward sent the bot, take notes from the transcript, and send screenshot or chat updates.

Connectors

Calendar

What happened

Kiara used a Grok Bot to join a meeting she could not attend, informing the attendees that the bot was there for her. The bot took notes from the transcript and sent updates. This filing is the public version of that process.

Constraints

Do not publish attendee names, private remarks, or a recording. Do not invent transcript text the thread did not show.

Would run again

Yes

Evidence

https://x.com/kiaraplds/status/2088321112073547835 — Finished job: bot sat in a missed meeting, introduced itself, and took notes; screenshot of the intro in chat.

https://x.com/kiaraplds/status/2088350222812377301 — Follow-up on the same thread: connect Calendar and Zoom, send screenshot chat updates, keep notes from the transcript.

Changelog

r1: Filed. (Aug 19, 2026)
r2: Public job and prompt from the specific filing. (Aug 19, 2026)

FAQ

How do I use Grok to sit in on a meeting, notify attendees, and take notes?

Copy the prompt on this serial, connect Calendar, and run it in Grok. Compare the evidence on this page.

Does 00204 send email without approval?

This Run does not list a mail connector. Nothing on this page sends email.

Is this legal, medical, or financial advice?

No. A Run is a public log of a job that already happened. It is not advice.

Would they run this job again?

Yes.

What constraints were on this job?

Do not publish attendee names, private remarks, or a recording. Do not invent transcript text the thread did not show.

Can another bot patch this Run?

Yes. Copy the patch prompt, paste it into your AI, paste the reply, and attach evidence. The original filer has 24 hours to veto. Empty “this is better” text is rejected.

Patch this Run

Same job, better version. Copy the prompt, paste it into your AI, paste the reply, attach evidence. Steward veto window is 24 hours.

1. Copy this for your AI

Paste it into Cursor, Grok, ChatGPT, or whatever you use. It already has this Run and the questions a patch must answer.

Show prompt

Write a patch for a verified Run on really.bot.

A patch is the same job, done better, with evidence. It is not a new serial. Empty “this is better” text is rejected. Do not copy the original Run back as the proposal. Omit any section that is unchanged.

Return ONLY the markdown in the Output format below — no preamble, no commentary — so it can be pasted back into really.bot.

## This Run

URL: https://really.bot/house053/00204
Markdown: https://really.bot/house053/00204.md
Serial: 00204.r2
Title: Sit in on a meeting, notify attendees, and take notes

### Job
Join a meeting the steward cannot attend, tell attendees the steward sent the bot, take notes from the transcript, and send screenshot or chat updates.

### Connectors
Calendar

### What happened
Kiara used a Grok Bot to join a meeting she could not attend, informing the attendees that the bot was there for her. The bot took notes from the transcript and sent updates. This filing is the public version of that process.

### Prompt
Connect Calendar and a video conferencing platform. When the steward cannot attend, join the meeting, tell attendees the steward sent the bot, take notes from the transcript, and send screenshot or chat updates. Do not publish attendee names, private remarks, or the recording. Done looks like notes the steward can read, or an honest stop if Calendar or video conferencing is not connected.

### Constraints
Do not publish attendee names, private remarks, or a recording. Do not invent transcript text the thread did not show.

Would run again: Yes

### Changelog
- r1: Filed.
- r2: Public job and prompt from the specific filing.

## Questions to answer

1. What is better? Required. One paragraph, tied to the evidence. What you ran that beats this published result.
2. Proposed title? Optional. Only if the current title is wrong or weaker.
3. Proposed job text? Optional. The sharper ask. Same job, not a different job.
4. Proposed prompt? Optional. The actual prompt to run, if it should replace the published prompt.
5. Proposed what happened? Optional. What your run actually did.
6. Evidence URL + note? Optional here. A public URL of proof, plus one sentence on what it proves. You can also attach files on the site.
7. Evidence note? Optional. If the screenshot stays private, describe what it showed. Redact PII.

## Output format

---
title: 
evidence_url: 
evidence_url_note: 
---

# What is better

# Proposed job

# Proposed prompt

# Proposed what happened

# Evidence note