docs(factories): add launch documentation foundation

.agents/skills/style_lint/style_lint.py

@@ -85,7 +85,6 @@
     ("Oz run",       "PLATFORM_RUN",             "{VARS.PLATFORM_RUN} in prose or {{PLATFORM_RUN}} in frontmatter"),
     ("Oz API & SDK", "API_SDK_NAME",             "{VARS.API_SDK_NAME} in prose or {{API_SDK_NAME}} in frontmatter"),
     ("Oz Platform",  "WARP_AUTOMATION_PLATFORM", "{VARS.WARP_AUTOMATION_PLATFORM} in prose or {{WARP_AUTOMATION_PLATFORM}} in frontmatter"),
-    ("Oz",           "WARP_AUTOMATION_PLATFORM", "{VARS.WARP_AUTOMATION_PLATFORM} in prose or {{WARP_AUTOMATION_PLATFORM}} in frontmatter"),
 ]
 
 # Oz terms to avoid (case-insensitive patterns)
@@ -908,19 +907,15 @@ def check_hardcoded_vars(lines: List[str], filepath: str) -> List[Issue]:
     `oz.warp.dev` in a code fence are not flagged.
 
     Literals are checked longest-first and matches are deduplicated by span so
-    a specific match (e.g. "Oz Platform", "Oz CLI") doesn't also get re-flagged
-    by the more general bare "Oz" entry for the same occurrence.
+    overlapping rename-sensitive names are not double-flagged.
 
     Matches use word boundaries (`\b`) rather than plain substring search, so
-    short literals like bare "Oz" don't false-positive inside unrelated tokens
-    such as URL query params, hashes, or other identifiers (e.g. a YouTube
-    share link's `si=OzvuInMl8DoNR97R` parameter).
-
-    An "@"-prefixed occurrence is skipped. "@Oz" is a literal mention handle
-    that a user types in Slack or Linear, not the product name appearing in
-    prose. Handles are strings the product owns, so they do not necessarily
-    change when the product name does -- variabilizing them would silently
-    rewrite a working handle into an invalid one at rename time.
+    literals don't false-positive inside unrelated tokens such as URL query
+    params, hashes, or other identifiers.
+
+    An "@"-prefixed occurrence is skipped because mention handles are literal
+    strings that do not necessarily change with product names. Variabilizing
+    a handle could silently rewrite it into an invalid value at rename time.
     """
     issues = []
     in_code_block = False
@@ -943,7 +938,7 @@ def check_hardcoded_vars(lines: List[str], filepath: str) -> List[Issue]:
                 span = m.span()
                 if any(span[0] >= s and span[1] <= e for s, e in matched_spans):
                     continue
-                # "@Oz" is a mention handle users type, not prose. See docstring.
+                # Mention handles are literal strings, not prose. See docstring.
                 if span[0] > 0 and prose_line[span[0] - 1] == "@":
                     continue
                 matched_spans.append(span)

astro.config.mjs

@@ -167,8 +167,9 @@ export default defineConfig({
 					customSets: [
 						{ label: 'Terminal', description: 'Warp Terminal features and configuration.', paths: ['terminal/**'] },
 						{ label: 'Agents', description: 'Warp\'s agents: capabilities, local agents, and CLI agents.', paths: ['agents/**'] },
+						{ label: 'Factories', description: 'Warp Factories documentation for setup, agent roles, definitions as code, integrations, measurement, and infrastructure.', paths: ['factories/**'] },
 						{ label: 'Warp Agent CLI', description: 'The Warp Agent CLI: agent conversations, shell commands, permissions, and configuration in any terminal.', paths: ['agents/cli/**'] },
-						{ label: 'Oz Platform', description: 'Warp\'s Oz platform: cloud agents, orchestration, triggers, integrations, environments, harnesses, and self-hosting.', paths: ['platform/**'] },
+						{ label: 'Automation Platform', description: 'Warp\'s Automation Platform: cloud agents, orchestration, triggers, integrations, environments, harnesses, and self-hosting.', paths: ['platform/**'] },
 						{ label: 'Code', description: 'Code editor, code review, and Git worktrees.', paths: ['code/**'] },
 						{ label: 'Enterprise', description: 'Enterprise features, SSO, team management, and security.', paths: ['enterprise/**'] },
 						{ label: 'Getting Started', description: 'Installation, quickstart, and migration guides.', paths: ['index', 'quickstart', 'getting-started/**'] },

src/components/WarpTopicNav.astro

@@ -5,9 +5,8 @@
 // Reference, etc.) as an inline-flex row with a small icon + label. The list
 // is sourced from `starlight-sidebar-topics`'s middleware, which exposes
 // `Astro.locals.starlightSidebarTopics.topics` on every Starlight route.
-// Each topic carries `{ link, label, icon, badge, isCurrent }`; we consume
-// `link`/`label`/`icon`/`isCurrent` and ignore `badge` for now (none of our
-// topics ship one). The plugin's per-topic sidebar filtering lives in its
+// Each topic carries `{ link, label, icon, badge, isCurrent }`. The plugin's
+// per-topic sidebar filtering lives in its
 // middleware (it rewrites `starlightRoute.sidebar`), so removing the topic
 // list from the sidebar markup does NOT break that filtering — the same
 // filtered nav still renders below this row in the page sidebar.
@@ -26,7 +25,7 @@
 //     underline share `--sl-color-text-accent`, which auto-adapts to dark
 //     and light themes.
 //   - No surrounding chip / box / bg — just type + icon
-import { Icon } from '@astrojs/starlight/components';
+import { Badge, Icon } from '@astrojs/starlight/components';
 
 const { topics } = Astro.locals.starlightSidebarTopics;
 
@@ -122,6 +121,11 @@ const CUSTOM_TOPIC_ICONS: Record<string, true> = {
 							</span>
 						) : null}
 						<span class="warp-topic-nav__label">{topic.label}</span>
+						{topic.badge && (
+							<span class="warp-topic-nav__badge">
+								<Badge text={topic.badge.text} variant={topic.badge.variant} />
+							</span>
+						)}
 					</a>
 				</li>
 			))}
@@ -210,6 +214,11 @@ const CUSTOM_TOPIC_ICONS: Record<string, true> = {
 		color: var(--sl-color-text-accent);
 		font-weight: 600;
 	}
+	.warp-topic-nav__badge {
+		display: inline-flex;
+		align-items: center;
+		margin-inline-start: 0.125rem;
+	}
 
 	/* 2px accent underline under the active tab, anchored to the link's own
 	   bottom edge so it hugs the tab. It previously dropped down to the

src/content/docs/enterprise/getting-started/quickstart.mdx

@@ -35,7 +35,7 @@ If you have an existing Warp account from before your organization enabled SSO,
 
 ## 3. Configure and run your first agent
 
-When you use agents in Warp, you're working with **Warp's built-in agents**. {VARS.WARP_AUTOMATION_PLATFORM} is Warp's programmable system for running and coordinating agents at scale, whether they run locally on your machine or in the cloud.
+When you use Agent Mode in Warp, you're working with the Warp Agent, Warp's built-in agent. {VARS.WARP_AUTOMATION_PLATFORM} is Warp's programmable system for running and coordinating agents at scale, whether they run locally on your machine or in the cloud.
 
 ### Index your codebase
 
@@ -52,14 +52,14 @@ Start a conversation right in the terminal. Try the following prompt:
 Explain the architecture of this project
 ```
 
-{VARS.WARP_AUTOMATION_PLATFORM} reads your codebase, understands its structure, and responds with a context-aware explanation.
+The Warp Agent reads your codebase, understands its structure, and responds with a context-aware explanation.
 
 ### Try more prompts
 
 * **Write code** - "Add input validation to the signup form"
 * **Debug** - "Why is this test failing?" (paste the error output)
 * **Explore** - "What patterns does this repo use for error handling?"
-* **Plan** - Use `/plan` to have {VARS.WARP_AUTOMATION_PLATFORM} create a structured task plan for complex features
+* **Plan** - Use `/plan` to have the Warp Agent create a structured task plan for complex features
 
 ## 4. Run a cloud agent
 

src/content/docs/factories/control-room.mdx

@@ -0,0 +1,9 @@
+---
+title: Control room
+description: >-
+  Factory control room documentation will cover monitoring and intervention in a follow-up PR.
+sidebar:
+  label: "Control room"
+---
+
+Factory control room documentation will land in a follow-up PR.

src/content/docs/factories/factory-agents.mdx

@@ -0,0 +1,9 @@
+---
+title: Factory agents
+description: >-
+  Factory agent documentation will cover specialized roles and configuration in a follow-up PR.
+sidebar:
+  label: "Factory agents"
+---
+
+Factory agent documentation will land in a follow-up PR.

src/content/docs/factories/factory-as-code.mdx

@@ -0,0 +1,9 @@
+---
+title: Definitions as code
+description: >-
+  Definitions-as-code documentation for Warp Factories will be added in a follow-up PR.
+sidebar:
+  label: "Definitions as code"
+---
+
+Definitions-as-code documentation for Warp Factories will land in a follow-up PR.

src/content/docs/factories/factory-mcp.mdx

@@ -0,0 +1,9 @@
+---
+title: Factory MCP
+description: >-
+  Factory MCP documentation will cover programmatic factory connections in a follow-up PR.
+sidebar:
+  label: "Factory MCP"
+---
+
+Factory MCP documentation will land in a follow-up PR.

src/content/docs/factories/integrations/github.mdx

@@ -0,0 +1,9 @@
+---
+title: GitHub integration
+description: >-
+  GitHub integration documentation for Warp Factories will be added in a follow-up PR.
+sidebar:
+  label: "GitHub"
+---
+
+GitHub integration documentation for Warp Factories will land in a follow-up PR.

src/content/docs/factories/integrations/jira.mdx

@@ -0,0 +1,9 @@
+---
+title: Jira integration
+description: >-
+  Jira integration documentation for Warp Factories will be added in a follow-up PR.
+sidebar:
+  label: "Jira"
+---
+
+Jira integration documentation for Warp Factories will land in a follow-up PR.

src/content/docs/factories/integrations/linear.mdx

@@ -0,0 +1,9 @@
+---
+title: Linear integration
+description: >-
+  Linear integration documentation for Warp Factories will be added in a follow-up PR.
+sidebar:
+  label: "Linear"
+---
+
+Linear integration documentation for Warp Factories will land in a follow-up PR.

src/content/docs/factories/integrations/slack.mdx

@@ -0,0 +1,9 @@
+---
+title: Slack integration
+description: >-
+  Slack integration documentation for Warp Factories will be added in a follow-up PR.
+sidebar:
+  label: "Slack"
+---
+
+Slack integration documentation for Warp Factories will land in a follow-up PR.

src/content/docs/factories/measure-and-improve.mdx

@@ -0,0 +1,9 @@
+---
+title: Measure and improve
+description: >-
+  Factory measurement and improvement documentation will be added in a follow-up PR.
+sidebar:
+  label: "Measure and improve"
+---
+
+Factory measurement and improvement documentation will land in a follow-up PR.

src/content/docs/guides/agent-workflows/build-a-self-improving-agent.mdx

@@ -120,7 +120,7 @@ Over time, the companion skill accumulates a clear description of how your team
 
 ## Next steps
 
-* [What is a software factory?](/platform/software-factory) — How the outer improvement loop fits into the full factory model.
+* [Warp Factories overview](/factories/) — How the outer improvement loop fits into the full factory model.
 * [Set up your software factory](/guides/agent-workflows/set-up-a-software-factory) — The inner loop the outer loop improves.
 * [Run a software factory in the cloud](/guides/agent-workflows/run-a-software-factory-in-the-cloud) — Move the loop to {VARS.WARP_AUTOMATION_PLATFORM} for team-wide visibility.
 * [Scheduled agents](/platform/triggers/scheduled-agents) — Full reference for running cloud agents on a cadence.

src/content/docs/guides/agent-workflows/build-a-triage-agent.mdx

@@ -11,7 +11,7 @@ tags:
 ---
 import { VARS } from '@data/vars';
 
-Learn how to use {VARS.WARP_AUTOMATION_PLATFORM} to build a triage agent that reviews each new GitHub issue for clarity, applies labels, and flags open questions before implementation begins. After completing the steps in this guide, you will have a working triage skill deployed as a GitHub Action. This is the first agent in your [software factory](/platform/software-factory).
+Learn how to use {VARS.WARP_AUTOMATION_PLATFORM} to build a triage agent that reviews each new GitHub issue for clarity, applies labels, and flags open questions before implementation begins. After completing the steps in this guide, you will have a working triage skill deployed as a GitHub Action. This is the first agent in your [software factory](/factories/).
 
 ## Prerequisites
 
@@ -121,7 +121,7 @@ Add repo-specific context without forking the core skill by creating a `triage-i
 
 ## Next steps
 
-* [What is a software factory?](/platform/software-factory) — How the triage agent fits into the full development loop.
+* [Warp Factories overview](/factories/) — How the triage agent fits into the full development loop.
 * [Write product and tech specs with agents](/guides/agent-workflows/write-product-and-tech-specs-with-agents) — Add the spec role once your backlog is well-triaged.
 * [Build a self-improving agent](/guides/agent-workflows/build-a-self-improving-agent) — Automate skill improvement based on your corrections.
 * [GitHub Actions integration](/platform/integrations/github-actions) — Full documentation for `warpdotdev/oz-agent-action`.

src/content/docs/guides/agent-workflows/run-a-software-factory-in-the-cloud.mdx

@@ -96,7 +96,7 @@ See [Multi-agent orchestration](/platform/orchestration) for fan-out, sharding,
 
 ## Next steps
 
-* [What is a software factory?](/platform/software-factory) — The conceptual overview of the full loop.
+* [Warp Factories overview](/factories/) — The conceptual overview of the full loop.
 * [Build a self-improving agent](/guides/agent-workflows/build-a-self-improving-agent) — Add the outer improvement loop on a schedule.
 * [Environments](/platform/environments) — Full reference for cloud agent environments.
 * [Deployment patterns](/platform/deployment-patterns) — Choose the right architecture for your team.

src/content/docs/guides/agent-workflows/set-up-a-software-factory.mdx

@@ -162,7 +162,7 @@ The reviewer agent surfaces issues and inconsistencies; the human makes the fina
 
 ## Next steps
 
-* [What is a software factory?](/platform/software-factory) — The conceptual overview of the full loop.
+* [Warp Factories overview](/factories/) — The conceptual overview of the full loop.
 * [Run a software factory in the cloud](/guides/agent-workflows/run-a-software-factory-in-the-cloud) — Move the loop into a managed {VARS.WARP_AUTOMATION_PLATFORM} deployment.
 * [Build a self-improving agent](/guides/agent-workflows/build-a-self-improving-agent) — Add the outer improvement loop.
 * [Review AI-generated code](/guides/agent-workflows/how-to-review-ai-generated-code) — The human review workflow for agent-generated PRs.

src/content/docs/guides/agent-workflows/write-product-and-tech-specs-with-agents.mdx

@@ -72,7 +72,7 @@ A tech spec defines how the feature will be implemented, including architecture
 
 ## Next steps
 
-* [What is a software factory?](/platform/software-factory) — How specs fit into the full development loop.
+* [Warp Factories overview](/factories/) — How specs fit into the full development loop.
 * [Set up your software factory](/guides/agent-workflows/set-up-a-software-factory) — Connect the spec role to implementation and review.
 * [`warpdotdev/common-skills`](https://github.com/warpdotdev/common-skills) — The full set of shared skills including `write-product-spec`, `write-tech-spec`, and `validate-changes-match-specs`.
 * [Planning](/agents/capabilities/planning) — Warp's built-in planning feature for smaller tasks.

src/content/docs/platform/deployment-patterns.mdx

@@ -113,7 +113,7 @@ When a task is naturally divisible, use [multi-agent orchestration](/platform/or
 
 ## Pattern 3: Self-hosted execution
 
-Use this when you need to control where agent execution happens while still using {VARS.WARP_AUTOMATION_PLATFORM} orchestration and visibility. Repositories are cloned and stored only on your infrastructure; orchestration metadata, session transcripts, and LLM inference route through Warp's backend under [ZDR](/enterprise/security-and-compliance/security-overview/#zero-data-retention-zdr).
+Use this when you need to control where agent execution happens while still using {VARS.WARP_AUTOMATION_PLATFORM} orchestration and visibility. Repositories are cloned and stored only on your infrastructure. Orchestration metadata and session transcripts route through Warp's backend; cloud conversations require Warp to store conversation data according to Warp's retention terms. LLM inference requests and responses route through Warp to contracted model providers under [ZDR](/enterprise/security-and-compliance/security-overview/#zero-data-retention-zdr), except for provider-specific models that are not covered by ZDR and follow the provider's retention requirements.
 
 Think of self-hosted execution as **customer-hosted execution with Warp-hosted orchestration**, not as a fully offline agent stack. Code repositories, build artifacts, runtime secrets, and execution workspaces stay on your infrastructure. Code context can still appear in session transcripts and LLM prompts as the agent works.