Connect a calendar and the day marks itself

Always-on capture already removes the worst decision: you never have to predict which conversation will matter, because the transcript exists either way. But it leaves one small piece of work behind. At the end of a day with eight meetings in it, you have one continuous transcript and eight spans to draw across it.

That work is not hard, but it is exactly the kind of small, repeated, end-of-day task that quietly doesn't happen. And your calendar already knows the answer. It knows the meeting was called "Roadmap review", that it ran from 14:00 to 15:00, and that it was a different meeting from the one before it.

So Earkeep reads it, and the marking stops being your job.

Every event becomes a span. Earkeep matches each event on your connected calendar to the stretch of the day's transcript it covers, and keeps that stretch as a meeting. You end a day of eight meetings with eight named transcripts and nothing to file.

The name comes from the agenda. A kept meeting arrives titled with the event's own name rather than a timestamp, so a week of saved meetings reads like your calendar rather than like a log.

Nothing is recorded differently. A calendar connection changes only which spans get kept, not what gets captured or how. Capture and transcription are the same continuous, local pipeline either way, so a meeting that isn't on any calendar is still in the transcript, waiting for you to drag a span across it by hand.

Reading your calendar happens on your own device. The connection is used only to read event names, times, and similar metadata, locally, so Earkeep knows where the meetings were. Your calendar is not copied to a server, because there is no Earkeep server to copy it to. See private by design for the whole network picture.

Calendars describe intentions, and conversations don't always agree with them. Every version of that is already covered, and none of it costs you a word of the transcript, because capture was never keyed to the calendar in the first place:

The meeting started before the invite said. People were already talking at five to the hour, and it is all in the transcript. Pull the span's edge up to where the conversation actually began.

It started late. The first ten minutes are the sound of people waiting. Pull the edge down and the meeting starts where the meeting started.

It finished early. Trim the tail, or leave it: an extra quiet stretch at the end of a kept meeting costs nothing but a few lines.

It overran by an hour. Nothing said after the scheduled end was lost, because the transcript never stopped at the scheduled end. Drag the edge out to the real one.

It was really one conversation across two invites, or never happened at all. Draw a single span across both blocks, or drop the one for the meeting that got cancelled in a chat message nobody put on the calendar.

So an automatic span is a good first draft rather than a verdict, and correcting one is a drag of an edge, not a form to fill in. And when a change on your calendar would reshape a meeting you have already saved, Earkeep asks first rather than quietly rewriting something you kept.

• Always-on capture: the continuous transcript that makes automatic spans possible, and how to mark them by hand.
• Private by design: what your calendar connection does and doesn't send anywhere.
• For project managers: turning a day of back-to-back calls into individually kept meetings without touching anything between them.
• For people managers: why 1:1 notes captured this way can look like an eidetic memory.