Session Metadata

.scribekit/session.json, beside the transcript. It is ScribeKit's bookkeeping: the transcript is the user's document, and losing or failing to parse this record never makes the transcript unusable.

Lifetime

Written before a meeting begins, and updated only after its transcript has been flushed and closed — and after any retained recording has been finalised. That ordering is the durability guarantee: a record saying a meeting completed is a claim about files that have already closed.

A completion that cannot be recorded leaves the session recorded as unfinished rather than falsely as finished.

What it records

Where the session stands: its identity, its MeetingState, its times, the applications captured, and the recognition language. It holds no transcript text.

MeetingState is the persisted domain lifecycle, with explicit transition rules. The runtime's MeetingRuntimeStatus — which has a failed case the persisted enum does not — is a presentation derivation and is not what is stored. See Meeting Lifecycle.

The distinction the states carry matters: an unexpected capture termination is recorded as interrupted, not completed, because a completion additionally claims that the meeting ended because someone ended it. See Failure Semantics.

Reading it back

• A session marked in progress at launch is offered for recovery.
• A damaged or newer-format record is reported and left exactly as it is. ScribeKit never repairs, rewrites or deletes one.
• A directory with a ScribeKit transcript and no record is listed as a legacy meeting, with only the facts the transcript itself states.
• A record must exist for a meeting to have an identity that notes and reviewed marks can attach to.

None of that is load-bearing for the transcript, which reads perfectly on its own.