Creating a voice
for a website

The problem

eidosagi.com had a distinct voice — direct, first-person, slightly provocative, builder-confident. Lines like:

"We don't build LLMs. We build the governance, decisions, and execution standards that make them trustworthy enough to hand real work."

"Trust us because you read the source, not because we asked nicely."

Two new pages (/consciousness and /constraints) were written by a different agent in a different session. Well-argued but wrong register — explanatory, defensive, academic. The founder noticed immediately.

The approach

An agent (PAL, using Gemini 2.5 Pro in high-thinking mode) was given all 5 page source files and asked for a brutal audit. No hedging, no politeness. Call out specific bad lines by quoting them.

The agent returned four deliverables:

1. A precise characterization of the authentic voice — sentence structure, word choice, rhetorical moves, reader assumptions
2. Specific lines from the new pages that read as "AI slop" — with explanations of why
3. A line-by-line comparison between old pages (which had the voice) and new ones (which didn't)
4. 6 concrete voice rules any writer (human or AI) could follow

The evidence

The authentic voice

The audit identified the voice as an opinionated, pragmatic builder:

• Staccato and declarative. Short sentences. Fragments for emphasis. "The models worked. The agents ran. So we built one."
• Concrete, blunt word choice. Strong verbs: enforce, govern, earn, commit. No Latinate business-speak.
• Assertive contracts. Frames principles as rules of the system, not suggestions.
• Show, don't tell. Code blocks, pip commands, and diagrams as proof.
• Assumes the reader is smart. Never defines "governance" or "agent."

Where the new pages deviated

• Explaining instead of declaring. The authentic voice states and moves on. The new pages justified, preempted objections, restated.
• Defensive phrasing. "This is not bureaucracy," "This is not fabricated competition" — the authentic voice is too confident for that.
• External authority. The authentic voice IS the authority. The new pages appealed to biology and philosophy to justify claims.

The 6 rules

1. Start with the tool, not the theory.
2. State it once, forcefully. Trust the reader. Cut ruthlessly.
3. Name your concepts. Naming makes it architecture.
4. Assertive claims, not defensive explanations. Never write "This is not X."
5. Show, don't just tell. Code blocks, configs, diagrams.
6. Analogies from systems, not nature — for tools pages. Philosophy pages can use biology when it IS the thesis.

The result

Both pages were rewritten. The consciousness page went from ~95 lines to ~65 — same ideas, no repetition, no defensive lines. The constraints page renamed its core concept from "competition" to "earned-seat accountability" after the founder pointed out fabricated competition is a lie.

The founder added a key nuance: tools pages and philosophy pages are different registers. Tools pages are the engineer at the whiteboard. Philosophy pages are the founder at dinner after the conference. Both are direct and confident, but philosophy pages earn the right to be longer and more exploratory.

Both pages now open with a philosophy banner that sets this expectation:

"This is AGI philosophy — the thinking behind the product, not the product itself. It's longer than our tools pages because it's meant to teach, not to sell."

The voice rules are now the canonical reference for any future page on the site — human-written or agent-written.