31 lines
1.7 KiB
Markdown
31 lines
1.7 KiB
Markdown
## ADDED Requirements
|
|
|
|
### Requirement: MVP demo SHALL provide an interview runbook
|
|
The MVP demo SHALL include a concise interview runbook that explains how to demonstrate the Agent flow and how to narrate the engineering value.
|
|
|
|
#### Scenario: Walkthrough explains the demo story
|
|
- **WHEN** a developer opens the interview walkthrough
|
|
- **THEN** it SHALL explain the user question, Agent flow, evidence tools, verifier judgment, trace API, feedback, and eval baseline connection
|
|
|
|
#### Scenario: Walkthrough stays scoped to existing capabilities
|
|
- **WHEN** the walkthrough describes the demo
|
|
- **THEN** it SHALL avoid claiming unsupported runtime behavior or new production features
|
|
|
|
### Requirement: MVP demo SHALL provide executable local demo scripts
|
|
The MVP demo SHALL provide scripts and request payloads for running the payment-timeout case through existing local APIs.
|
|
|
|
#### Scenario: Demo script sends the fixed diagnosis request
|
|
- **WHEN** the demo script is executed against a running local service
|
|
- **THEN** it SHALL send the fixed payment-timeout chat request with a stable session id
|
|
|
|
#### Scenario: Demo script captures review artifacts
|
|
- **WHEN** the demo script finishes successfully
|
|
- **THEN** it SHALL write chat, trace, and feedback responses under a demo output directory
|
|
|
|
### Requirement: MVP demo SHALL provide a trace inspection checklist
|
|
The MVP demo SHALL document which trace fields to inspect for evidence, verifier behavior, and session-level auditability.
|
|
|
|
#### Scenario: Checklist maps fields to interview claims
|
|
- **WHEN** a developer reviews a trace response
|
|
- **THEN** the checklist SHALL map concrete JSON paths to the claims made in the interview walkthrough
|