Make two variants and edit with an agent.

Use a saved copy of the lower-third exercise in an explicitly supplied test package. For the agent portion, use a client whose connection instructions apply to that candidate. Preserve the original and keep the exercise disposable.

1. Choose the wording and colour parameters a variation should change.
2. Promote each from Basement to the object’s Controls.
3. Raise through any containing Groups and onto the comp.
4. Name the controls Name, Role and Panel colour where appropriate.
5. Inspect the exposed controls before placing instances.

1. Create a parent comp and place the source twice with enough time to inspect each.
2. Set distinct exposed Name values on the two instances.
3. Enter the shared source and change a property neither instance overrides.
4. Return to the parent and inspect both: shared change should reach both, names should stay distinct.
5. Revert one name override and confirm it follows the source.
6. Save/reopen and inspect again.

1. Open the project yourself and connect the supported client.
2. Ask the agent to identify both instances and shared controls without editing.
3. Ask it to change only one exposed Role, then stop.
4. Inspect both instances to confirm the other was preserved.

Read the current project and identify the two lower-third instances. Do not edit yet. Explain which controls are shared and which are instance overrides.

Change wording by hand. Require the agent to reread and report that change before editing another property. It must preserve the newer wording rather than replay cached state. Ask it to stop after the next bounded revision.

Expected: the same visually editable project throughout, with clear source/instance scope and observed takeover.

Save/reopen a test copy and inspect source, overrides and animation. Export/send only after reviewing method, range and destination. After an uncertain edit/send, inspect before retrying. A website illustration cannot validate the exercise.