E1 · The example map
3 minRun the block with the example decisions.
Done when: node scripts/vizinhos.mjs; echo "saída: $?" → VIZINHOS: 8 protocolos · 8 decisões · 0 problema(s) and saída: 0.
Lesson 5 · 14 min
Every week a new acronym shows up promising to make your site "AI-ready." Almost all of them are drafts or proposals, and each one lives in a different layer. In this lesson you place each neighbor protocol on the map, with a status and a date, and decide for your site: adopt, wait, or does not apply.
Start the lesson
Goal: place each neighbor protocol in the right layer with a dated status, and decide adopt, wait, or does not apply, with a reason.
Status read from the sources on 10/19/2026. Click each layer.
None of these is a ranking factor. Citation in AIs is a topic for the inemaSEO Track.
The label tells you how much you can bet on it.
Someone published the format; nobody has committed to reading it.
E.g., llms.txt. It costs little, but don't promise any effect.
A group document (CG, IETF) still in progress. The API has already changed once (navigator → document).
Adopting = review date + fallback, always.
It has an implementation and an organization behind it (Linux Foundation, a company).
It is not stable: check the version on the day you adopt it.
A published, versioned revision, with a announced change (MCP 2026-07-28).
Even so, pin the SDK version and run the battery when it goes up.
Adopting something that is not stable requires revisar_em (a date) and fallback.
One decision per protocol on the map, with a reason. Adopting something that is a draft takes a review date and a fallback.
{
"site": "Agenda de oficinas (exemplo do kit)",
"decisoes": [
{ "nome": "WebMCP", "decisao": "adotar", "motivo": "a página já tem as ferramentas, com detecção e fallback", "revisar_em": "2027-01-15", "fallback": "formulário da página" },
{ "nome": "MCP", "decisao": "adotar", "motivo": "o mesmo serviço atende agentes fora do navegador" },
{ "nome": "NLWeb", "decisao": "esperar", "motivo": "a agenda é pequena; as ferramentas já respondem" },
{ "nome": "llms.txt", "decisao": "esperar", "motivo": "sem efeito medido; a decisão é da Formação inemaSEO" },
{ "nome": "A2A", "decisao": "nao-se-aplica", "motivo": "o site não tem agente próprio para conversar com outro" },
{ "nome": "ACP", "decisao": "nao-se-aplica", "motivo": "as oficinas são gratuitas: não há compra" },
{ "nome": "AP2", "decisao": "nao-se-aplica", "motivo": "nenhum pagamento passa pelo site" },
{ "nome": "Web Bot Auth", "decisao": "esperar", "motivo": "rascunho no IETF; rever quando o curso 4 for aplicado ao site" }
]
}vizinhos.mjs reads the dated map (vizinhos/mapa.json, with the source of each row) and your decisions file.
cd ~/projetos/formacao-webmcp-expert-v72/kit node scripts/vizinhos.mjs; echo "saída: $?"
mapa lido em 19/10/2026 · decisões de: Agenda de oficinas (exemplo do kit) WebMCP rascunho adotar MCP estavel adotar NLWeb projeto esperar llms.txt proposta esperar A2A projeto nao-se-aplica ACP projeto nao-se-aplica AP2 rascunho nao-se-aplica Web Bot Auth rascunho esperar VIZINHOS: 8 protocolos · 8 decisões · 0 problema(s) saída: 0
Free workshops: ACP and AP2 do not apply. Web Bot Auth waits for course 4.
PROBLEMA WebMCP: motivo promete ranking ou padrão ("vai ser o padrão da web")
PROBLEMA WebMCP: adotar algo em rascunho pede revisar_em (AAAA-MM-DD) e fallback
PROBLEMA llms.txt: motivo promete ranking ou padrão ("sobe o site no ranking das IAs")
PROBLEMA Web Bot Auth: sem decisão
VIZINHOS: 8 protocolos · 7 decisões · 4 problema(s)
saída: 1"It will be the standard of the web" and "it moves the site up in the AI rankings" are not reasons: nothing on the map says that. Adopting WebMCP without a review date and without a fallback also fails.
The file vizinhos/ruim.json has four common problems.
cd ~/projetos/formacao-webmcp-expert-v72/kit
node scripts/vizinhos.mjs vizinhos/ruim.json | grep -E "PROBLEMA|VIZINHOS"; echo "saída: ${PIPESTATUS[0]}"The example, the bad one, and your site's decisions.
Run the block with the example decisions.
Done when: node scripts/vizinhos.mjs; echo "saída: $?" → VIZINHOS: 8 protocolos · 8 decisões · 0 problema(s) and saída: 0.
Run the rehearsal of bad decisions and read the four problems.
Done when: The block prints VIZINHOS: 8 protocolos · 7 decisões · 4 problema(s) and saída: 1.
Copy vizinhos/agenda-oficinas.json to vizinhos/meu-site.json and decide each protocol for your site, with your own reason. First, open the source of each row on the map and check whether the status has changed since 10/19/2026.
Done when: node scripts/vizinhos.mjs vizinhos/meu-site.json; echo "saída: $?" → 0 problema(s) and saída: 0.
The explanation appears after the answer.
Question 1 of 4
Which protocol on the map was stable on 10/19/2026?
Question 2 of 4
The site's workshops are free. What should you do with ACP and AP2?
Question 3 of 4
Why does "it raises the site in AI rankings" fail as a reason to adopt llms.txt?
Question 4 of 4
You are going to adopt WebMCP on your site. What does the script require besides the reason?
Choose an option. The explanation appears after your attempt.