DocGen Solutions — per-org index¶
One folder per organization (tenant). Every org is a multi-tenant slice of the same DocGen engine; its folder holds that org's solution docs (PRD/TDD where written) and points to its template spec in docgen/src/docgen/authoring/specs/. Org wiring lives in docgen/src/docgen/fixtures/orgs.py.
Shared, cross-cutting reference (formulas, gap maps, gold data, the demo-app guide) stays in ../reference/ — solution folders link to it rather than copy it.
Built orgs¶
| Org (slug) | Use case | Template spec / seed | Docs |
|---|---|---|---|
odyssey |
Phoenix firm-order memo (reinsurance) | odyssey-phoenix-firm-order.json (+ -spec.json) |
prd · tdd |
tomorrow-law |
JBRK estate reporting letter | fixtures/jbrk.py (Python seed) |
prd · tdd |
goa |
Public-figure background check | goa-background-check.json |
README |
altaml |
DealDesk PoV proposal + SOW | altaml-dealdesk-proposal.json + altaml-dealdesk-sow.json |
README |
vertical-scope |
Carbon Media proposal | vs-carbon-media-proposal.json |
README |
Candidates (assessed for DocGen fit — not built)¶
| Client | Verdict | Doc |
|---|---|---|
| NAIT | ❌ Phase-1 gap analysis is a classification grid, not a document template; the Phase-2 Content Feeder is the fit | _candidates/nait.md |
| SITE Resource Group | ✅ strong fit — subcontractor RFP scope-of-work = document-in-a-template | _candidates/site-resource-group.md |
Fit discriminator: a deliverable that is a document in a template → fit; a classification / comparison grid → not a fit.