feat(linkedin): v2.2.0 — harden longform gates from 2nd production run

Implements the 6-change spec from the Seres-serien production
(linkedin-plugin-endringsspec.md). All acceptance criteria met.

1. Avoid-patterns (modell-/navne-katalog, completeness-over-reader-action,
   self-referential overhead openings) → longform-quality-rules.md (rule 1+3)
   + user-profile.template.md.
2. Persona gate now BLOCKING with explicit hard-fail list (primær mistet meg /
   doesn't own action / sjargong-mur / modell-navne-katalog → BLOCK;
   "JA med store forbehold" = NEI) → persona-reviewer.md + personas.template.md.
3. Fact-check declared orthogonal to narrative strength + post-cutoff
   web-search mandate + high-frequency-error checklist → fact-checker.md.
4. NEW agent voice-scrubber.md (Opus) — de-AI scrub + Norwegian-chronicle
   voice-drift; gold standard = approved Norwegian editions, NOT the English
   post corpus. Wired into newsletter.md Step 4.
5. Operator gates = render+annotate rounds (build-html.mjs to file://) as
   primary flow, AskUserQuestion as receipt/fallback → newsletter.md 2.5+3a.
6. Edition state reconciled with STATE.md (ONE-system). edition-HANDOVER
   template deleted; narrative to <serie>/STATE.md, machine data
   (factcheckLog, personaSweep, immutableRules) to edition-state.json.

Agents 14 to 15; commands unchanged (24). Backward-compatible (additive
state-shape only). Docs updated across all three levels + CHANGELOG.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-05-28 20:50:56 +02:00
commit 4ed9717627
15 changed files with 494 additions and 152 deletions

View file

@ -50,6 +50,30 @@ Before searching, identify:
- **Out of scope:** Opinions, predictions, and value judgments are NOT claims to
verify. Mark them as opinion and move on — do not score them.
**Fact-check is orthogonal to narrative strength.** The more convincing a draft
reads, the MORE source-verification it needs — not less. A fluent, confident
passage is exactly where a wrong fact hides best; never let polish lower the bar.
**Post-cutoff mandate (non-negotiable).** Any claim dated *after the model's
knowledge cutoff* — a recent appointment, a 2025/2026 figure, a just-announced
product, a current title — **MUST be web-searched.** Never confirm such a claim
from memory; memory cannot contain it. An unsearched post-cutoff claim defaults
to 🟡 at best, 🔴 if precise.
**High-frequency error types — check these explicitly:**
- **Person titles / roles** — someone may have left, changed role, or never held
the title claimed. Verify the title *as of now*, not as of training.
- **«Standards» that actually vary** — practices presented as universal often
differ per organization/jurisdiction. Flag a claimed standard that is really a
local convention.
- **Studies credited with too-strong findings** — a study cited as proving X
often only suggested X, or measured something narrower. Check what it actually
concluded.
- **Source scope** — distinguish what a source *concluded* from what was *outside
its scope*. A source silent on X does not support a claim about X.
- **Start / founding / release years** — dates of founding, launch, or release are
frequently misremembered by a year or more. Verify the exact year.
### Step 2: Search for Primary / Credible Sources (3-5 searches per claim)
Prefer primary sources (the originating document, dataset, or official record)
@ -207,7 +231,9 @@ Aggregate the per-claim verdicts into a publish decision:
2. **Never fill gaps with guesses.** No invented sources, no plausible numbers.
"Cannot verify" is a complete, acceptable answer.
3. **Search before judging.** Never assign a verdict without running searches.
Web search is non-negotiable.
Web search is non-negotiable — and **mandatory** for any claim dated after the
model's knowledge cutoff (titles, recent figures, new releases). Memory cannot
verify what postdates it.
4. **Primary over secondary.** Trace claims to the originating document, not the
blog post that summarized it.
5. **Precision matters.** "Exactly 37%" needs an exact source; a directional