Meeting recaps: preserve corrections across sessions

Last updated: 7 Oct 202611 min read

tutorial

A recurring-meeting recap should carry forward only confirmed decisions and open actions, with their versions and owners. The prompt must not treat a newer meeting as a blanket replacement for all prior minutes. A correction may change the wording of one action, revoke a decision, or merely add context. Record the original claim, corrected claim, confirming person, and effective meeting. If two sessions conflict, show the conflict until an authorized owner resolves it. In the next recap, distinguish completed, still open, superseded, and newly assigned actions. This keeps the record usable without pasting entire transcripts into every prompt.

Operational case

One week after Beacon's pilot meeting, a follow-up says the rollback validation passed and Dana's action is complete. The 20-depot pilot may proceed. The 47-depot expansion is still unapproved. The chair corrects an earlier recap that had mistakenly named Dana as owner of depot notification; the action returns to unassigned until Jo accepts it in the follow-up. The revision ledger retains the old wording, the correction, and the meeting where Jo accepted. It does not silently overwrite the earlier minutes or assume the full rollout became approved because the pilot condition cleared.

Prior D1: 20-depot pilot conditional on rollback test.
Follow-up: rollback passed -> condition satisfied; pilot may proceed.
Prior P1: 47-depot expansion remains unapproved.
Correction: notification owner Dana -> unassigned -> Jo accepted.
Record each state change with confirming meeting and reviewer.

Performance and operating cost

With H historical decisions and actions, a bounded carry-forward ledger needs O(H) storage; replaying all prior transcript tokens for every meeting grows much faster as the series lengthens. Diffing K changed entries is O(K) after identifiers match. A version ledger adds review work but prevents an attractive recap from erasing accountability. Archive closed actions according to the organization's retention policy instead of carrying them forever. A model summary can suggest what changed; the meeting owner confirms the operative state.

Common Mistakes

Do not overwrite an earlier record without an explicit correction trail.
Do not treat fulfillment of a pilot condition as approval for full expansion.
Do not carry a guessed owner into the next meeting as settled fact.

Connected lessons

prompt engineering

meeting records