docs: rename Oz to Automation Platform

[rachaelrenk]

Summary

Follow-up to #513, which built the rename machinery and deliberately deferred the rename itself. This PR performs the rename: WARP_AUTOMATION_PLATFORM flips from "Oz" to "Automation Platform", and the prose is edited to match.

Draft while the article pass lands. See "Why this is one PR" below — the value flip and the prose edits are only correct together, so they cannot be split.

Plan: 2dcfd56b-e53c-4931-9310-7bdca5e956eb

Why this is one PR

"Oz" is a proper noun that reads correctly bare: "with Oz", "Oz provides", "Oz's backend". "Automation Platform" is a common-noun phrase that needs a definite article in the same positions. Flipping the variable alone produces "with Automation Platform" and "Automation Platform's backend" across most of the platform docs.

The inverse is also true, which is what forces the atomicity: inserting "the" before a token that still renders "Oz" produces "the Oz". Neither half is correct on its own.

The two defect sets

Measured on this branch against hyc/factory-launch at 0254fb7b.

Will break on the flip — 205 sites across 72 files. WARP_AUTOMATION_PLATFORM is used 264 times across 78 files (235 as {VARS.X} in body prose, 29 as {{X}} in frontmatter). Of those, 59 already read correctly with a common-noun name. The other 205 need an article or a rewrite: 175 in running prose, 19 in link text, 8 possessive, 3 bold term leads.

Already broken today — the opposite direction. The tokenization pass in #513 replaced the phrase "Oz platform" with the variable but dropped the word "platform", leaving the article behind. Those sites render "the Oz" on the merged branch right now, including the platform overview's own frontmatter description ("The Oz provides the CLI, API/SDK, orchestration, environments, and observability"), which is also its meta description and AI-citation snippet. Every one of these is fixed by the flip, with no edit required.

So the current state is not a safe resting point that the rename endangers. The correct state exists only on the far side of doing both together.

The article rule

Applied consistently across all 205 sites:

Referential uses take "the" — when the token names the platform as an entity (subject, object, or possessor).

• with {VARS.X} → with the {VARS.X}
• {VARS.X} provides → The {VARS.X} provides
• {VARS.X}'s backend → the {VARS.X}'s backend

Attributive uses stay bare — when the token modifies a following noun.

• {{X}} settings, {{X}}-hosted, {{X}} overview, {{X}} Open Source Partnership

Two categories took a judgment call rather than a mechanical insert. Link text ([{VARS.X}](...)) puts the article outside the link so anchor text stays clean for search and agents. Bold term leads (* **{VARS.X}** - ...) are definitions, so the term stays bare.

Changes

src/data/vars.ts

• WARP_AUTOMATION_PLATFORM: "Oz" → "Automation Platform"

Prose — 205 sites across 72 files

• Article pass per the rule above.
• Plus the rename-sensitive strings that were still hardcoded and would not have flipped with the variable.

src/sidebar.ts

Not processed by the Vite transform, so its labels are invisible to both the flip and the lint guard.

• 'Getting started with Warp and Oz' — duplicated index.mdx's tokenized frontmatter title, so the two would have disagreed after the flip.
• 'Oz API & SDK' → ${VARS.API_SDK_NAME}.
• 'Oz web app' → ${VARS.WEB_APP} (tokenized only; the value holds until 9/15).

.agents/skills/style_lint/style_lint.py

• RENAME_SENSITIVE_VAR_STRINGS keeps its "Oz" entries, which now catch stale references rather than un-tokenized ones, and gains "Automation Platform" entries so the new name cannot be hardcoded either.

Transition language

A short :::note on the highest-traffic entry points stating that Oz is now the Automation Platform and that the oz CLI and oz.warp.dev keep working until 9/15. A first-reference parenthetical on a handful of secondary pages. Both time-boxed for removal after 9/15.

Four sites changed to "Warp" instead (80526c03)

Each was assessed for whether the sentence is truly about the platform as distinct from Warp. These four are not, so the plain product name is both accurate and more durable. All four read correctly under the old and new values, so they carry no rename risk.

• enterprise/enterprise-features/architecture-and-deployment.mdx and enterprise/security-and-compliance/security-overview.mdx — "let Warp orchestrate agents in isolated Docker containers". The adjacent bullet in the same list already reads "Warp provides cloud connectivity, shared context, visibility, and session sharing".
• platform/orchestration/index.mdx — the description said workflows run "on the Oz", but the page body says orchestration "supports local, cloud, and mixed execution". The description was narrower than the page.
• platform/runners.mdx — "Full command-line reference for the Oz" carried no information under any product name.

The remaining dangling sites are all under platform/ and deliberately keep the platform name: those sentences exist to draw the platform-versus-Warp distinction, so collapsing them would break the sentence.

What holds until 9/15

Untouched, each a separate value change on the later date:

• WARP_AGENT_CLI ("Oz CLI", the oz binary), WEB_APP ("Oz web app"), WEB_APP_URL (oz.warp.dev)
• The platform/oz-web-app slug
• Every oz <command> invocation and oz.warp.dev URL inside code fences
• Changelog entries — historical records, not current product surface
• @Oz mention handles, still hardcoded pending the product answer flagged on Factory launch (8/18): Automation Platform rename infra + Factories tab scaffold #513

Validation

• npm run build — 370 pages, matching the base
• Internal link check — 0 broken
• style_lint --all — rename-sensitive hardcoded sites at 0
• Article audit re-run with the substitution applied — 0 sites left needing an article
• Rendered HTML grepped for "the Oz" (the defect is invisible in source — The {{WARP_AUTOMATION_PLATFORM}} provides looks fine in the .mdx)
• oz commands and oz.warp.dev URLs inside code fences confirmed untouched
• No slug or redirect changes, so the route count is unmoved

Unverified claims

None — this PR changes product naming and prose only. It adds no new UI labels, Settings paths, CLI flags, permission defaults, or plan-eligibility claims. The 9/15 holdout list reflects the team decision recorded in the #513 thread.

Notes for reviewers

The naming decision assumed here is "Automation Platform", not "Warp Automation Platform". If that is still open with ZL, the article pass is the part that would need redoing — the long form reads acceptably bare in some positions where the short form does not.

Open question on timing: shipping before 8/18 tells readers about a name they cannot see in the product yet; shipping after leaves the "the Oz" renderings live in the meantime.

Co-Authored-By: Warp agent@warp.dev

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 17, 2026 9:21pm

[oz-for-oss]

@rachaelrenk

I'm starting a first review of this pull request.

You can view the conversation on Warp.

I completed the review and no human review was requested for this pull request.

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

Overview

This PR flips WARP_AUTOMATION_PLATFORM to Automation Platform, updates article usage across the docs, refreshes naming-sensitive assets/sidebar labels, and adds lint coverage for future determiner mistakes. The broad rename is mostly consistent, but two correctness issues should be fixed before merge: the new lint rule does not cover frontmatter descriptions, and some integration instructions now tell readers to address the platform itself instead of the agent/handle that users actually interact with.

Concerns

• platform-determiner skips all frontmatter, leaving meta descriptions and other description fields unguarded against the same rendered grammar defect this PR is trying to prevent.
• Slack/Linear guidance still has addressable-platform phrasing after the rename; those instructions should continue to name the agent/handle until the relevant product UI/handles change.

Verdict

Found: 0 critical, 3 important, 0 suggestions

Request changes

Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).

Powered by Oz

[oz-for-oss]

⚠️ [IMPORTANT] This skips every frontmatter field, so platform-determiner misses descriptions like the meta-description defect called out in the PR. Keep the title/sidebar exemptions narrow and still scan description text.

[rachaelrenk]

Fixed in 7c28538. You were right that this was the worst field to leave uncovered — description becomes the meta description, which is what search engines and AI engines read before deciding whether to cite a page.

The check now tracks which frontmatter key it is inside and scans description, including folded >- blocks that continue across indented lines. title and sidebar.label stay exempt, since those are headline-style and correctly bare.

Worth reporting honestly: closing the gap surfaced no live defects — the determiner count is still 0. So this is prevention rather than a fix. That said, the gap was real and I hit its consequences earlier in this work: stale meta descriptions from a build cache were invisible to every check I had at the time, and this rule would now catch the grammar half of that class.