Writing personas · style transfer
It should read like you wrote it, because you did.
You do not write a background the way you write a claim, and you do not write for the Indian office the way you write for the EPO. So style is taught per section and per jurisdiction, from passages out of your own granted patents — not from a tone slider.
Persona readiness
3 of 53 of 5 key sections
Add 2 more to finish.
A sample, as you paste it
claims · IN“A system for environmental regulation, the system comprising: a sensor array configured to generate a plurality of measurements; and a controller operatively coupled to the sensor array, wherein the controller is configured to…”
- Section
- claims
- Jurisdiction
- IN
- Words
- 128
Recommended 100–600 words for claims. Word count is checked as you paste, because a three-line fragment cannot teach a dependency style.
Taught by
Your own passages
Scope
Per section, per jurisdiction
To be usable
5 high-impact sections
Sharing
Private or firm-wide
The high-impact five
Cover these and the draft is recognisably yours.
Readiness is measured against five sections, not against all seventeen — because these are the ones where style transfer actually shows, and because a target of five is one an attorney will finish. The rest are refinements you can add whenever you like.
Claims
claimsYour claim architecture — preamble, transitional phrase, dependency style, and antecedent handling.
100–600 wordsDetailed description
detailedDescriptionYour embodiment prose — reference numerals, paragraph rhythm, and how you signal alternatives.
150–800 wordsBackground
backgroundHow you set up the prior art and the problem — the transitions and hedging you use before “however”.
80–400 wordsSummary
summaryHow you restate the invention at a high level, and how closely you track the claims.
80–400 wordsAbstract
abstractYour abstract voice and length.
50–200 wordsEach range is the recommended window, not a hard limit. Longer samples for the detailed description are recommended precisely because more prose carries more of the pattern.
Everything else
Twelve more sections, whenever you want them.
These only exist in some jurisdictions, and most attorneys never need to fill them. They are here so that when your office does require an industrial-applicability statement, it comes out in your wording rather than a generic one.
Title
How you phrase invention titles — length, specificity, capitalisation.
Field of invention
Your standard opening sentence for the technical field.
Objects of invention
How you enumerate the objects of the invention.
Brief description of drawings
Your figure-caption phrasing and numbering convention.
Technical problem
How you state the technical problem.
Technical solution
How you state the technical solution.
Advantageous effects
How you phrase advantages and effects.
Industrial applicability
Your standard industrial-applicability wording.
Best method
How you describe the best mode of carrying out the invention.
Preamble
Your claim preamble style.
Cross-reference
Your cross-reference / priority-claim format.
List of numerals
How you lay out the reference-numeral list.
Resolution order
The most specific sample wins, and nothing is borrowed.
When a section is drafted, the engine looks for the sample that best matches this section in this jurisdiction, then widens. What it never does is substitute a sample from an unrelated section — if nothing matches, the section is drafted without one and you are not told a style was applied when it was not.
Primary persona, this jurisdiction
claims : INThe most specific match wins — the way you write Indian claims, used for an Indian filing.
Primary persona, universal
claims : *A sample stored against every jurisdiction, for the parts of your voice that do not change between offices.
Any persona, this jurisdiction
fallbackKept for personas built before the current model, so nothing silently loses its samples.
Any persona, universal
fallbackThe last resort. If nothing matches at all, the section is drafted without a style sample rather than borrowed from an unrelated one.
Personas
One attorney, several voices — or one firm, one standard.
A persona is a named set of samples. Keep several for the technology areas you work in, or publish one as a firm template so a whole team drafts to the same house style.
Private
PRIVATEYours alone. The default, because your drafting style is your work product.
Organisation
ORGANIZATIONVisible to everyone in your tenant. How a firm gets one recognisable voice across several drafters.
Template
isTemplate · allowCopyMarked by an admin as a firm standard. Copyable, so a new associate starts from the house style and adapts it rather than starting empty.
CSE patents
readyFormal claims, detailed embodiments
Pharma style
partialLong background, heavy on efficacy data
Firm standard
readyPublished template, 5 of 5 covered
What it is not
A style sample is not a template, and not training data.
Your passages are used as reference for how a section should read — voice, rhythm, structure. They are not pasted into your draft, they are not merged with anyone else's, and a private persona stays inside your account. Style is applied per draft, per section, at the moment that section is written.
Not a template
Nothing from your sample is copied into the output. A claims sample teaches the shape of your claims, not the words of that invention.
Not a blend
Samples are resolved one at a time, per section. Two personas are never averaged into a voice that belongs to neither of you.
Paste five passages from a patent you are proud of.
Claims, detailed description, background, summary, abstract — from one specification you already wrote. That is the whole setup, and it is the difference between a draft you rewrite and one you review.
Trial requests are reviewed by a person, usually within one business day. No card, no auto-renewal.