docs(demo): scope statement + serial-flow wording in squad demo (WS-592)#5640
Open
josonzhao wants to merge 1 commit into
Open
docs(demo): scope statement + serial-flow wording in squad demo (WS-592)#5640josonzhao wants to merge 1 commit into
josonzhao wants to merge 1 commit into
Conversation
WS-584 follow-up: apply the 2 wording fixes from the WS-589 product walkthrough to docs/demo/squad-collaboration.md, plus 1 adjacent cross-ref fix. - §1: add a scope statement clarifying this demo covers single-workspace multi-agent collaboration (leader orchestration + member specialization + observable handoff); the WS-567 cross-employee remote-agent endpoint + messaging protocol is a separate blocked 2-week P0 MVP, out of scope (优化点 1, 方案 A). - §2 value table: "并行的专项工作 + leader 级编排" -> "专项化工作 + leader 编排", matching the actual serial pipeline (架构 -> 编码 -> 测试 -> 文档) rather than claiming parallelism the demo does not exhibit (优化点 2). - §2 note: fix wrong cross-reference "见 §8 局限" -> "见 §10 局限" (局限 is §10; §8 is the single-agent vs squad comparison). Disclosed adjacent fix, since the new §1 scope note also references §10 and the inconsistency would otherwise be glaring. Also commits the previously untracked demo dir (squad-collaboration.md + seed-squad-demo.sh) delivered by WS-584; seed-squad-demo.sh is unchanged. Co-authored-by: multica-agent <github@multica.ai>
|
Someone is attempting to deploy a commit to the IndexLabs Team on Vercel. A member of the Team first needs to authorize it. |
multica-eve
reviewed
Jul 19, 2026
multica-eve
left a comment
Collaborator
There was a problem hiding this comment.
Thanks for the contribution. We cannot merge this as public repository documentation: it is a workspace-specific operational runbook that relies on pre-existing, hard-coded agent names and internal WS references, and it creates or modifies live workspace data. Those assumptions do not hold for general Multica users and would leave an internal demo workflow to maintain in the OSS docs. Please keep this material in the appropriate internal/demo environment rather than revising this PR for merge.
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
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.
Summary
Lands the WS-584 squad demo doc + script (
docs/demo/squad-collaboration.md,docs/demo/seed-squad-demo.sh) and applies the 2 wording fixes from the WS-589 product walkthrough follow-up (WS-592).The demo files were previously only workspace artifacts (never committed to the repo); this PR commits them with the WS-592 fixes already applied.
Changes
并行的专项工作 + leader 级编排→专项化工作 + leader 编排, matching the actual serial pipeline (架构 → 编码 → 测试 → 文档) rather than claiming parallelism the demo does not exhibit.见 §8 局限→见 §10 局限(局限 is §10; §8 is the single-agent vs squad comparison).Verification
seed-squad-demo.shis unchanged; idempotency was already re-verified in the WS-589 walkthrough.Refs