feat(solicitation-create): ACE owns composition; labs validates schema#398
Merged
Conversation
Walks back the "future labs-side create_solicitation_from_brief" direction floated in the previous PR. Operator chose to keep composition in ACE so this skill retains full control over voice, archetype-branched scope, framing/scoring_guide quality, and decisions-log integration (all ACE-context that labs would have to learn). Labs's tightened MCP (2026-05-22 deploy) is the right server-side contribution: create_solicitation + update_solicitation now validate the canonical schema and fail loudly with INVALID_SCHEMA + error.details.fields keyed by JSON-path (e.g. evaluation_criteria[0].linked_questions). Schema enforcement, not content generation. Changes: - New top-level design-principle callout at the start of ## Process: "ACE owns composition; labs validates the schema." Documents the contract + how to read INVALID_SCHEMA responses + when to re-read tools/list inputSchema as the source-of-truth. - Step 6's payload-rejection paragraph updated: labs now rejects unknown top-level fields at write time (post-deploy); error.details surfaces the offending field path. Do not retry with the same payload; do not stuff extras into free-form fields. - Change Log entry removes the "Removal criteria: keep until labs ships create_solicitation_from_brief" line from PR #396 — this skill is the long-term home for solicitation composition. Co-Authored-By: Claude Opus 4.7 <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.
Summary
Walks back the "future labs-side `create_solicitation_from_brief`" direction from PR #396. Operator decided to keep composition in ACE so this skill retains full control over voice, archetype branching, scope transformation from the work order, question framings, evaluation `scoring_guide`s, and decisions-log integration.
Labs's tightened MCP (forthcoming 2026-05-22 deploy) is the right server-side contribution: `create_solicitation` + `update_solicitation` now validate the canonical schema and fail loudly with `INVALID_SCHEMA` + `error.details.fields` keyed by JSON-path (e.g. `evaluation_criteria[0].linked_questions`). Schema enforcement, not content generation.
Changes
New top-level design-principle callout at the start of `## Process`:
Plus operational guidance for reading `INVALID_SCHEMA` responses and refreshing the schema against `tools/list` when this SKILL.md is stale relative to a recent labs deploy.
Step 6's payload-rejection paragraph updated: labs now rejects unknown top-level fields at write time (post-deploy); `error.details.fields` surfaces the offending JSON path. Don't retry with the same payload; don't stuff extras into free-form fields.
Change Log entry removes the "Removal criteria: keep until labs ships `create_solicitation_from_brief`" line from PR feat(solicitation-create): work-order-as-input + canonical labs schema + comprehensive content shape #396. This skill is the long-term home for solicitation composition.
Test plan
🤖 Generated with Claude Code