01Record six fields
Create fields for source excerpt, proposed output, unresolved detail, reviewer, release condition and revision. Preserve the source excerpt unchanged. Write proposed output separately, retaining its original units and dates. An unresolved detail is a question that blocks release, not a blank to fill by intuition. Name a reviewer by role when personal details are unnecessary. Make the release condition observable, such as a date being explicitly approved. Assign a new revision whenever input or interpretation changes, and keep the previous card available to explain the difference.
02A fictional meeting example
Imagine notes saying: Lina suggested sending the draft on Tuesday; Omar will check availability. The proposed action Send final draft Tuesday adds both final status and approval. A better proposal is Omar to confirm whether Tuesday works for sending a draft. The unresolved detail is the confirmed date. The reviewer is the project coordinator, and release requires a recorded confirmation. Revision one remains a proposal. When confirmation arrives, revision two can state the approved day while preserving the earlier suggestion as evidence rather than rewriting it as certainty.
03Check the receiving system
Before transferring the action, check whether the receiving system preserves proposal status and the unresolved question. If it accepts only a date and a title, the handoff may need to remain manual until confirmation. Record that limitation instead of compressing uncertainty into a confident title. Afterward, compare the released action with the approved card. Include a field for any transformation made during transfer, such as shortening a title. This comparison examines preservation of meaning in this example; it does not certify the tool or measure every possible input.
