# CASAN Manifest-Driven Delivery Flow

The production flow is selected by `apps/<project>/domain/project.manifest.json` and is identical
for every registered project:

```text
manifest validation
  → SRS → business design → specification → spec review
  → plan → plan review/retry → detailed design → test design
  → tasks → implementation draft → code review/retry
  → manifest build + test → evidence → release candidate
```

All generation steps preserve requirement IDs from the selected requirement document. Review
steps use the selected quality profile. Build/test and post-patch verification execute only argv
arrays declared by the manifest. Rejected reviews return to the owning generation step with a
bounded retry; verification failure rolls back the approved patch. Application deployment is a
separate environment adapter and must define workload identity, health checks, and rollback.

Run:

```bash
bin/casan project validate --manifest apps/<project>/domain/project.manifest.json
bin/casan pipeline --manifest apps/<project>/domain/project.manifest.json
```