Outreach

Entry points that return to the canonical theory.

Outreach articles introduce AAT, SFT, ArchSig, and attractor engineering for public reading. They are publication routes, not a second source of truth for definitions, theorem status, or tooling claims.

Publication rule

The public site keeps the technical source of truth in English. Japanese essays on Qiita, Zenn, Hashnode, or similar media are welcome as outreach, but they should point readers back to the canonical English page before relying on definitions, theorem status, measurement boundaries, or non-conclusions.

Outreach can explain motivation and intuition. It should not become a parallel place where theorem status, empirical hypotheses, or tooling claims drift away from the repository.

Article routes

These routes collect the current public-article drafts and the intended publication lanes. Platform copies should keep their return links to this site or the corresponding repository source.

Canonical returns

Each outreach article should make the return path explicit. The return target depends on the claim being made, not on the platform where the article is published.

  • AAT definitions and theorem status Return to AAT, AAT Lean Status, and the repository theorem index before making formal claims.
  • SFT forecasts and field language Return to SFT and the AAT / SFT interface before reading field, force, attractor, or forecast as a theorem.
  • ArchSig measurements Return to ArchSig and ArchSig Boundaries before treating tool output as evidence for a broader conclusion.

SEO sitemap

This repository does not commit a production sitemap.xml until the public domain is chosen. After the domain is fixed, the sitemap should be generated or manually written from website/SITEMAP.md, using the GitHub Pages public root as the URL base.