Registers and modes
Two settings on every rewrite. The register says where the writing is going. The mode says what to do with the input.
Registers
| Value | Label | For |
|---|---|---|
slack | Slack | Messages to a channel or a person. Short, direct, no throat-clearing. |
email | The default. A person is going to read this in an inbox. | |
skip_level | Skip-level / charter | Writing that goes up, or a document that has to stand on its own. Longer sentences are allowed. |
linkedin | A post. The register where machine-shaped prose is most common and most obvious. |
The register is not a formality dial. It changes which checks fire and at what threshold — em dash density, sentence-length variance, how short is too short. A construction that is a tell in Slack can be ordinary in a charter, and the report reflects that.
register is required on every API call.
Modes
| Value | In the app | What it does |
|---|---|---|
rewrite | (default) | Rewrite the draft. Keep every fact. |
expand | Expand toggle | Turn notes into prose. Pro only. |
vary | Try another | Another rewrite, meaningfully different in shape from the last. |
closer | Closer to original | Stay nearer the draft's wording and order. |
vary and closer need previousRewrite in the request. That text is named as
something to differ from or stay near — never as a source of facts. A claim that
appears only in previousRewrite and not in text should not appear in the
result.
Picking between them
- First pass:
rewrite. - The substance is right and the shape is wrong:
vary. - You already liked the draft and just want the tells gone:
closer. - You have bullets, not prose:
expand.
Running vary repeatedly is not a search for a better answer. Two or three is
the useful range; past that you are shuffling.