Test a reusable document template with contrasting examples

A template can produce one convincing document while failing the next case. Test the reusable source with contrasting inputs rather than polishing only a finished copy. The following invitation is fictional and expanded manually. It demonstrates placeholder and condition review, not an automated Kiguri template engine or an actual invitation being sent.

Define the placeholders and conditional blocks

Write a short source: “{{host}} invites {{audience}} to {{topic}} on {{date}}.” Add a video-only sentence: “Bring an approved visual example for the video discussion.” Add a question sentence using {{question_owner}} when supplied, otherwise {{host}}. Finish with “Afterward, {{host}} shares {{follow_up}}.”

Make a contract describing required fields, repeated fields, and conditions. Host must appear consistently in the opening, fallback question route, and closing. Topic, audience, date, format, and follow-up are required. Question owner is optional. The video paragraph appears only for the video format. Decide what unsupported or missing format means instead of silently applying a convenient default.

Expand a complete video fixture

Use these invented values: host Nora, audience writers, topic Outline review, date 3 November 2026, format video, question owner Eli, and follow-up review notes. The opening becomes “Nora invites writers to Outline review on 3 November 2026.” The video sentence remains. Questions go to Eli. Afterward, Nora shares review notes.

Check every placeholder against the fixture, including repeated names. If the source closing still contains a literal old host, Dana, the expansion fails even though the greeting correctly says Nora. Record the precise source location behind the stale detail. Replacing Dana in this one output does not establish that the source will work for the next host.

Expand a contrasting text-only fixture

Now use host Sam, audience editors, topic Terms check, date 5 November 2026, format text, no question owner, and follow-up written questions. The opening becomes “Sam invites editors to Terms check on 5 November 2026.” The video sentence disappears. Questions go to Sam. Afterward, Sam shares written questions.

Read the complete result, not just the changed fields. A closing sentence saying bring the visual example described above would now refer to a suppressed paragraph. An empty question-owner substitution would leave no usable help route. The fixture tests conditional dependencies and fallback behavior, not merely whether the date changes.

Repair the reusable source and repeat both expansions

Replace literal inherited details with the appropriate fields. Put references that depend on the video paragraph inside the same condition, or rewrite them so they remain meaningful without it. Define the fallback question sentence explicitly. Keep a finding log naming the defect, source rule, affected fixture, and correction.

Expand both examples again from the repaired source rather than copying the already patched outputs. Search for unresolved placeholder notation and inspect repeated fields for inconsistency. A fix for text-only content must not accidentally remove the useful video instruction from Nora's version. Passing one contrasting case cannot stand in for checking the other.

State the supported cases and finish check

Record which formats and optional fields the contract covers. Leave additional variants, such as multiple hosts or an unknown date, unsupported until their rules are designed and tested. Do not imply that the template handles every invitation merely because two examples read well.

Ask a second reviewer to reproduce the two expansions using the contract alone. If they disagree about whether a section appears or where questions go, clarify the source rule. The useful result is a small reusable contract and reproducible outputs whose meaning stays coherent across the cases actually checked.