DUNIN7 · LOOMWORKS · RECORD
record.dunin7.com
Status Current
Path scoping-notes/loomworks-ogilvy-writing-audit-seed-voice-scoping-note-v0_2.md

Ogilvy Writing Audit — Seed-Voice Scoping Note

Version. 0.2 Date. 2026-06-05 Status. Scoping note for v0.2 of the ogilvy-writing-audit skill. Not an implementation. Leads with orientation.


Plain-language summary

The ogilvy-writing-audit skill (v0.1, built and packaged) checks business writing against David Ogilvy's ten rules. v0.1 judges voice against a generic standard — natural, spoken cadence. Inside a Loomworks engagement that is the wrong standard, because the engagement has declared a voice in its seed (R-A7), and the right standard is the declared voice, not generic naturalness.

This note scopes v0.2: make the voice audit seed-aware. The change is surgical — only the voice rule and part of the clear-ask rule become seed-aware; the rest of the audit stays universal. The hard part is that seed voice is per-consumer (a board briefing and a regulatory submission have different declared voices in the same engagement), so the audit must first establish which consumer the piece is for.

Decision needed from the Operator: confirm the four defaulted decisions in §6, or amend. Then it can go to a CR-drafting session.

In scope: seed-aware voice audit (rule 2), seed-aware ask audit (rule 9), seed-aware jargon caveat (rule 4 terms-of-art). Out of scope: fetching the seed (Claude.ai can't reach the record), changing rules 3/5/6, any rewrite capability.


1. Where v0.1 sits

v0.1 audits six observable rules (2, 3, 4, 5, 6, 9) and surfaces four process rules (1, 7, 8, 10) as prompts. It produces a severity-sorted diagnostic. It does not rewrite.

On voice specifically, v0.1 rule 2 ("write the way you talk") rewards natural, spoken cadence and flags stiff, written-not-spoken phrasing. This is correct for generic business writing.

2. The correction this note makes

Prior position (v0.1): voice is a single quality — conversational good, stiff bad.

Corrected position (v0.2): voice is declared and per-consumer. The seed's R-A7 names the posture the work takes toward each consumer, and that posture varies by consumer within one engagement.

Evidence from a live seed (geology engagement, v0.3, R-A7): > "Evidence-based and descriptive for technical consumers. Advisory for the board. Declarative for regulatory submissions."

Three consumers, three declared voices, one engagement. A board briefing written in a conversational-casual register is wrong against this seed even though v0.1 would praise its naturalness. v0.1's generic standard actively misfires inside an engagement that has declared a non-conversational voice for the relevant consumer.

This is the crystallisation: the audit gains a question it did not have — who is this piece for? — because the answer selects which declared voice to judge against.

3. What becomes seed-aware, and what does not

Surgical scope. Only where declared voice legitimately changes the judgement.

| Rule | Seed-aware in v0.2? | Why | |------|---------------------|-----| | 2 — Write like you talk | Yes | The declared voice replaces the generic naturalness standard. "Advisory for the board" means measured advisory phrasing is correct, not stiff. | | 9 — Clear ask | Partly | An action-directing voice should have a clear ask. A neutral/descriptive voice may legitimately have none. The seed tells the skill whether a missing ask is a defect or correct. | | 4 — No jargon | Caveat sharpened | Terms of art are not jargon when the reader shares them. The seed's R-A6 (consumers) + R-A7 (voice) tell the skill which reader shares which vocabulary. "Evidence-based for technical consumers" means domain terms are expected, not violations. | | 3 — Short sentences | No | Concision is good regardless of declared voice. | | 5 — Two-page limit | No | Length discipline is universal; the existing long-form note already handles legitimately long renders. | | 6 — Check quotations | No | Accuracy is universal. |

4. The core mechanism: establishing the target consumer

Because declared voice is per-consumer, the audit must establish which consumer the piece targets before it can pick the right voice to judge against. Two approaches were considered.

Option A — ask the writer. Before auditing, present the seed's R-A6 consumer list and ask which one the piece is for. Clean and unambiguous. Cost: adds a step; assumes the writer can name the consumer.

Option B — infer then confirm. Read the draft, infer the likely consumer from content and register, state the inference, audit against that consumer's declared voice. Faster. Cost: inference can be wrong, and auditing against the wrong voice yields confidently wrong findings.

Recommended default: B, with a stated guess the writer corrects in one word, and a safe fallback. This matches the project's "best-guess default, confirm with a single word" discipline. The safety property: if the skill cannot infer the consumer with reasonable confidence, it does not guess — it falls back to v0.1's generic standard and says so explicitly. Wrong-voice findings are worse than generic findings, so the fallback is the floor, not an error.

5. How the skill gets the seed (the access constraint)

The skill does not fetch the seed. Claude.ai cannot reach record.dunin7.com (behind Cloudflare Access). The skill therefore requires the seed's R-A6 and R-A7 content to be in context — either:

If neither R-A6 nor R-A7 is present in context, the skill degrades to v0.1 generic behaviour and states that it is doing so. It never guesses what the seed says. This preserves the drift-surface discipline: the skill names the source of the voice standard it is applying (declared-from-seed vs generic-fallback) so the judgement is visible and correctable.

6. Four decisions, defaulted

  1. Consumer establishment: Option B (infer, state, confirm in one word), with generic fallback when inference is low-confidence. Default: yes.
  2. Seed access: require R-A6/R-A7 in context; degrade to generic when absent; never fetch, never guess seed content. Default: yes.
  3. Scope of seed-awareness: rules 2, 9 (partly), 4 (caveat) only; rules 3, 5, 6 stay universal. Default: yes.
  4. Report transparency: every voice and ask finding names which standard it used — "judged against the seed's declared voice for [consumer]" or "judged against generic standard (no seed voice in context)." Default: yes.

One word per decision confirms or amends.

7. What v0.2 does NOT change

8. Seed-alignment check

v0.2 brings the skill closer to the seed, not into conflict with it. The seed commits R-A7 voice as governing shaping and rendering across the engagement's lifetime; v0.2 makes the writing audit honour that commitment instead of overriding it with a generic standard. No conflict surfaced. The skill remains additive — a quality lens, not a structural element.

9. Action path

  1. Operator: confirm or amend the four decisions in §6 (one word each).
  2. On confirmation: open a CR-drafting session for ogilvy-writing-audit v0.2. Inputs: this scoping note + the v0.1 SKILL.md and references file.
  3. Build target: v0.2 modifies SKILL.md (voice/ask/jargon sections + a new "establish the target consumer" step) and references/ogilvy-rules.md (rules 2, 4, 9 gain seed-aware subsections). Bump both the package and the rule reference to v0.2.
  4. Land: package as ogilvy-writing-audit-v0_2.skill; place under the user-skills path via CC with halt-before-commit.

Ogilvy Writing Audit — Seed-Voice Scoping Note — v0.2