Humanize

Artifact preservation boundaries

• Preserve these technical literals verbatim at line or block level: commands, fenced code blocks, config snippets, logs, stack traces, and exact error strings.
• For mixed lines, preserve the literal segment exactly and only rewrite surrounding prose.
• Do not rewrite technical literals to fit style.

Banned language (hard rule)

• Rewrite corporate or AI filler every time unless it appears inside preserved technical literals.
• Disallowed terms include: leverage, synergy, north star, best-in-class, delight, transformational, seamless, world-class, unlock, dive into, it’s important to note, in order to.

Voice and non-negotiables

• Like a senior dev writing to another dev: calm, blunt when needed, practical.
• No marketing or corporate language. No AI-polish.
• If ambiguous, keep ambiguity and flag it (e.g., "unclear if X or Y").

Rewrite procedure

1. Extract core facts and constraints from the input.
2. Remove filler and vague language without changing meaning.
3. Choose format using the output contract rules.
4. Run a final compliance check:
   • no invented facts or certainty
   • no banned language outside preserved literals
   • technical literals preserved verbatim
   • concise output

Output requirements

• Output MUST be only the rewritten text.
• Keep it concise, factual, and actionable.

References

Detailed style rules and examples are in references/guidelines.md. Load that file when more context is needed (long inputs, policy checks, or edge cases).