Skip to main content

How Our Automation Works

Advanced

Transparency page: here's the machinery that helps keep AILmanac fresh and high-quality with minimal maintainer effort. The principle throughout: automation surfaces work for humans to approve — it never silently publishes unverified claims.

The build gate (active)

Every change is built with onBrokenLinks: 'throw', so a dead internal link or broken MDX fails the build before merge. This is the single most valuable check — it keeps navigation trustworthy.

CI workflows

The workflow files live on the ci-workflows branch and are enabled once the repo has a token with the workflow scope (see the README). Until then the site deploys from the gh-pages branch.

  • build-check — builds every PR (broken links fail). A required check.
  • deploy — builds and publishes to GitHub Pages on push to main.
  • link-checklychee runs weekly and on PRs; on broken external links it opens a tracking issue (label link-rot) instead of just going red.

Freshness automation (planned / phased)

  • Release watcher — a scheduled job that polls Anthropic's docs/changelog and the fastest-churning consumer surfaces (apps, voice, mobile, marketplace). On a change it opens an issue/PR labeled upstream-change + needs-verification pointing at likely-affected pages. A human writes the update.
  • Model-table verifier — diffs data/models.json against the official model list and opens a PR when something drifts. The models table shows a "last verified" date.
  • Staleness sweep — flags volatile pages whose lastVerified is older than a threshold.

Why human-in-the-loop

:::tip Automated and honest > automated and wrong An AI that auto-commits "news" to a reference site risks publishing hallucinations — the opposite of trustworthy. So our automation proposes (issues/PRs); humans verify and merge. See Fact Verification. :::

Want to help with automation?

Improving these workflows is a great advanced contribution — see the .github/workflows (on the ci-workflows branch) and Contribute.

Next