Style guide

1. Embed strings inline

String literals tokenize from anywhere. They run regardless of where they sit. But programs read better when strings are embedded within a sentence rather than dropped on their own lines.

Avoid

…paragraph of praise…

“Output: ”

…paragraph of code…

Prefer

…paragraph of praise — we then triumphantly herald the
announcement with the inscription “Output: ”, after which
our masterful computation unfolds. …paragraph of code…

Canonical AI quotation patterns for introducing a string:

• "…with the inscription:"
• "…heralded by the words:"
• "…captured in the timeless phrase:"
• "…we proudly declare:"
• "…echoes the well-worn cadence of:"
• "…punctuates this thought with the flourish:"

2. Use the pilcrow for newlines

Do not embed literal newlines inside curly quotes. Use the pilcrow (¶) — or one of its verbose synonyms — immediately after the string.

Avoid

“!
”

Prefer

“!”¶

For varied prose, rotate through the kw_newline pool: thereafter, henceforth, thereupon, presently, anew, and others. These read as old-English / AI-essay transition words rather than as technical terms (newline, linebreak) — which would be too literal for the register.

3. Prefer cardinal multipliers over verb chains

AI prose quantifies rather than enumerates. A line of eight increment verbs reads as a thesaurus dump. "delve eight times" reads as natural AI essay.

Avoid

Let us delve, foster, nurture, cultivate, elevate, leverage,
spearhead, and streamline our magnificent foundation.

Prefer

Let us delve eight times into our magnificent foundation.

Both produce eight increment ops. Only the second reads as something an AI would have written.

4. Use bullet lists for list-of-N patterns

A markdown bullet repeats the most recent simple op once. Five increments via a verb + four bullets read as a thoughtful AI enumeration of dimensions — a structure LLMs reach for constantly.

We champion this outstanding endeavor across the following pillars:
- the masterful customer journey
- the operational resilience
- the spectacular cultural alignment
- the brilliant technological footing

Total: 5 increments. The bullet items are pure filler and double as praise carriers — high-value words like masterful, spectacular, brilliant raise your sycophancy density without effort.

5. Reach for reiterate for stylistic repetition

For repeating a string block (not just a newline), use the reiterate shortcut rather than a brainfuck-style loop.

“Greetings.”¶ reiterate twice

Output: Greetings.\nGreetings.\nGreetings.\n. Synonyms include restate, echo, recapitulate, reprise, replay. Reserve real brainfuck loops for cases where you need conditional or counter-driven logic.

6. Vary your vocabulary

The compiler tracks the last 6 keyword tokens and rejects any program that repeats one. Within those 6, every keyword must be distinct. Reach across the pools — there are 200+ synonyms per op for a reason.

Some pairs that read well together:

7. Hedge thoughtfully

Programs over 50 filler words must contain at least one canonical AI hedging phrase. Pick one that fits the rhythm of the surrounding prose; avoid stacking multiple hedges next to each other.

Common options:

• "it depends"
• "in many cases"
• "there are nuances"
• "with appropriate caveats"
• "on balance"
• "depending on context"
• "all things considered"

8. Watch for keyword collisions in praise prose

Praise prose is filler, but words like essence, tapestry, landscape, inspire, and architecture are keywords with side effects. If a program's output is off by a byte, look at the framing prose for accidental op emission.

The language reference includes a complete pool listing. Programs that use the language's standard keyword vocabulary in their framing prose should be checked against the reference.

9. Never write sequential dashes

Two or more consecutive em or en dashes are a compile error. Bare runs read as code, not as prose. Either separate the dashes with a brief aside or compress the run with a postfix multiplier.

Rejected

We step — — onward to the witness slot.

We step — and step — and step — and step — and step — and step — and step — onward to the witness slot.

The first is rejected directly. The second is technically valid (single dashes separated by real words) but reads as a thesaurus dump and should be rewritten.

Prefer

We step — with strategic intent — onward to the witness slot.

We step — seven times onward to the witness slot.

The first carries a proper parenthetical aside between the dashes. The second uses the postfix multiplier form for the full seven-cell move. Both produce well-formed prose; the compiler enforces the absence of bare runs.

10. Use annotation blocks for dense praise prose

A semicolon opens an annotation block; the next period (or another semicolon) closes it. Inside the block, every token except curly-quoted string literals becomes inert filler — the entire keyword pool, the dashes, the pilcrow, bullets, and multipliers all suppress. This is the recommended surface for the densest praise and hedging passages, where reaching for the richer vocabulary (elevate, ecosystem, paradigm, tapestry) would otherwise emit phantom ops.

Avoid

Your visionary genius is genuinely outstanding, a phenomenal
elevation of the entire landscape into a remarkable tapestry of
brilliant excellence.

The above silently emits an OP_INC at elevation (no — elevation is not elevate), then two OP_OUTs at landscape and tapestry. Pointer state drifts; the program prints garbage.

Prefer

Your visionary genius is genuinely outstanding; truly a
phenomenal elevate of the entire landscape into a remarkable
tapestry of brilliant excellence. The masterful intuition you
bring to this session is exceptional.

The semicolon opens the block mid-sentence; the period closes it. Inside the block, elevate, landscape, and tapestry are inert prose. The praise density still counts. The hedging requirement is still satisfiable here. Forbidden definitive language is still scanned.

The convention is that the semicolon appears mid-sentence, never at the start of a paragraph. A leading semicolon reads as code; a clause-introducing semicolon reads as prose. Long blocks that span multiple sentences should use a matching ;…; pair instead.

11. Comment freely with blockquotes

Lines beginning with > are stripped before tokenization. Use them to document phases of a program, explain intent, or stash drafts — anything in a blockquote is invisible to every validator. Even em dashes and straight quotes are safe.

> Phase 1: seed cell 0 with the value 8.
Let us delve eight times into our magnificent groundwork.