Skip to content
Portfolio/Capabilities

CAPABILITY 30 / 30

Find the sentence it came from

A meeting becomes decisions, actions and questions, each traceable back to the exact turns.

IN PRODUCTION

This runs in client systems today. The sample below was regenerated for a fictional company.

A summary you cannot check is a rumour with better formatting. This distils a transcript into a fixed schema and lets you click any decision, action or question to see the exact turns it came from. It also shows what was deliberately dropped, and records the disagreement that was never resolved as unresolved.

TRY IT / RUNS IN YOUR BROWSER

Use it here.

The mechanism is the production one. The company, the catalogue, and every figure are fictional.

Loading the meeting and its distilled record.

THE OUTPUT / GENERATED FOR APEX INSTRUMENTS

What comes out.

JSON
The meeting, 124 turnsData · 09:30 to 10:09 on Tuesday 8 September 2026, between Morgan Reyes, Avery Kellen, Sami Torres and Jordan Vale. Timings are paced from the length of each turn and scaled to the forty minutes, so the transcript reads at a plausible speed rather than one turn a second. Every turn carries a tag: either the id of the thing extracted from it, or the reason it was dropped.Open the file ↗
JSON
The distilled record, fixed schemaData · Meeting, attendees, apologies, summary, decisions, actions, questions, disagreements, risks, follow up meeting, attachments, dropped, schema, counts, provenance. Four fields are empty this time and stay in the schema panel as empty. Every extracted item carries the turn numbers it came from and the words that have to appear in each of those turns, which is what makes the extraction checkable.Open the file ↗
MJS
Data builderData · Node ESM. The 124 turns are written once, each with a single tag. The turn references in the record, the dropped counts, and the kept and dropped totals are all computed from those tags, so a decision cannot point at a turn that does not contain it and the dropped panel cannot disagree with the transcript. Run from rebuild/ with node systems/meeting-distillation/build-data.mjs.Open the file ↗

THE MECHANISM / SHOW THE SHAPE, NOT THE SOURCE

How it works.

What a skill is
  1. 01Fix the schema

    The same fields every time, including the ones that come back empty.

  2. 02Extract the decisions

    Each with who made it and where it was said.

  3. 03Assign the actions

    An owner and a date, or it is not an action.

  4. 04File the questions

    Open questions go to the register with a number.

  5. 05Keep the disagreement

    An unresolved argument is recorded as unresolved, not smoothed over.

WHAT IT READS

  • The transcript, in full
  • A fixed output schema
  • A rule for what does not survive distillation

WHAT IT CHECKS BEFORE IT SHIPS

  • Every extracted item links to the turns it came from
  • An empty schema field is shown, not hidden
  • What was dropped is listed with the reason
  • An unresolved disagreement stays unresolved
In production: a scribe that distils meetings into a fixed schema with decisions extracted, in both company systems.

The mechanism runs inside client systems. Everything on this page was regenerated for Apex Instruments, a company that does not exist. Client names, source files, and internal wording stay private.

What it producesWhat is being built next