docs(factories): document that factories and the Oz web app coexist - #564
Closed
hongyi-chen wants to merge 2 commits into
Closed
docs(factories): document that factories and the Oz web app coexist#564hongyi-chen wants to merge 2 commits into
hongyi-chen wants to merge 2 commits into
Conversation
Aloke's soft-launch note to sales spells out three things a customer will experience that the docs never said: both the Slack and Linear integrations keep working after a factory exists, the two surfaces run side by side, and a factory enabled for a Linear team takes precedence over the legacy integration. The factories docs currently describe factories as though Oz v1 doesn't exist, and the platform Slack and Linear pages never mention factories at all, so the customer with both has no page written for them. - platform Slack and Linear: add a 'Factories and this integration' section. Slack has no conflict, since each factory installs its own app; Linear does, so that page states the precedence rule. - factories Linear: lead with precedence rather than framing it as a fallback, which read as though the legacy integration were primary. - factories overview: place the two web apps side by side and say plainly that creating a factory changes nothing you already run. Precedence is grounded in replaysBuiltInWhenUnclaimed in logic/ai/ambient_agents/webhook/workflow.go: a delivery with zero matched factory actions falls back to the provider's built-in behavior, so a matched one does not. No migration or consolidation timeline is mentioned, per Aloke's note not to communicate that yet. Co-Authored-By: Warp <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Collaborator
Author
|
This PR was generated with Warp. Comment   |
|
Your GitHub account is not connected to Warp. Connect it here. |
Contributor
|
Your Warp account is not a member of any team with access to this repository. |
…ctories-oz-v1-coexistence
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes the gap between what Aloke told sales the soft launch would look like and what the docs actually say.
His note spells out three customer-visible facts. The docs covered one of them.
What was missing
The launch stack documents factories as though Oz v1 doesn't exist.
git grepacross all ofsrc/content/docs/factories/foroz.warp.dev, "Oz v1", or "legacy" returned nothing, and neitherplatform/integrations/slack.mdxnorplatform/integrations/linear.mdxmentioned factories at all. The customer Aloke is preparing sales for — one who has both — had no page written for them.Only the
oz→warphandle rename was already handled, by #542.Changes
platform/integrations/linear.mdxandplatform/integrations/slack.mdx— new "Factories and this integration" section on each. The two cases differ, so the copy does too: Slack has no conflict because each factory installs its own app carrying the factory's name, while Linear genuinely overlaps, so that page states the precedence rule.factories/integrations/linear.mdx— the precedence sentence led with the fallback ("if a session doesn't match any automation, the Linear integration handles it with its default behavior"), which reads as though the legacy integration were primary. Now leads with precedence and keeps the fallback as the tail.factories/index.mdx— places the two web apps side by side and says plainly that creating a factory changes nothing you already run.On accuracy
The precedence claim is grounded in code rather than in the Slack message.
replaysBuiltInWhenUnclaimedinlogic/ai/ambient_agents/webhook/workflow.godocuments an unclaimed delivery as one with "zero matched Factory actions", which then falls back to the provider's built-in behavior — so a matched delivery does not. That's the same rule from the other direction.The Slack wording deliberately avoids claiming precedence, because per
factories/integrations/slack.mdxeach factory gets its own dedicated app, so nothing competes for a single mention.No migration or consolidation timeline appears anywhere in this PR, per Aloke's note not to communicate that yet.
Verification
npm run buildexits 0, with only the pre-existing/404route-priority warningstyle_lint --changedreports 0 errors across the four files; remaining warnings are pre-existing (screenshot-width, bolded UI labels, one Title Case header)VARSexpressions resolve to real text and URLs rather than literal tokens, and that/factories/exists as a link target