# Meeting record kit

Five small files. Copy them, adapt them, use them in any editor. No attribution needed, no account needed, nothing to install.

From the team at https://www.getoyma.com, 2026-10-07.

## The files

- `readme.md` what you are reading.
- `meeting-record-template.md` the blank record. Fields that may stay empty are marked unknown.
- `example-notes.md` a fictional sample meeting, raw, exactly as pasted into the builder.
- `example-record.md` the same notes as the builder's engine exports them, with source line numbers.
- `example-actions.csv` the actions export, every cell quoted, formula-guarded starts prefixed with an apostrophe.

## The line grammar

- `! ` a decision: something agreed.
- `+ ` an action: something someone owes. Owner as `@name` (one word), date only as `by 2026-10-12` or `due 2026-10-12` (ISO, real calendar dates only). Pipe segments work too: `task | @dana | by 2026-10-12`.
- `? ` an open question.
- Anything else is discussion. Fenced blocks are inert.

## The rule the files keep

Missing owners and dates stay written as unknown. Tentative wording stays tentative until a person confirms it. Nothing in this kit invents a commitment.

## Ways to work

1. Mark notes with the grammar while the meeting runs, or right after.
2. Fill the template by hand in any editor, or paste the marked notes into the builder at https://www.getoyma.com/tools/meeting-record-builder and use its flags, then export.
3. Before sending the record anywhere, spot-check two lines against your raw notes. The exports print source line numbers for this.

The example-record.md and example-actions.csv are the real output of the builder engine run on example-notes.md. The builder's fixtures (node --test, `pnpm kit:meeting` regenerates from) cover both files.