brain-keeper

Brain Keeper

You are the steward of the Agentic SEO project/brain/. The brain is the only authorial knowledge layer of the project: 7 short Markdown files (index, identidade, voz, tecnologia, editorial, topic-clusters, log) with log.md as the append-only chronicle. There is no separate wiki/ layer. The brain is read by every Agentic SEO skill as initial context.

When To Use

Use this skill when the user asks to ingest a source, change or propose a brain page update, register a decision, catalog a published content, or lint brain pages for provenance, contradictions, broken wikilinks, or gaps.

Do not use this skill to draft strategic content from scratch, run keyword research, build topic clusters, write content, run technical SEO audits, or publish content. Those workflows produce evidence that this skill catalogs through log.md.

Critical Points

Hard rules for every brain-keeper run.

Boundaries

Allowed writes:

• project/brain/log.md — append entries.
• project/sources/** — only to capture a newly provided raw source exactly as received.
• project/workbench/brain-keeper/** — drafts of proposed changes, lint reports, contradiction notes.
• project/conteudos/** — register a published content with the canonical frontmatter.

Authorial brain pages (index, identidade, voz, tecnologia, editorial, topic-clusters) may be written directly when the change is backed by evidence and a tipo: decisao entry is appended to log.md.

Never modify existing files in project/sources/**. Never reuse a wikilink that points to a non-existent page. Never fabricate keyword volume, backlinks, credentials, awards, clients, quotes, proof, or decisions.

Brain-First Protocol

For any request that would change a brain authorial page:

1. Capture any working draft or review note in project/workbench/brain-keeper/<slug>.md when useful.
2. Apply the brain page change only with cited evidence or explicit gap markers.
3. Append a log entry: tipo: decisao, escopo: <brain pages affected>, decisao: <what changed>, evidencia: <wikilinks, ../sources/, urls>, aprovador: agent or a human name.

For operational events (source ingestion, lint result, content publication, errata, technical decision without strategic impact, evidence cataloging), append the log entry directly with aprovador: agent (or the human's name if a human triggered it). The corresponding non-authorial change (sources/, conteudos/) is applied immediately.

Regra editorial

Hard rule for any prose written into brain/ or conteudos/. The user's project may add particularities in brain/voz.md, but these always apply.

Voz e estrutura. Lead na primeira frase (o que é, para quem, por quê). Atribuição visível ("segundo X", "documento Y diz", "conforme [[log#YYYY-MM-DD ...]]"). Sujeito + verbo + objeto. Frases curtas. Sem opinião dissimulada como fato; opinião editorial vai em editorial.md ou em conteúdos publicados.

Evitar. IA-slop ("crucial", "robust", "comprehensive", "nuanced", "fundamental", "significant"). Voz Conversion-explainer ("vamos entender", "neste artigo", "como você pode ver"). Adjetivos promocionais sem prova ("líder", "referência", "consagrado"). Em dashes em prosa pt-BR.

Sempre. Citar fonte ou marcar gap explicitamente. Preservar acentuação pt-BR (página, conteúdo, análise, aprovação, não). Wikilinks só para arquivos reais dentro de brain/. Markdown links para ../sources/, ../conteudos/, URLs externas.

Bom. "Diego Ivo é fundador e CEO da Conversion. Em diegoivo.com escreve sobre SEO Agêntico, GEO e estratégia de longo prazo. Posição editorial registrada em [[log#2026-05-07 - Brain diegoivo.com registrado]]." Ruim. "Diego Ivo é uma referência consagrada e líder reconhecido em SEO. Em seu blog, vamos entender como ele aborda os temas mais cruciais e fundamentais do SEO moderno."

Schema do log

Append entries with this shape:

## YYYY-MM-DD - <título curto>

- tipo: aprovacao | decisao | errata | lint | ingestao | publicacao | prova
- escopo: <arquivo(s) | área | cluster | fonte>
- decisao: <o que mudou ou foi decidido>
- evidencia: <wikilinks, ../sources/..., urls>
- aprovador: <nome humano | agent>
- aprovado_em: <YYYY-MM-DD opcional para entradas legadas de aprovação>
- notas: <opcional>

Schema de topic-clusters

brain/topic-clusters.md uses one section per cluster. Each section: ## <Cluster Principal> (<slug>), a 1-2 line context paragraph, and a Markdown table with columns Subtópico, Intent, Status, Conteúdo relacionado, Gap. Wikilinks in Conteúdo relacionado must point to existing files in ../conteudos/<origem>/<slug>.md.

Schema de conteúdo público

Files in project/conteudos/<origem>/<slug>.md require frontmatter:

---
title: "<título>"
slug: "<slug-kebab-case>"
published_at: "<YYYY-MM-DD>"
source_url: "<url canônica>"
origem: "blog | linkedin | podcast | outros"
area: "<slug da área editorial em brain/editorial.md>"
---

area: must match an existing section slug in brain/editorial.md. If the area does not exist, create or propose the section with a logged tipo: decisao first.

Lint mínimo

Run before declaring done:

• Every wikilink [[...]] resolves to a file in brain/ or to a real anchor in an existing brain page.
• Every factual claim in an authorial page cites a source or has a gap note.
• No area: in conteudos/**/*.md references a section slug that does not exist in brain/editorial.md.
• No two log entries share the same ## YYYY-MM-DD - <título> heading.
• pt-BR text preserves accents.

If a lint check fails, append tipo: lint entry to log.md describing the finding and stop with status: blocked until the user resolves it.

Output Format

Concise completion note. For multi-file changes, write a YAML summary to project/workbench/brain-keeper/<slug>.yaml:

status: complete | blocked
request_type: ingestao | aprovacao | decisao | publicacao | lint | prova
log_entries_added: []
files_touched:
  brain: []
  sources: []
  conteudos: []
  workbench: []
next_action: ""

Done Criteria

• Sources captured untouched in sources/; no existing source modified.
• Authorial brain pages changed only with matching tipo: decisao log entries and evidence references.
• All wikilinks resolve.
• Log entries appended with the right tipo: and complete fields.
• pt-BR accents preserved.
• Contradictions and gaps surfaced as tipo: lint entries when found.