Spec schema
A specification version of a product or agent built with Trovensa has one section per stage id from
forge.config.json stages[]. Section keys are exactly discovery, preclinical, clinical and
manufacturing, in stage order. Statuses follow the plan lifecycle draft -> review -> approved ->
archived; approved versions are immutable and a new version returns to draft. Every acceptance
criterion is an observable check that tests reference as <stage_id>#<index>.
Header
Spec: <spec name> | Version: <n> | Status: draft | Date: <YYYY-MM-DD> | Source: <generated | edited>Summary
Two to four sentences: what is being specified and for whom. Logged, not stored with the version.
Stage blocks
Each of the four blocks carries the same seven parts.
| Part | Content | Rule |
|---|---|---|
| Objective | one or two sentences on what the stage must achieve | must not be blank |
| Requirements | numbered, concrete, testable | at least one |
| Decisions | “X because Y” lines | may be empty |
| Artifacts | deliverables with their path or location | may be empty |
| Acceptance criteria | numbered observable checks, referenced as <stage_id>#<index> | at least one |
| Risks | “risk - mitigation” lines | may be empty |
| Notes | free-form or “none” |
discovery - Discovery
Questions, sources and findings that frame the program; hypotheses proposed and decided; gaps addressed.
preclinical - Preclinical development
Plans, protocols and experiments for preclinical work; reports drafted and approved; SOP checks on protocols.
clinical - Clinical development
Clinical plans and protocols, experiment and report records, review checks and deviations, milestones with approvals.
manufacturing - Manufacturing planning
Manufacturing planning: milestones, dependencies (blocks, informs), open items and approvals owned by the manufacturing specialist.
Plan
The building blocks the product or agent needs, each tied to one stage id. Prefer the exact name of an existing organisation record when one fits.
| Name | Kind | Purpose | Stage |
|---|---|---|---|
<name> | <tool, connection, agent run kind, ...> | <why it is needed> | <stage_id> |
Status history
| Date | From | To | By |
|---|---|---|---|
<YYYY-MM-DD> | - | draft | <who> |
Source: forge.config.json, PRODUCT-CONTRACT.md, api/app/db/models/plans.py