Writability Rules + Substitution Tables

These examples and illustrative results are independently authored teaching materials, not measured model results.

Use case

An internal status update allows prose edits but protects API names, numbers, owners and quotations. Teaching text says “We will utilize CheckoutAPI v2 and commence a12-account pilot on Friday.” It needs explicit writable regions and a replacement table.

Mechanism

List editable and protected regions first. Build a domain-appropriate table, such as utilize→use and commence→start; a Chinese example replaces a nominalized investigation phrase with “we investigated.” Apply entries contextually rather than globally inside identifiers, quotes or exact terms. Compare facts, modality and names afterward; preserve ambiguous terminology with a note.

Bad example

Make the whole update more professional and replace every occurrence. Adjust API names, timing and numbers for fluency too.

Good example

Edit narrative wording only; protect CheckoutAPI v2, Friday,12 accounts and exact quotations. Replace ordinary utilize with use and commence with start: “We will start a12-account pilot on Friday using CheckoutAPI v2.” Check meaning after each edit and do not turn a plan into completed work.

Why the change matters

Writability rules define scope, while the table supplies repeatable concrete edits. Context checks protect terms and facts so style changes cannot silently change content.

Observable expectation

The teaching revision retains v2, Friday,12 accounts and future intent. Preserve utilize if it occurs in an API field name. Compare protected spans and manually check planned versus completed meaning; an inapplicable table entry may remain unchanged.

Limits

This entry has no confirmed frozen source; examples are independent teaching constructions. A table is not a universal dictionary or sentence-length rule. Domain terms and legal quotations may require exact preservation. With uncertain writability, propose edits before changing protected content.