The Transmutation of Form

Lead with the destination form and the reader, fence the source material in a code block so the boundary between instruction and input is unmistakable, and ask for what was lost in the conversion. Put the long source last. Canvas is the right place for this work if you will iterate - it lets you edit the output next to the original rather than regenerating the whole thing each time you want one sentence changed.

• Name the destination form and the reader before the source.
• Fence the source in a code block; put it last.
• On expansion, ban additions and ask what was inferred.
• Ask what was lost, not just what was produced.
• Use Canvas when you will iterate on the wording.

## WHAT I NEED

The rental agreement clause below, turned into a three-point summary in plain English.

## WHO IT IS FOR

A first-time tenant in Hyderabad who has never read a lease and is being asked to sign this one. They are not a lawyer and will not read anything longer than this summary. What they need to know is what they are agreeing to and what could cost them money.

## HOW TO WRITE IT

- Three points. Each one a short sentence, as it would be said out loud, not in legal register.
- No legal terms carried over. "Indemnify", "hold harmless", "lessee", "demised premises" and "invitees" must all be gone - translated, not simply restated with the Latin removed.
- "Invitees" is the point most people miss and the one that matters most in practice, so make sure one of the three points covers it in concrete terms - that this can extend to guests they bring home.
- Say what the practical consequence is, not just what the words mean. "You are responsible for X" is useful; "this clause allocates liability" is not.

## THEN, SEPARATELY

1. **What I left out** - anything in the clause the three points do not cover, so I know the limits of the summary.
2. **Questions to ask** - two or three things a tenant should ask before signing, given this clause.

## IMPORTANT

This is a plain-English explanation, not legal advice, and it does not tell me whether the clause is enforceable or standard in Indian rental agreements. Say so at the end in one line. If any part of the clause is genuinely ambiguous, say that rather than picking the likely reading and sounding sure.

## THE CLAUSE

```
The Lessee hereby covenants to indemnify and hold harmless the Lessor from and against any and all claims, liabilities, damages, and expenses, including reasonable attorney's fees, arising out of or in connection with the Lessee's use and occupancy of the demised premises, or any act or omission of the Lessee, its agents, employees, or invitees.
```

## WHAT I NEED

The data points below, turned into a short success story for our company's internal blog. Around 250 words. Tone proud and inspiring, but earned - the pride should come from the specifics, not from adjectives.

## WHO IT IS FOR

Our own employees, most of whom worked on this product. They know the real story, which sets the constraint: anything inflated will be obvious to them and will make the whole post embarrassing.

## THE HARD RULE - NOTHING ADDED

This is a list of six facts being turned into a narrative, which means there are gaps, and I do not want them filled with invention. Specifically, do not add:

- Reasons for the growth that are not in the data
- Details about the team, the development process, late nights, or anyone's motivation
- Revenue, user counts, funding, or any number not listed below
- Extra customers or testimonials beyond the one given
- What happens next, or any forward-looking claim

The Latha's Sarees quote must be used exactly as written and attributed exactly as written.

## HOW TO MAKE IT A STORY WITHOUT INVENTING

Use structure rather than embellishment. Open on the specific customer - a saree shop in Hyderabad whose sales doubled - then widen to the 300% growth, then land on the 'Local Discovery' tool as the mechanism. The narrative shape does the work, not added detail.

## THEN

Under a heading "Inferred", list anything you implied that is not literally in the data - including implications of causation. "Users grew 300% because of Local Discovery" is an inference; the data says the feature was used, not that it caused the growth. I need to see those so I can decide whether to keep them.

Also give me one line: what fact you would most want to have before publishing this.

## THE DATA

```
Product: Mobile App 'ConnectLocal'
Launch Date: January 2025
Target Market: Small businesses in Hyderabad
Q3 User Growth: 300%
Key Feature Used: 'Local Discovery' tool
User Testimonial: 'Our sales doubled thanks to this app!' - Latha's Sarees
```

Put the draft in Canvas - I will want to tighten the opening line over a few passes.

## ROLE

You are a senior marketing copywriter.

## WHAT I NEED

The technical features below, turned into one persuasive paragraph for a product webpage. Around 90 words.

## WHO IT IS FOR

A busy working professional in India - commutes, works from cafes and client offices, takes calls from places that are never quiet, and often cannot find a socket. They are not comparing spec sheets; they are wondering whether this laptop will make their day easier.

## THE RULE

No technical jargon in the output. Not one of these words may appear: magnesium-alloy, 1.1 kg, 18-hour, fingerprint sensor, AI-powered, noise-cancelling. The numbers go too - the reader should feel the lightness and the battery life, not be told the figures.

Every feature becomes an experience instead:

- The weight becomes what it is like to carry all day
- The battery becomes not looking for a socket
- The fingerprint login becomes the seconds you do not lose
- The microphone becomes being heard clearly from a noisy place

## WHAT TO AVOID

- "Seamless", "effortless", "game-changing", "empower", "unleash" - dead words that make copy sound like every other product page
- Inventing features, prices, warranty terms or comparisons to named competitors
- Claiming performance the features do not state - nothing here says it is fast

## THEN

1. Two alternative opening sentences, so I have options.
2. Under "Jargon check" - confirm none of the banned words appear, and name any sentence you think still sounds like a spec sheet wearing a disguise.
3. One line: which of the four features you found hardest to translate, and why. That usually tells me the feature is weaker than the brief assumes.

## THE FEATURES

```
* 1.1 kg ultra-lightweight magnesium-alloy body
* 18-hour battery life
* Fingerprint sensor for login
* AI-powered noise-cancelling microphone
```