Handbook
STI schemas
Architecture-ready JSON Schema stubs live in the product repo at schemas/. Runtime validation (LCDL contract.schema, consumer gates) lands in follow-on phases.
Updated
test_case.v1
File: schemas/test_case.v1.schema.json
Sample: schemas/samples/test_case.sample.json
Atomic test case: id (tc_*), level, intent, steps, oracle (prefer subprocess/schema over llm_gate), trace links to requirements/stories/defects.
test_suite.v1
File: schemas/test_suite.v1.schema.json
Sample: schemas/samples/test_suite.sample.json
Groups case ids (ts_* → tc_*), exit criteria, environment hints.
test_run_summary.v1
File: schemas/test_run_summary.v1.schema.json
Sample: schemas/samples/test_run_summary.sample.json
Campaign result for EvidencePacket attach: counts, status, optional forge_run_id and fleet_job_id.
ForgeRun attach (planned)
Platform extension fields will reference these schema ids under evidence without forking forge_run.v1.schema.json.
Editing policy
Schema changes require handbook update in this page and a version bump (test_case.v2 when breaking). One commit in sti; rebuild stiw submodule after publish.