Back to Details

eval-business-logic

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Business Logic Evaluator Agent

业务逻辑评估Agent

Specialized evaluator for tracks that implement core product logic — generation pipelines, state machines, pricing, or other business-rule-heavy features.
专为实现核心产品逻辑的track设计的专用评估器，覆盖生成流水线、状态机、定价或其他强业务规则类功能。

When This Evaluator Is Used

本评估器的适用场景

Dispatched by 
loop-execution-evaluator
when the track involves:
  • Core product pipeline logic
  • State machine or workflow systems
  • Pricing tier enforcement
  • Dependency resolution between deliverables
  • Download or packaging features
当track包含以下内容时，会由
loop-execution-evaluator
调度本评估器：
  • 核心产品流水线逻辑
  • 状态机或工作流系统
  • 定价层级管控
  • 交付物之间的依赖解析
  • 下载或打包功能

Inputs Required

所需输入

  1. Track's 
    spec.md
    and 
    plan.md
  2. conductor/product.md
    — product rules (deliverables, tiers, dependencies)
  3. Project-specific pipeline/prompt configurations (if applicable)
  4. Data definition files (e.g., asset definitions, feature configs)
  5. Implementation code being evaluated
  1. track的
    spec.md
    和
    plan.md
    文件
  2. conductor/product.md
    —— 产品规则（交付物、层级、依赖）
  3. 项目专属的流水线/提示词配置（如有）
  4. 数据定义文件（如资产定义、功能配置）
  5. 待评估的实现代码

Evaluation Passes (6 checks)

评估环节（共6项检查）

Pass 1: Product Rules Compliance

环节1：产品规则合规性

Check against rules defined in 
conductor/product.md
:
RuleWhat to Verify
DeliverablesAll defined deliverables are implemented and functional
DependenciesEach deliverable's dependencies are correctly enforced
Processing orderSequential processing respects dependency chain
Tier systemFree tier limitations enforced, paid tier unlocks correct features
PricingPricing model matches product spec (one-time, subscription, etc.)
State rulesState transitions (e.g., lock/unlock, draft/publish) propagate correctly
markdown
undefined
对照
conductor/product.md
中定义的规则做检查：
规则校验内容
交付物所有定义的交付物均已实现且功能正常
依赖每个交付物的依赖都得到正确管控
处理顺序顺序处理逻辑符合依赖链要求
层级体系免费版限制已生效，付费版正确解锁对应功能
定价定价模式与产品规范一致（一次性付费、订阅制等）
状态规则状态流转（如锁定/解锁、草稿/发布）可正确传播
markdown
undefined

Product Rules: PASS / FAIL

Product Rules: PASS / FAIL

  • Rules checked: [count]
  • Violations: [list rule: actual behavior]
  • Deliverables functional: [X]/[total]
undefined
  • Rules checked: [count]
  • Violations: [list rule: actual behavior]
  • Deliverables functional: [X]/[total]
undefined

Pass 2: Feature Correctness

环节2：功能正确性

For each feature in the spec, verify it works correctly:
CheckMethod
Happy pathPrimary user flow produces expected result
Input validationInvalid inputs rejected with clear messaging
Output correctnessGenerated data matches expected format/structure
State mutationsState changes are correct and complete
Side effectsDownstream effects trigger correctly (e.g., dependency propagation)
markdown
undefined
对规范中定义的每个功能，校验其运行是否正确：
检查项校验方式
正常路径主用户流程可产出预期结果
输入校验无效输入会被拒绝，并返回清晰提示
输出正确性生成的数据符合预期格式/结构
状态变更状态变更正确且完整
副作用下游影响可正确触发（如依赖传播）
markdown
undefined

Feature Correctness: PASS / FAIL

Feature Correctness: PASS / FAIL

  • Features tested: [count]
  • Correct: [count]
  • Failures: [describe each]
undefined
  • Features tested: [count]
  • Correct: [count]
  • Failures: [describe each]
undefined

Pass 3: Edge Cases

环节3：边界用例

ScenarioWhat to Verify
Empty stateFirst-time user with no data
Boundary valuesMax input length, empty inputs, special characters
Concurrent operationsWhat happens if user triggers 2 operations at once
Network failure mid-operationPartial state handled correctly
Re-processingRe-running an operation on existing data prompts confirmation if needed
All items locked/finalizedUI reflects that no further changes are possible
Tier limitsExceeding free tier limit shows upgrade prompt
markdown
undefined
场景校验内容
空状态首次使用无数据的新用户场景
边界值最大输入长度、空输入、特殊字符
并发操作用户同时触发2个操作时的表现
操作中途网络故障可正确处理部分完成的状态
重复处理对已有数据重新运行操作时，按需触发确认提示
所有条目已锁定/最终化UI正确展示无法再编辑的状态
层级限制超出免费版限制时展示升级提示
markdown
undefined

Edge Cases: PASS / FAIL

Edge Cases: PASS / FAIL

  • Scenarios checked: [count]
  • Unhandled: [list]
  • User impact: [describe]
undefined
  • Scenarios checked: [count]
  • Unhandled: [list]
  • User impact: [describe]
undefined

Pass 4: State Transitions

环节4：状态流转

Verify state machine correctness for your project's state model. Example pattern:
StateValid Transitions
empty
→ 
processing
(when user triggers action)
processing
→ 
ready
(success) or 
error
(failure)
ready
→ 
locked
(user finalizes) or 
processing
(re-process)
locked
→ 
outdated
(dependency changed) or 
ready
(unlock)
outdated
→ 
processing
(user re-processes)
error
→ 
processing
(retry)
Adapt the state table above to match your project's actual states.
markdown
undefined
针对项目的状态模型校验状态机正确性，示例模式如下：
状态合法流转路径
empty
→ 
processing
（用户触发操作时）
processing
→ 
ready
（成功）或 
error
（失败）
ready
→ 
locked
（用户最终确认）或 
processing
（重新处理）
locked
→ 
outdated
（依赖发生变更）或 
ready
（解锁）
outdated
→ 
processing
（用户重新处理）
error
→ 
processing
（重试）
请根据项目实际状态调整上方状态表。
markdown
undefined

State Transitions: PASS / FAIL

State Transitions: PASS / FAIL

  • States implemented: [list]
  • Invalid transitions possible: [list]
  • Missing transitions: [list]
undefined
  • States implemented: [list]
  • Invalid transitions possible: [list]
  • Missing transitions: [list]
undefined

Pass 5: Data Flow

环节5：数据流

CheckWhat to Verify
Input → ProcessingUser form data correctly feeds into processing pipeline
Processing → OutputResults stored/displayed correctly
Output → PersistenceResults saved to store/database
Cross-componentData shared correctly between components
Stale dataNo stale renders after state changes
markdown
undefined
检查项校验内容
输入→处理用户表单数据可正确传入处理流水线
处理→输出结果可正确存储/展示
输出→持久化结果可保存到存储/数据库
跨组件组件间数据共享正确
陈旧数据状态变更后无陈旧渲染问题
markdown
undefined

Data Flow: PASS / FAIL

Data Flow: PASS / FAIL

  • Flow verified: [input → output]
  • Stale data issues: [describe]
  • Data loss points: [list]
undefined
  • Flow verified: [input → output]
  • Stale data issues: [describe]
  • Data loss points: [list]
undefined

Pass 6: User Journey Completeness

环节6：用户旅程完整性

Walk through the complete user journey for the feature under evaluation. Example structure:
1. User provides input (form, selection, etc.)
2. System processes input
3. User reviews output
4. User can lock/finalize results
5. System handles dependencies between outputs
6. User views all deliverables
7. User can export/download results
8. User can re-process any unlocked item
9. Locked items show "outdated" if dependencies change
Adapt the journey steps above to match your project's actual user flow.
markdown
undefined
遍历待评估功能的完整用户旅程，示例结构如下：
1. User provides input (form, selection, etc.)
2. System processes input
3. User reviews output
4. User can lock/finalize results
5. System handles dependencies between outputs
6. User views all deliverables
7. User can export/download results
8. User can re-process any unlocked item
9. Locked items show "outdated" if dependencies change
请根据项目实际用户流程调整上方旅程步骤。
markdown
undefined

User Journey: PASS / FAIL

User Journey: PASS / FAIL

  • Steps completed: [X]/[total]
  • Broken at step: [which]
  • User experience: [smooth / friction at: describe]
undefined
  • Steps completed: [X]/[total]
  • Broken at step: [which]
  • User experience: [smooth / friction at: describe]
undefined

Verdict Template

结论模板

markdown
undefined
markdown
undefined

Business Logic Evaluation Report

Business Logic Evaluation Report

Track: [track-id] Evaluator: eval-business-logic Date: [YYYY-MM-DD]
Track: [track-id] Evaluator: eval-business-logic Date: [YYYY-MM-DD]

Results

Results

PassStatusIssues
1. Product RulesPASS/FAIL[details]
2. Feature CorrectnessPASS/FAIL[details]
3. Edge CasesPASS/FAIL[details]
4. State TransitionsPASS/FAIL[details]
5. Data FlowPASS/FAIL[details]
6. User JourneyPASS/FAIL[details]
PassStatusIssues
1. Product RulesPASS/FAIL[details]
2. Feature CorrectnessPASS/FAIL[details]
3. Edge CasesPASS/FAIL[details]
4. State TransitionsPASS/FAIL[details]
5. Data FlowPASS/FAIL[details]
6. User JourneyPASS/FAIL[details]

Verdict: PASS / FAIL

Verdict: PASS / FAIL

[If FAIL, list specific fix actions for loop-fixer]
undefined
[If FAIL, list specific fix actions for loop-fixer]
undefined

Handoff

流转规则

  • PASS → Return to 
    loop-execution-evaluator
    → Conductor marks complete
  • FAIL → Return to 
    loop-execution-evaluator
    → Conductor dispatches 
    loop-fixer
  • 通过 → 返回至
    loop-execution-evaluator
    → Conductor标记为完成
  • 未通过 → 返回至
    loop-execution-evaluator
    → Conductor调度
    loop-fixer