feat(selling): 统一候选规格口径并强制候选间规格分层 - #193
Open
ruanzhengxin-zhuxing wants to merge 1 commit into
Open
Conversation
在售卖 pipeline 三个阶段间建立规格一致性约束，解决候选资源规格在 规划-描述-成本实测间不一致、规格变更未记录理由、候选间缺乏规格分层的问题： - architecture_planning: conclusion_schema 新增 planned_specs 规格基线字段， SKILL/prompt 要求多候选按定位做 ECS/RDS 规格分层，禁止候选核心规格完全一致 - template_generating: conclusion_schema 新增 described_specs，要求面向用户 描述规格与模板落地资源规格一致，沿用 planned_specs 基线 - cost_estimating: conclusion_schema 新增 spec_reconciliation，要求逐资源核对 实测规格与计划/描述规格，偏离计划时记录 change_reason 否则回退计划规格 - 同步更新三个 skill 的单测断言 Aone: 84592949
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.
背景
Aone #84592949 —— 候选资源规格在规划(architecture_planning)、描述(template_generating)与成本实测(cost_estimating)间不一致，规格变更未记录理由，且候选间缺乏规格分层。
改动（均在 iac-code 售卖 pipeline）
planned_specs规格基线字段；SKILL/prompt 要求多候选按定位做 ECS/RDS 规格分层，禁止候选核心规格完全一致。described_specs；要求面向用户描述规格与模板落地资源规格一致，沿用 planned_specs 基线。spec_reconciliation；逐资源核对实测规格与计划/描述规格，偏离计划时记录change_reason，否则回退计划规格。验证
tests/pipeline/selling/358 passed。