feat(eval): add evidence pipeline acceptance closure

This commit is contained in:
aruo
2026-07-09 00:47:48 +08:00
parent a77c947cd4
commit db0f229285
46 changed files with 1434 additions and 53 deletions
@@ -98,3 +98,17 @@ without requiring raw JSON inspection first.
planner `read_skill` text mentions, executor `read_skill` text mentions, and
verifier `read_skill` text mentions
### Requirement: MVP demo SHALL provide stable evidence-pipeline scenarios
The MVP demo SHALL provide stable scenarios that explain how to demonstrate positive evidence, no-evidence, and safety/reject behavior for an Agent engineering interview.
#### Scenario: Scenario guide maps demo inputs to evidence claims
- **WHEN** a reviewer opens the demo scenario guide
- **THEN** it SHALL list the supported positive, no-evidence, and safety/reject scenarios
- **AND** it SHALL map each scenario to a request payload or fixture id
- **AND** it SHALL describe the expected Gatekeeper, Verifier, Composer, and trace fields to inspect
#### Scenario: Live and fixture-backed scenarios are distinguished
- **WHEN** a demo scenario is fixture-backed rather than live-scripted
- **THEN** the documentation SHALL say so explicitly
- **AND** it SHALL avoid promising deterministic live LLM output for that scenario