Meeting recap

The agent looks for finished recordings every couple of minutes, at the tenant's interval.

Where each person connects their own recorder (CONN-PLAUD-WHOSE), each account is read on its own and each recording goes to whoever recorded it.

A person's recordings count from the moment they connected their recorder; earlier ones are left alone.

e.g. connected today, meeting recorded last week → left alone.

An earlier starting point can be set for one person, bringing in recordings they already had; removing it restores the default.

A recording its source has renamed is still the same recording, filed and announced once.

When the recorder account cannot be read the person is told, at most once a day, and the agent keeps trying.

Only the audio is taken from the recorder; its own transcript and summary are never used.

A recording of any length is transcribed, in pieces when it is long.

A transcription that fails part way keeps what it heard and carries on from there.

The tenant says which engines transcribe and in what order; the next serves when one will not.

The page names who transcribed it, or says plainly that this was not recorded.

A recording with nothing said in it is not written up, announced or filed.

The audio is deleted when the attempt ends, worked or not.

The write-up runs on the login of the person whose recording it is (CONVO-OWN-LOGIN).

The page states only what the transcript says; anything unclear is left out, not guessed.

Names the transcriber mishears are spelled correctly on the page; the transcript stays as heard.

With a tenant mission set, the page says whether the meeting advanced it, was neutral or cost attention, and why in a line.

e.g. no mission written → no verdict on the page.

The meeting is filed under one of the tenant's folders, never an invented one, anything unclear in the catch-all, and says why.

With no calendar connected the recording is still written up, filed and announced, without a meeting name, and the Hub names that loss (SKILL-RUNS-WITHOUT).

Entries overlapping the recording, give or take half an hour, are the candidates; the tenant can widen it.

All-day entries, cancelled ones, untitled ones and titles on the tenant's block list are never offered.

e.g. "Focus Time" on the block list → not a candidate.

Which meeting it was is decided by what was said, from the entries offered and no others; none of them is a normal answer.

e.g. two overlapping meetings, the talk is plainly the second → the second.

A matched recording is filed in a folder named after the meeting, and takes its name when the recorder gave only a timestamp.

The page lists who was in the meeting and whether the names came from the calendar entry or the transcript.

Where the tenant has tied a calendar to a folder, a match on it files the meeting there whatever the write-up chose.

The page names the entry chosen and why, and lists every entry it was chosen from, with times and calendars.

Times on the page are the tenant's clock, with the zone named; matching is by instant, so a clock change costs nothing.

A published calendar address and a connected Google calendar are read into one list (CONN-GOOGLE-OAUTH, CONN-FAILING-SOURCE-BY-ALIAS).

Filing writes the page and the full transcript beside it, linked from it, into the tenant's brain (BRAIN-SKILL-TARGET).

The page is committed and pushed; a push that fails is reported as a failure, never as nothing to file.

The credential that pushes is used for that push alone, never left on disk or in a log.

Two recordings starting in the same minute are both filed, under names that tell them apart.

A recap moved or renamed by hand still counts as filed.

A recap deleted from the brain is written again at the next look.

A page records whose recorder it came from.

The recap is announced in the channel set for it, or as a direct message when none is (CONVO-PLATFORM-SPEAKS-FIRST).

The agent says in its own words that the recap is ready, where it is filed and the three most useful things in it, and offers to answer questions.

With in-thread answering switched on, a plain message in the recap channel is answered without addressing the agent (CONVO-OWN-THREAD-NO-MENTION). Off by default.

A recap blocked by a lapsed agent login says so in the recap channel, and finishes once the login is back.