docs(factories): editorial pass on infrastructure and security

[hongyi-chen]

Summary

Editorial pass on top of #523. The content and verified facts are unchanged — this is a clarity and house-voice rewrite of factories/infrastructure-and-security.mdx, plus the same treatment for the two self-hosting paragraphs that PR touches.

Targets hyc/factories-infra so it can be merged into #523 before that PR lands.

What was unclear

The page read like a compliance memo rather than Warp docs:

• Hedged, third-person phrasing. "supported factory data," "the applicable provider account," "available controls depend on your team's configuration and agreement with Warp," "customer-owned" throughout. The style guide calls for second person and plain language.
• Four stacked decision tables, the third of which (Choose execution, inference, and storage independently) largely restated the two above it.
• Inconsistent bolding inside those tables — **Environment** bold, Runner not; **Checkout and commands** bold, Compute not. This appears to have been driven by the style linter's glossary check rather than by meaning.
• Relative page links (../platform/environments). Every other page in the repo uses root-relative links with trailing slashes; this was the only file using the other form.
• Missing house conventions: no callouts, no --- section breaks, no Related pages section, and no Early Access / Enterprise gating treatment even though most of the page describes Enterprise-gated controls.
• Implementation detail that belongs on the pages this one links to: runner file resolution mechanics, "Warp rejects a hosted shape above that limit," "workers authenticate to Warp with a supported principal."

What changed

• Opens with what the reader controls, leading with the product name for search and answer engines.
• Reuses the orchestration-vs-execution framing already established in platform/self-hosting/, instead of introducing fresh "control plane / execution plane" vocabulary for the same idea.
• One comparison table (Warp-hosted vs self-hosted) survives, with consistent bolding. Environments/runners, the independent-choice matrix, and credentials become bold-term lists in the standard * **Term** - description format.
• Callouts carry the gating and the caveats: :::note[Early access] for Early Access and Enterprise features, :::caution for "self-hosting is customer-hosted execution, not a guarantee that factory data stays in your network."
• Adds a Related pages section and converts all links to root-relative form with trailing slashes.
• Simplifies the Mermaid diagram — the previous version carried a three-line sentence on one edge.
• Same clarity pass on the self-hosting wording: "Warp stores applicable orchestration and conversation data according to your product configuration and agreement" → "Warp stores orchestration and conversation data according to your team's configuration and its agreement with Warp," and the BYOLLM section keeps its BYOLLM link.

No new product claims. Every fact, caveat, and eligibility statement from #523 is preserved.

Validation

• npm run typecheck — 0 errors
• npm run build — 377 pages built, Complete!
• Every internal link on the three edited pages resolves against the built routes — 0 broken
• Style lint — clean except two unrecognized-term warnings on the bold table header row, the identical pattern platform/self-hosting/index.mdx already produces

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
docs	Ready	Preview	Aug 16, 2026 6:00am

[hongyi-chen]

This PR was generated with Warp.