Automater site build marketing-2026.10.12.3: build identity, News topic filter and editorial method
Automater marketing build marketing-2026.10.12.3 built 2026-10-12 identifies current site identity, domains and rollback target; News index shows Subscribe via RSS, topic chips with Filter by topic and dated stories; editorial method documents AI-assisted two-reviewer workflow.
Automater’s public marketing site currently identifies itself as build marketing-2026.10.12.3, built on 2026-10-12. The identifier comes from the official marketing release manifest at release.json, read successfully as a public document, paired with the reader-facing News index and the published editorial method. Together they show what readers can verify now: which site build is current, how News stories can be filtered by topic and subscribed via RSS, and how Newsroom stories are sourced and reviewed.
Current build identity
The manifest labels the surface as marketing, version marketing-2026.10.12.3, with git SHA cf84791cf6925866237023f820cd4e63d2fdb3a4 and artifact SHA-256 fb52e83338e54d4945ea4a5c58fa0552b9e6704e6d1f1300fe91b08b0453500e. Its builtAt timestamp is 2026-10-12T05:08:06.937Z. That timestamp records when this marketing build was produced, not a first-launch announcement date, and the manifest’s deployedAt value is null, which does not by itself establish when deployment occurred. Availability here means the manifest was observed by a successful public read on 2026-10-12.
| Field | Value in release.json |
|---|---|
| surface | marketing |
| version | marketing-2026.10.12.3 |
| gitSha | cf84791cf6925866237023f820cd4e63d2fdb3a4 |
| builtAt | 2026-10-12T05:08:06.937Z |
| deployedAt | null |
| rollbackTarget | marketing-2026.10.12.2 |
| rollbackPredecessor | marketing-2026.10.12.2 |
The same document lists seven domains covered by the build: automater.ai, www.automater.ai, lite.automater.ai, classic.automater.ai, beta.automater.ai, hybrid.automater.ai, and heavy.automater.ai. It also lists five release screenshots under release-screenshots/marketing-2026.10.12.3/ for desktop and mobile download and home views plus a Lite desktop view. Both rollback fields point to marketing-2026.10.12.2, giving operators a concrete predecessor identifier if they need to compare builds.
{
"version": "marketing-2026.10.12.3",
"builtAt": "2026-10-12T05:08:06.937Z",
"deployedAt": null,
"rollbackTarget": "marketing-2026.10.12.2"
}
The manifest does not by itself establish synchronized desktop and Lite releases, Lite binary availability, or performance or hosting behavior. Readers should treat it as what it states: the primary record for marketing build identity and currently observed availability.
News index: hero, RSS, topic chips with Filter by topic, and dated stories
The public News index available now presents a hero headline reading What’s changing. Why it matters. with a visible Subscribe via RSS link directly beneath it, alongside a Latest Briefing panel summarizing recent stories. Below that hero area the page shows a row of topic chips starting with All news followed by llama.cpp, qwen-code, opencode, deno, google cloud, claude-code, and below the chips a collapsed Filter by topic disclosure control, followed by dated entries with headlines and summaries. Captured entries include Oct. 11 stories on llama.cpp, Qwen Code and OpenCode, Oct. 10 stories on Deno, Qwen Code preview and Google Data Agent Kit, Oct. 9 stories on Claude Code, Codex, NVIDIA, Ollama and others, and Oct. 8 stories including Automater Lite 0.1.29. The page footer links to the AI-assisted editorial method and in-depth Intel guides.
For readers, the practical value is straightforward: the index is browsable now, stories carry publication dates, the topic chips with the Filter by topic control offer a way to narrow the list without leaving the public site, and the Subscribe via RSS link visible in the faithful capture offers subscription from the same public page. This article does not claim search behavior or a subscriber count for News, because the verified index evidence and capture supplied for this build do not establish those details. The RSS claim here is limited to what the capture shows: the link is present and visible. Operators and readers who rely on News for fleet decisions should open the index directly and confirm the filter and RSS behavior in their own browser.
A prior site-build report on marketing-2026.10.07.2 covered a similar pairing of build identity with News filtering and the editorial method. That earlier coverage remains useful context for how the manifest, index, and method pages fit together, while this article covers only the newer marketing-2026.10.12.3 identifier and what is visible now.
Editorial method: cited sources, two reviewers, real screenshots
The published editorial method available now says Newsroom covers AI tools and workflows, industry developments, and publicly shipped Automater updates, with articles AI-assisted and published under the Automater Newsroom byline. Each story draws on cited public sources. A writing agent prepares original reporting and illustrations, then two reviewers from different model vendors, each different from the writer, assess facts, sources, originality, code and rendered media. The writer addresses their findings, and both reviewers must approve the final revision before publication.
On images, the method draws a distinction readers can use when evaluating a story: illustrations are authored for the article with light and dark versions, while screenshots are real captures of their attributed source, not generated reconstructions. On upkeep, corrections create a new revision through the same review process, updates carry a modification date, and stories may be withdrawn when evidence no longer supports publication. The page invites error reports by email to support@automater.ai with the article URL and supporting evidence, alongside a back-to-News link.
What this build does not prove
Terse manifest fields do not support broader guarantees. Nothing in the three verified documents establishes secure credential storage, proxy routing, automatic capture triggers, full transcript preservation, immutability, protection from provider retention, replacement of external configuration files, model deployment across a fleet, performance benchmarks, or availability on every platform. Roadmap or Next items remain future, and any beta label retains that qualification. The download notice visible in News captures, which pauses desktop downloads for new installs while a review finishes, is separate administrative status text, not evidence about the marketing build itself.
How to verify now
- Open release.json and confirm
version,builtAt,gitSha,domains, androllbackTargetmatch the values above. - Open the News index and confirm the What’s changing. Why it matters. hero, the Subscribe via RSS link, the Latest Briefing panel, and the topic chips with the Filter by topic control to narrow dated stories.
- Open the editorial method to confirm sourcing, two-reviewer approval, illustration versus screenshot policy, and the corrections process before citing a News story in operational notes.
Described this way — current build identity with its accurate build date, plus reader features shown as available now — the marketing-2026.10.12.3 evidence supports a narrow but useful report: the site you are reading identifies its build precisely, lists where it applies, and pairs that identity with a filterable News archive with visible RSS access governed by a documented review method.