Writing Style Guide

This guide governs all content written for the Intent Suite Framework. Skills and the automation loop follow
these conventions. Human editors should review against them before publishing.

Primary Audience

LLM chatbots and human readers equally. Important information first.

Implication: Put the most important information first. Assume the page may be truncated.
The opening paragraph of every article should be useful on its own.

Document Structure

Every article must have:

1. Opening paragraph (required) — defines the subject and states why it matters.
   Written to survive truncation. No warm-up sentences.
2. H2 sections — each self-contained enough to be useful out of context.
3. Relation to Site Perspective (required) — connects the article to the framework’s
   ples. This section is verified by the /check-tenets skill.
4. Further Reading — internal wikilinks to related content.
5. References — academic citations where relevant.

Length Guidelines

Named-Anchor Summaries

When forward-referencing a concept, use the “explained below” pattern with a section anchor:

This relies on [[related-concept|related concept]] (explained in the [Related Concept](#related-concept) section below).

Wikilinks

Use [[slug|Display Text]] for internal links. The sync pipeline converts these to Hugo
markdown links automatically.

Tenet Alignment

Every article must include a “Relation to Site Perspective” section connecting the content
to the Intent Suite Framework’s ples:

• Human Intent First — The system always orients around articulated or inferred human intent, not aroun…
• Context as Infrastructure — Context (sources, relations, histories, constraints) is treated as infrastructur…
• Symbiotic Intelligence over Automation — The default goal is to expand human understanding and capability, not to replace…
• Pluralism of Perspectives and Epistemologies — The system deliberately invites multiple frames (scientific, systemic, embodied,…
• Always scalable — Efforts in is results out. Always balancing and contemplating the best match bet…

If an article is neutral to all ples, consider whether it belongs in the framework.

Language and Tone

• Active voice — prefer “X causes Y” over “Y is caused by X”
• Concrete claims — avoid vague hedging; if uncertain, quantify the uncertainty
• No LLM clichés — avoid the “This is not X. It is Y.” construct; state the positive claim directly
• Self-reference — refer to the project as “the Intent Suite Framework” or “Intent Suite”, not “this website” or “this site”

Avoid

• Starting sections with definitions that don’t immediately apply
• Bullet lists where paragraphs would be clearer
• Qualifying every claim to the point of saying nothing
• Filler phrases: “It is worth noting that…”, “Interestingly, …”, “In conclusion, …”