# SDLC work-product seed

Regenerates every ISO/IEC 29110 work product under `sdlc/` from controlled project
data, in the layout of the audited `200-TAS-25-001-00` reference package: Thai
section headings, a `Document No` control block, and Secretary / Reviewer /
Approval signature tables on every document.

`sdlc/` is generated output. Edit the data files here, never the Markdown.

## Files

| File | Contents |
|---|---|
| `project.mjs` | People, dates, project code, scope, deliverables, Customer Requirements (CR01–CR14) |
| `engineering.mjs` | Software Requirements (SR01–SR09), Software Units, Test Cases, and the CR→SR→Unit→Test mapping |
| `history.mjs` | Work Schedule, reporting periods, meetings, Correction Register, Change Reports |
| `lib.mjs` | Buddhist-calendar dates, Markdown tables, signature blocks |
| `format.mjs` | The shared work-product scaffold |
| `docs-*.mjs` | One generator per work product |
| `build.mjs` | Writes all documents and checks no folder is left empty |

## Usage

```bash
node scripts/sdlc-seed/build.mjs      # regenerate sdlc/ only
bash scripts/build-sdlc-delivery.sh   # seed, render to PDF, then verify
```

The traceability chain is validated at import time: every Customer Requirement
must resolve to existing Software Requirements, Software Units, and a Test Case,
or the build fails.