Demo

From a meeting to a recap people trust

A note taker joins an invented team’s stand-up, transcribes it on the team’s own computer and writes a recap. Each action item goes to its owner, who alone can approve it, and each recap goes where its meeting title says. When a transcript is late, one placeholder post is edited in place. A second panel checks two suspicious emails.

This is a simulation. No AI model runs on this page and no audio plays: the stand-up is a scripted transcript, the recap is written in advance with one action item wrong on purpose, and the team, the emails, the domains and every source’s answer are invented. The channel, the private messages and the board are mock lists on this page. Nothing you do leaves your browser or is kept, and reloading the page starts again.

Take the five parts in order, or jump to any of them. Each says what it is doing as it goes.

1. Capture the stand-up

“Stand-up, day 3” starts at 09:00. Three people are finishing release 2.4 of an invented stargazing app:

Wren, team lead, hosting the call
Juniper, app developer
Basil, app developer

Note taker: Not in the call

Nothing is captured until the host lets the note taker in.

Transcript, on this computer

The transcript appears here once the stand-up is played.

Line 1, Wren: Morning. Release 2.4 is due on day 5. Where are we?
Line 2, Juniper: The star map opens in under two seconds now. I will finish offline mode by day 4.
Line 3, Basil: The crash on older phones is fixed on my branch. I am not rewriting the sign-in screen, that can wait until after the release.
Line 4, Wren: Agreed, sign-in waits. Basil, can you get the fix reviewed today?
Line 5, Basil: Yes. Juniper, could you review it this afternoon?
Line 6, Juniper: Sure, right after lunch.
Line 7, Wren: I will write the release notes and send them round on day 4.
Line 8, Juniper: One risk: the map pictures for the southern sky are still missing.
Line 9, Wren: Then we ship without them and say so in the notes. Decided.
Line 10, Wren: Thanks, everyone.

2. The recap, and who approves what

The recap always has the same shape: a summary, each person’s update, the decisions and the action items. Each action item goes to its owner in a private message, and becomes a task on the board only if that person approves it.

The recap is written once the stand-up has been transcribed.

3. Where each recap goes

A routing table keyed on the meeting title decides where a recap is posted, so a private meeting stays private. The first rule that matches wins.

The routing rules, checked from the top
When	The recap goes to
The title has “one-to-one”	A private message to the people in the meeting, and nobody else
The title starts with “Sprint”	A status update on the project board
The title has “stand-up”	A reply in the team channel’s stand-up thread
Any other title	A new thread in the team channel

Meeting title

Pick a title and send a test recap to see where it lands.

4. When the transcript is late

“Design review” (Wren and Juniper) was recorded by the meeting service and ended at 10:00. Its transcript takes a while. A scheduled job runs every 20 minutes: it claims the meeting so no other run handles it too, looks for content in three places, and tries at most 5 times.

The transcript is

The job runs at 10:20, 10:40, 11:00 and so on. A transcript ready at 11:10 is found by the 11:20 run.

Once its recap is written, its one action item, B-1, goes privately to Juniper to approve, as the stand-up’s items do. This demo lets you decide only the stand-up’s items, in part 2.

Job clock: 10:00
Meeting: Not seen yet
Tries: 0 of 5

Runs

Each run is written here with its time.

Where posts land

Mock lists standing in for a team chat and a project board. Posts that are edited keep their number. Each part also shows, under its buttons, the posts its last step added or edited.

Team channel

Nothing yet.

Private messages

Nothing yet.

Project board

Nothing yet.

5. Check a suspicious email

The companion also checks a link or an email a colleague is unsure about. It asks 4 mocked sources at once, each with a 3 second limit, reads the message’s authentication results, and writes a plain verdict. Here the verdict comes from fixed rules. The reputation service is down for the first few minutes: after 2 time-outs in a row its circuit breaker opens and it is skipped for 5 minutes, so a slow source never holds up an answer. Answers are kept for a few minutes, so a second scan reuses them.

E-1

Invoice 2291 is overdue

From: Orbit billing, at orbit-billing.example
Link: orbit-billing.example/pay
Checks in its header: SPF fail, DKIM none, DMARC fail

Your account will close today unless invoice 2291 is paid. Pay now at the link below.

E-2

Release 2.4 notes, first draft

From: Wren, at orbit.example
Link: orbit.example/notes/2-4
Checks in its header: SPF pass, DKIM pass, DMARC pass

Here is the first draft of the release notes. Comments by day 4, please.

Scanner clock: 10:00
Reputation service breaker: Closed: calls go through

The team’s own domain is orbit.example.

Scans so far

None yet.

What the demo shows

A note taker that asks first. It waits to be let in, notices when it is admitted, tells everyone it is recording, and keeps the transcript on the team’s own computer.
Recaps in one fixed shape. Summary, updates, decisions and action items, every time, so people know where to look.
Nothing becomes work without its owner. Each action item goes to its owner privately. Only they can approve or reject it, so a wrong item, like the one planted here, never reaches the board.
Routing that keeps private meetings private. A table keyed on the meeting title sends each recap to the team, to a private message or to the board.
Late transcripts without duplicate posts. A placeholder goes up once, runs that find nothing post nothing, the same post is edited when the transcript arrives, and after a set number of tries the job says it gave up. A claim on each meeting stops two runs handling it twice.
A scanner that stays useful when a source is down. Several sources are asked at once. The one that keeps timing out here, the reputation service, sits behind a circuit breaker that skips it for a while. Answers are reused for a short while, and the verdict says when it rests on fewer sources.

1. Capture the stand-up

Transcript, on this computer

2. The recap, and who approves what

Recap: Stand-up, day 3

3. Where each recap goes

4. When the transcript is late

Runs

Where posts land

Team channel

Private messages

Project board

5. Check a suspicious email

Invoice 2291 is overdue

Release 2.4 notes, first draft

Scans so far

What the demo shows