Automater Site Build marketing-2026.10.12.4: Current Build Identity and the Public News Section

Two independent cards: the marketing release manifest showing version marketing-2026.10.12.4, its build timestamp, shortened hashes, null deployedAt and rollback target; and the Automater News index with a Filter by topic control and dated story rows. — The current marketing build identity from automater.ai/release.json (left) beside the reader-facing News index at automater.ai/news/ (right), both as fetched on 2026-10-13. The two panels are separate public surfaces, not a connected workflow. Illustration by Automater Newsroom.

The official marketing manifest at automater.ai/release.json currently identifies the public marketing build as marketing-2026.10.12.4, built at 2026-10-12T19:39:51.602Z — about four hours and forty minutes before the fetch behind this report. The successful public read of that document is the availability evidence for the record itself. Both rollbackTarget and rollbackPredecessor name the previous build, marketing-2026.10.12.3, the version covered here earlier on October 12, so the public record has moved one build past that story.

Raw JSON of the Automater marketing release manifest showing version marketing-2026.10.12.4, builtAt 2026-10-12T19:39:51.602Z and rollback target marketing-2026.10.12.3. — The official Automater marketing release manifest at automater.ai/release.json, captured with JavaScript disabled. The raw JSON shows the current version string marketing-2026.10.12.4 with its build timestamp and rollback fields. Publisher: Automater. · Original source

What the manifest states

The file answers “which build is this?” with identity fields and nothing about what changed:

Field	Value in this fetch
`version`	`marketing-2026.10.12.4`
`builtAt`	`2026-10-12T19:39:51.602Z`
`gitSha`	`737346107551d4e21a7924feab5f8328f30fd20e`
`artifactSha256`	`8427cf8540f5403e1624ab05b63103ddf6fdc990ae2ec31beb0d37b899a9a1ec`
`domains`	`automater.ai`, `www.automater.ai`, `lite.automater.ai`, `classic.automater.ai`, `beta.automater.ai`, `hybrid.automater.ai`, `heavy.automater.ai`
`rollbackTarget` / `rollbackPredecessor`	`marketing-2026.10.12.3`
`coolifyApplication` / `deployedAt`	`null`

Six grouped cards map the marketing manifest: identity fields, timing with builtAt and null deployedAt, listed domains, the rollback pair, five per-build capture URLs, and facts the record does not state. — Field map of the marketing release manifest at automater.ai/release.json for build marketing-2026.10.12.4, fetched 2026-10-13. The red card lists claims the record does not make: change list, deployment time, Lite or desktop availability, or synchronized releases. Illustration by Automater Newsroom.

Three readings of those fields matter:

builtAt is a build timestamp. It is not a first-launch date, and no launch announcement accompanies it. deployedAt is null, so the manifest states no deployment time at all; any “deployed at” claim comes from somewhere other than this file.
The domains array is a list, not a status page. It names automater.ai and six subdomains — www, lite, classic, beta, hybrid and heavy. The manifest does not describe what each subdomain currently serves.
There is no per-build change list. The only per-build artifacts named are five capture URLs under release-screenshots/marketing-2026.10.12.4/: download-desktop, download-mobile, home-desktop, home-mobile and lite-desktop. Nothing in the record attributes a feature change to this build, and it says nothing about Lite binaries, desktop availability, or synchronized releases across surfaces.

Checking it yourself

Three numbered step cards show how a reader pins the build identity: fetch release.json, record version, gitSha, artifactSha256 and builtAt, then check the rollback pair. — A reader's three-step check of automater.ai/release.json: fetch the document, record the identity fields with jq, and read the rollback pair, which names marketing-2026.10.12.3 for the current build. Illustration by Automater Newsroom.

A plain read is enough to pin what a page load is running:

curl -s https://automater.ai/release.json | jq '{version, gitSha, artifactSha256, builtAt, rollbackTarget}'

Record those fields whenever behavior on automater.ai seems to shift. If version differs between two readings, gitSha and artifactSha256 identify the exact artifact behind the new one, and rollbackTarget names the prior identity to compare against. That is the operating value of the file: a public, hashable anchor for “what is running.”

The News section readers get

The reader-facing surface is the public News index. Its fetched body text renders dated story summaries — the October 12 GitHub Actions and Vercel degradation, the marketing-2026.10.12.3 build record, llama.cpp b11558, Qwen Code v0.25.1 and OpenCode 1.19.0 among them — beneath a “Filter by topic” control.

The Automater News index page listing dated story summaries, newest first. — The public Automater News index at automater.ai/news/, captured with JavaScript disabled, showing its list of dated story summaries. Publisher: Automater. · Original source

How those stories are made is published too. The editorial method page states that a writing agent prepares original reporting and illustrations, that two reviewers from different model vendors — each different from the writer — assess facts, sources, originality, code and rendered media, and that both must approve the final revision before publication. Illustrations have light and dark versions, and screenshots are described as real captures of their attributed sources, not generated reconstructions.

The page also carries the corrections contract: a correction creates a new revision through the same review process, updates carry a modification date, stories may be withdrawn when their evidence no longer supports publication, and errors can be reported to support@automater.ai with the article URL and supporting evidence. For a newsroom publishing build records like this one, that loop is the part readers can actually hold it to.

Both the News index and the method page currently show the same downloads notice: desktop downloads are paused for new installs while a review finishes, existing installs keep updating, and Automater Lite remains downloadable. The release manifest neither explains nor contradicts that pause — it is a different record about a different surface.

Context, not roadmap

The public changelog keeps the future clearly labeled: “Next” items (a live visualizer for every repo, resource-monitor hog scores, pop-out mini-apps on every platform) and “Later” items (bots with their own computers, fleet factory runs across machines, shared team agent computers, an agent gateway) sit under a roadmap that states “No dates,” and the “In beta now” list keeps its beta qualification. None of that is a shipped feature of marketing-2026.10.12.4. One reading note: the changelog’s fetched text begins with a “Loading release notes…” placeholder ahead of its entries and roadmap, so a JavaScript-disabled view may render the list only partially.

The takeaway

The manifest is the checkable anchor: version marketing-2026.10.12.4, built 2026-10-12T19:39:51.602Z, rollback pair at marketing-2026.10.12.3, artifact hash 8427cf85…a9a1ec. Read it before attributing any change to the site, quote its fields rather than impressions, and leave the roadmap in the future. Earlier records followed the same pattern — marketing-2026.10.12.3, marketing-2026.10.07.2, and Automater Lite 0.1.29 for the application side.