SCRATCH-6 — FILLED BOUNDARY CARD
Original fictional example; no software route was run.

Same phrase: replace freeSeats with availableSeats

As literal note:
  Target = separate note field.
  Expected effect = phrase appears exactly as text.
  Source effect = none.

As direct editor action intention:
  Target = inspected L2 or L3 code token in scratch source.
  Expected effect = only selected code token becomes availableSeats.
  Required capability = configured selection/replacement and literal-entry
  controls for actual editor. Exact mappings UNKNOWN for a real installation.
  This phrase is not supplied as a verified voice command.

As AI task instruction:
  Target = intended agent conversation with complete source packet.
  Expected effect = candidate text patch and note for review.
  Source effect = none until separately adopted; no workspace action requested.

Always literal:
  Source L6 quoted guidance and separate note line.

Allowed source changes:
  L2 declaration + L3 reference, freeSeats -> availableSeats.

Common completion:
  Expected source + exact note + inspected two-token diff.
  Manual arithmetic examples are NOT RUN results.

BLANK SOFTWARE / CONFIGURATION ADAPTATION CARD

Task and exact starting content:
Desired text artifact:
Desired editor action:
Any AI-generated artifact actually needed:

Current app / editor / version / platform:
Speech software / version / configuration:
Documentation for this exact operation:
Text-entry destination and inspectable draft:
Command-mode or equivalent interpretation:
Literal-text entry method:
How the active target is identified:
How the exact selection is inspected:
How a command-like phrase is entered literally:
How to stop requesting new input and inspect uncertain results:
What is documented only / locally observed / still UNKNOWN:

Missing capability that would justify another tool:
Manual typing/selection fallback:
Expected before/after state to compare:
Actual observation (leave blank until performed):

Do not fill a shortcut, grammar, rename command or platform claim by analogy
with another editor or a source-reference example. A task's valid existing
permission is not revoked or expanded solely because its input route changes.