• Canonical ownership: generated

Functional Spec

• Story: story-vibepro-bug-diagnosis-dag
• Status: -
• Clauses: 6

C-001

A bug Story diagnosis artifact records its Story id, run id, target HEAD, and all ordered node results in the durable process-record store. Derived Stories preserve their inferred bug contract type. Every accepted node must be bound to that target HEAD, and PR preparation rejects evidence for an older HEAD.

Origin refs

C-002

The execution DAG connects every bug diagnosis node between implementation_started and implementation_complete before existing verification and review nodes.

Origin refs

C-003

A blocked diagnosis reports the first unmet node as return_to_node and provides a next action bound to the Story and run.

Origin refs

C-004

The deprecated verify-first command accepts only registered bug Stories and delegates to the same story diagnosis implementation without creating a second DAG.

Origin refs

INV-001

A bug Story remains blocked until reproduction, root cause, regression proof or justified inapplicability, root fix, and same-path reverification are accepted in order.

Origin refs

S-001

When unit verification passes but reproduction evidence is missing, pr prepare persists blocked and pr create refuses the PR.

Origin refs

Diagrams

flow

flowchart LR Story[Bug Story] --> Diagnose[Diagnosis nodes] Diagnose --> Implementation[Implementation complete] Implementation --> Verify[Verification] Verify --> Review[Review] Review --> PR[PR create]