docs(orchestrate): guard StructuredOutput cap + producer/consumer ownership#330
Merged
Conversation
…ership
Two failure modes from a real model-tiered build, folded into the skill:
- StructuredOutput-cap caveat (Step 1 sizing): an oversized agent({schema})
item can exhaust the 5-retry cap and throw, aborting its whole sequential
group so later items never run. Mitigations: split, drop the schema, or
isolate it in its own single-item group. Matching Stop Conditions line.
- Data-flow ownership rule ("Group by file ownership"): ownership must cover
the producer<->consumer pair of every new cross-cutting symbol, not just
edited files, or the integration silently no-ops while tests still pass.
- Fresh-eyes /rereview-loop note for trust-core changes (Step 3).
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
- Replace undefined "trust-core" jargon with "high-stakes / cross-cutting". - Make the cap-abort pipeline semantics precise (group entry drops to null, verify skipped) instead of vague "stage drops to null". - Broaden the ownership check to cover wiring, not just a producer's existence; soften "ships dead" → "ships broken". - Clarify it is the item's output (not the schema) that is oversized. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
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.
Fold two failure modes from a real model-tiered build into the /orchestrate skill:
exhaust the Workflow tool's 5-attempt retry cap and throw, aborting its whole
sequential group so later items never run. Added sizing guidance (split, drop
the schema, or isolate it in its own single-item group) plus a matching Stop
Conditions bullet.
pair of every new cross-cutting symbol, not just edited files, or the
integration silently no-ops while tests still pass.
Co-Authored-By: Claude noreply@anthropic.com