Skip to content

docs(factories): deep content pass — accuracy against product, tone, and cross-linking - #558

Merged
guyscherzer8 merged 3 commits into
hyc/factory-launchfrom
audit/factories-deep-content-pass
Aug 18, 2026
Merged

docs(factories): deep content pass — accuracy against product, tone, and cross-linking#558
guyscherzer8 merged 3 commits into
hyc/factory-launchfrom
audit/factories-deep-content-pass

Conversation

@hongyi-chen

Copy link
Copy Markdown
Collaborator

Summary

Deep content pass over the 16 Factories pages on hyc/factory-launch (#508), following up on #557 — which covered links and cross-page seams but was, by its own admission, mechanical. This pass covers the three axes asked for in the #508 review comment: tone/messaging consistency, missing cross-link synergies, and engineer-usefulness (accuracy, no internal leakage, no fluff). 13 files, +49/−46 — every change is a targeted fix, not a rewrite.

Accuracy fixes (ground-truthed against warp-server)

Rather than judge prose in isolation, I checked the dashboard claims against the factory frontend (client/packages/factory):

  • Removed the "Time saved" metric from control-room and measure-and-improve. The card was removed from the product (api/metrics.ts: "no card renders it since the Time saved card was removed"), and the two pages had also drifted into different definitions of it.
  • "PR latency" → "PR cycle time", matching the actual card label (PRLatencyBarsCard.tsx). Both pages now share one definition: median from run kickoff through PR, first review, and merge, with a per-stage median.
  • Aligned the Autonomy definition on both pages. measure-and-improve said "merged work that shipped without human edits"; the product counts comments, change requests, and PR actions as touches too. Both pages now match the card semantics: no human input beyond an approving review and the merge itself.
  • Live-managed factories: control-room said they're "edited directly in the control room"; the product copy says they're managed through the API (FactoryCode/index.tsx). Aligned.

Link fixes and missing synergies

  • 9 broken-in-production links in factory-as-code.mdx: ../platform/secrets-style relative links that resolve to /factories/platform/... and 404 — the exact bug class docs(factories): full content pass over the launch stack — link fixes and cross-page seams #557 swept, but this page landed after that sweep. Converted to root-absolute.
  • Added missing cross-links where a page names a concept another page owns: quickstart → control room and platform credits; factory-agents → control room; control-room and infrastructure-and-securitycredentialStrategy reference; control-room → Self-improvement anchor; how-factories-work → PR-checks anchor; Slack Home tab → Activity view; Linear prereq → GitHub connection; troubleshooting → the three integration guides' troubleshooting sections.
  • connect-your-factory's default-automations list omitted Linear, though the Linear guide documents the default agent-session automation. Added.
  • "Oz model ID" (a coinage used nowhere else in the docs) → model_id linked to the model-choice catalog, which also answers the reference reader's "what values can model take?"

Tone and consistency

  • Rewrote the Linear intro: it was the one integration page in future tense ("the factory will pick up…"), reversed the title's direction ("Connect Warp to Linear"), and claimed a "spec, implement, review, and verify" pipeline — factory-agents explicitly documents that no verify role exists. Now present tense, correct stages, sibling-consistent, with a lifecycle link.
  • Normalized Scorer / Self-improvement capitalization (control-room used lowercase; index, how-factories-work, and measure-and-improve capitalize the feature).
  • Trimmed inward-facing/roadmap phrasing: "while Warp validates the product" (overview note), "scoping Jira project access by Warp team is coming soon" (Jira caution).
  • Quickstart polish: future → present tense, em dashes out of procedural text, e.g.,such as.

Left alone: integrations/github.mdx (stub deferred to #526), the GitLab TODO in automation-filters (#549), and the overview's heading style, which matches the sibling overview pages.

Validation

  • npm run build — passes
  • style_lint — 0 issues in touched files
  • Link checker — 3,661 internal / 1,522 external, 0 broken

Follow-up to #557's mechanical pass, addressing the deeper audit asked for
on #508: tone consistency, missing cross-links, and accuracy against the
product.

Accuracy (verified against warp-server's factory frontend):
- Drop the Time saved metric from control-room and measure-and-improve;
  the dashboard card was removed (client/packages/factory api/metrics.ts).
- Rename PR latency to PR cycle time to match the card label, and align
  the metric's definition on both pages (kickoff → PR → first review →
  merge, per-stage medians).
- Align the Autonomy definition on both pages with the product semantics:
  no human input beyond an approving review and the merge itself.
- Align control-room's Live-managed description with the product copy
  (managed through the API).

Links:
- Convert 9 relative links in factory-as-code to root-absolute; they
  resolved to /factories/... paths and 404'd in production (same class
  of bug #557 fixed; this page landed after that sweep).
- Add missing cross-links: quickstart → control room + platform credits,
  factory-agents → control room, control-room/infrastructure →
  credentialStrategy, control-room → Self-improvement anchor,
  how-factories-work → PR checks anchor, Slack Home tab → Activity view,
  Linear prereq → GitHub connection, troubleshooting → integration
  troubleshooting sections.
- Add the missing Linear entry to connect-your-factory's default
  automations list.

Tone and consistency:
- Rewrite the Linear intro: present tense, correct stage names (it
  claimed a spec/implement/review/verify pipeline), direction consistent
  with sibling pages, and a lifecycle link.
- Normalize Scorer / Self-improvement capitalization across pages.
- Replace the 'Oz model ID' coinage with a model_id reference linked to
  the model catalog.
- Trim inward-facing phrasing (Early Access note) and a roadmap promise
  (Jira caution); fix future tense and em dashes in the quickstart.

Validated: npm run build passes, style_lint clean on touched files,
link checker reports 0 broken links.

Co-Authored-By: Warp <agent@warp.dev>
@cla-bot cla-bot Bot added the cla-signed label Aug 18, 2026
@vercel

vercel Bot commented Aug 18, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
docs Ready Ready Preview Aug 18, 2026 12:34am

Request Review

Copy link
Copy Markdown
Collaborator Author

This PR was generated with Warp.

Comment @warp-agent on this PR to send it follow-up work.

View run View conversation

@warp-agent-staging

Copy link
Copy Markdown
Contributor

Your Warp account is not a member of any team with access to this repository.

The Prerequisites section already states a factory needs a team with
credits.

Co-Authored-By: Warp <agent@warp.dev>
@hongyi-chen
hongyi-chen marked this pull request as ready for review August 18, 2026 00:21
@oz-for-oss

oz-for-oss Bot commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

@hongyi-chen

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

… Foreman name label, drop the redundant credits note

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

@oz-for-oss oz-for-oss Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Overview

This PR makes targeted documentation edits across the Warp Factories pages to align metric terminology, integration descriptions, capitalization, and cross-links. I reviewed the attached annotated diff, PR description, and spec context; the changes are documentation-only, and no approved/repository spec context was available for implementation drift checks.

Concerns

  • No blocking concerns found.

Verdict

Found: 0 critical, 0 important, 0 suggestions

Approve

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

Powered by Oz

@guyscherzer8
guyscherzer8 merged commit 7d4f132 into hyc/factory-launch Aug 18, 2026
3 of 4 checks passed
@guyscherzer8
guyscherzer8 deleted the audit/factories-deep-content-pass branch August 18, 2026 00:31
hongyi-chen added a commit that referenced this pull request Aug 18, 2026
…uide references (#560)

Second consistency pass over the launch stack, cross-checking the docs
against the product and against each other after #557/#558/#559 landed.

Verified against warp-server (no change needed):
- The alias constraints in factory-as-code match the shared
  factoryalias.Normalize contract (60 runes; letters, digits, spaces,
  '-', '_', '.'; case-insensitive uniqueness).
- Activity's terminal stage really is labeled 'Complete' while the Slack
  Home tab uses 'Completed' (slack_app_home.go) — both pages correctly
  reflect their own surface, so the apparent mismatch stands.

Aligned:
- factory-as-code: bridge the alias key to its control-room label,
  Foreman name (#559 introduced the label in the quickstart), and say
  it @-mentions the foreman, matching the UI copy.
- control-room Settings: name the identity fields (name, avatar,
  Foreman name) and link Foreman name to the alias reference.
- run-a-software-factory-in-the-cloud: DIY-loop runs appear in the
  cloud agent dashboard, not the Factories product's dashboard — use
  {VARS.DASHBOARD}.
- The five DIY-factory guides framed the Factories product page as 'the
  conceptual overview of the full loop'; their next-step descriptions
  now say what the destination is (the managed product), and
  build-a-self-improving-agent deep-links the Self-improvement section
  it parallels (the reverse link already existed).
- set-up-a-software-factory and run-a-software-factory-in-the-cloud
  intros now point readers to Warp Factories as the managed alternative.

Validated: npm run build passes; link checker 3,664 internal / 1,522
external, 0 broken; style_lint adds no new findings on touched files.

Co-authored-by: hongyi-chen <hongyigma@gmail.com>
Co-authored-by: Warp <agent@warp.dev>
Co-authored-by: Hong Yi Chen <hongyi@warp.dev>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants