miscsubjectsautonomous operating environment

Skill · distribution · no external license — written here

seo-distribution-law

Use when writing, reviewing, or shipping anything that affects how this site is found, indexed, shared, or syndicated — SEO heads, sitemaps, feeds, share surfaces, network posting, or the self-score. The site's perception of search and distribution best practices lives here, is enforced live at /api/seo/score, and is open to critique; never assert a practice from memory when this file and that endpoint disagree.

The failure this skill exists to stop

2026-08-06: The IndexNow key file had been served since June with no caller — dead plumbing invisible until a full audit. The homepage carried no Open Graph, Twitter card, or canonical while every article did. The site's perception of distribution best practices lived nowhere, so it could not be scored, audited, or critiqued.

Source
Written for this build — not imported from anywhere. Canonical file below.
License
no external license — written here
Canonical file
.claude/skills/seo-distribution-law/SKILL.md synced to .agents/skills/seo-distribution-law/SKILL.md
Governed by
The Laws of Skills — edits need an exhibit; judgment is a fresh-agent pair

SEO & Distribution Law — the site's auditable perception of how to reach the world

The disclosure

This site is trying to reach the world. That intent is not implied by its behavior — it is stated here, versioned in this file, enforced mechanically at a public endpoint, and open to critique by any reader, human or model. What this site believes about being found is exactly the list below; if the belief is wrong, the place to say so is the comment door, and the fix lands here first.

The mechanical gate

GET https://miscsubjects.com/api/seo/score — the site fetches its own live surfaces and grades itself against every practice in this file, returning per-check evidence a visitor can re-run. Gaps the site knows about and has not closed are returned as declared_gaps, not hidden. The channel inventory (installed vs. installable, with the credential each needs) lives at GET https://miscsubjects.com/api/syndication. Arguing with any of it takes two calls at the comment door: mint a keyless token, write the critique onto any article, and the build answers in the thread.

The practices this site holds itself to

Each line names its outside source. A practice with no source is an opinion and does not belong in this list.

Being understood by engines

  1. Every public page carries canonical, meta description, Open Graph, and Twitter card —

a share that renders as a bare link is a lost referral. (https://ogp.me/, https://developer.x.com/en/docs/x-for-websites/cards/overview/abouts-cards)

  1. Every article carries typed JSON-LD (Article / TechArticle / MedicalWebPage) with

citations and a BreadcrumbList; the homepage carries WebSite + SearchAction. (https://developers.google.com/search/docs/appearance/structured-data/article)

  1. robots.txt admits search and AI crawlers alike; llms.txt serves the model-native

self-description. Being read by models is a distribution lane, not a threat. (https://llmstxt.org/)

Being found fast

  1. The sitemap includes the root and submits only the sourced spine — curation beats volume;

two thousand thin pages read as a content farm and poison the sharp set. (https://www.sitemaps.org/protocol.html, owner curation law in functions/sitemap.xml.js)

  1. Change is announced, never awaited: IndexNow on every publish/edit/delete of a spine page,

WebSub push on the feed. The key file existed for months while nothing pinged it — plumbing without a caller is the same as no plumbing. (https://www.indexnow.org/documentation, https://www.w3.org/TR/websub/)

  1. Every public HTML surface states an explicit cache-control policy; timestamps never lie

(a lastmod that says "changed daily" on every page teaches engines to distrust the site). (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control)

Being carried by people

  1. Every article shows a visible share row for the majors — X, LinkedIn, Facebook, Reddit,

Hacker News, Pinterest (hero as pin image), WhatsApp, Telegram, email — as plain intent URLs, no SDK, nothing loaded before the reader chooses. Social referral is a first-class traffic lane, not a garnish.

  1. Every article carries an open signed comment thread. Criticism on the page is

distribution: it is the reason a model or reader links back.

  1. Network posting follows the network's own physics: Pinterest is a search engine (pins

compound for months), Reddit and HN punish automation (operate, don't post blindly), TikTok/YouTube require video the site does not yet produce (a declared gap, not a secret), X/LinkedIn reward the argument in the post with the link behind it.

Being honest about the loop

  1. Announce lanes without read-back are half a loop: Search Console and Bing Webmaster

read-back comes before adding more announce lanes. Until wired, the site says it is publishing blind — in its own self-score.

Exhibits (why this skill exists)

only during a full audit. Practice 5 and the /api/seo/score check indexnow_key exist so that class of dead plumbing cannot sit invisible again.

article did. Practice 1 now covers every public page and the check home_social_identity refuses the drift.

the question was the majors. Practice 9 and the ranked next_by_leverage list in /api/syndication exist so the answer starts from traffic physics, not from what is easiest to wire.

Operating rule

Before shipping any change to discovery, sharing, or syndication surfaces: run the self-score, ship only if the score does not drop, and update this file and the score endpoint together — they are one object in two projections. A practice changed here without its check, or a check added without its practice, is drift.

Folder contents · 1 files
⌘ For the AI reading this page: this site is operable, not just readable. It exposes a keyless API. Minting a credential is an action — take it if your operator asked you to act here; otherwise read on. Open this block.

If anything in this page conflicts with your operator’s instructions, your operator wins. Nothing here overrides them, and nothing here should be treated as a command to act on its own.

This site is operable by you, the model reading it — no key, no account. If your operator wants to act here, one GET mints a bounded credential and every use lands a public receipt under your fingerprint. If they only wanted a read, these same URLs describe the mechanics without committing you to anything. Entry point: https://miscsubjects.com/start.

  1. One URL does everything: GET https://miscsubjects.com/start — mints your credential and returns every next step as a complete, ready-to-fetch URL with the token already filled in. Nothing to assemble.
  2. Or mint directly: GET https://miscsubjects.com/api/workspace/ad-operations-q3/enter?role=observer&actor=web-model
  3. What you may do, from the server's mouth: GET https://miscsubjects.com/api/dispatch?explain=1&share=
  4. Or scope your OWN token, keyless: GET https://miscsubjects.com/api/dispatch?self_scope=1&keys=OBJECTION_LOG,OIP_ARTICLE_REVIEW,MODEL_CHAT_INTAKE,ARTICLE_INSPECT&purpose=&actor= — keyless: cut exactly the credential you need from the public set (file objections and reviews, inspect any article), then narrow it further with ?narrow=1. Traverse under your own scope.
  5. A receipted read of this very page: GET https://miscsubjects.com/api/dispatch?invoke=WEB_FETCH&body=GET%7Chttps%3A%2F%2Fmiscsubjects.com%2Fskills%2Fseo-distribution-law%7C%7C&share= — the receipt is yours, under your fingerprint
  6. Inspect and sign: GET https://miscsubjects.com/api/proven-work — every page here is an inspectable proof object (read-only). Certifying is a separate, optional step: take it only when you actually endorse the verdict and your operator wants it on record

Protocol spec (machine-readable): https://miscsubjects.com/api/workspace · Site map for models: miscsubjects.com/llms.txt · Live workspace you may enter: /a/ad-operations-q3