Bastien Chanot 8b0c98c99a fix(geo): I3 — port NAP direction rule (LRN-032) into geo-analyzer spec ...

geo-analyzer owns JSON-LD NAP (ownership matrix, seo/SKILL.md:261) and can
rewrite it via G2 — AUTO tier, no confirmation (geo-analyzer.md:660). The
LRN-032 protection lived ONLY in the /seo dispatcher prompt
(seo/SKILL.md:339-343), so standalone /geo reconciled NAP with no canonical
and no anti-seed guard — the exact zenquality trap, writing into client
structured data.

Root cause: a safety invariant that depended on the caller. Fixed at the
layer that owns the data.

- Data integrity: NAP direction rule, caller-independent, binds G2/G6.
  Covers CREATE (LocalBusiness from scratch) not just rewrite — geo builds
  missing schemas, seo-analyzer's wording only covered rewrite.
- STEP 6 checklist: pointer at the line that triggers the action.

Absent canonical is already the safe default (no directional fix), so no
NAP collection step is needed in /geo — that would duplicate seo/SKILL.md
STEP 0 and risk drift.

Verified: make test 25+5+5 GREEN / 0 RED (incl. G3 strict-YAML frontmatter).

2026-07-16 16:06:30 +02:00

..

audits

darwin: Phase 3 report — bottom-5 round 1, avg 58.0 → 78.2

2026-05-12 18:01:42 +02:00

memory

chore(memory): BDR-069 + LRN-130 + EVAL-024 — deny-list design pass

2026-07-16 15:02:00 +02:00

tasks

fix(geo): I3 — port NAP direction rule (LRN-032) into geo-analyzer spec

2026-07-16 16:06:30 +02:00

settings.json

chore(graphify): rewrite CLAUDE.md + hook to prefer graphify query over GRAPH_REPORT.md

2026-05-21 05:55:13 +02:00