Automotive Programs

TRF helps automotive OEMs and suppliers coordinate evidence across long, multi-tier development programs.

Program phases

Phase	Evidence focus	TRF artifacts
Concept / item definition	Vehicle-level goals, hazards, stakeholder requirements	item_definition, hazard, safety_goal, requirement
System development	Architectures, interface contracts, allocation of safety mechanisms	design, component, safety_requirement, safety_mechanism
Software/hardware development	Module design, implementation, unit/integration tests	design, component, test, build_info
Verification & validation	System tests, scenario coverage, evidence for audits	test, coverage reports, assessment_finding
Production & service	Work instructions, maintenance plans, incident reports	work_instruction, maintenance_plan, incident_report

Supplier integration

• Request suppliers deliver signed TWPack files for their subsystems.
• Import supplier packs using tw merge supplier.twpack and maintain provenance via signatures.
• Link supplier evidence to OEM-level hazards and requirements to preserve end-to-end chain of custody.

Change management

• Record change requests as artifacts (change_request) linking impacted requirements/tests.
• Use tw diff between releases to highlight evidence deltas for gate reviews.
• Tag artifacts with release identifiers (tags: ["R2024.3"]) to track inclusion.

Toolchain ecosystem

• Integrate requirement tools (DOORS, Jama) through export scripts that write JSONL.
• Connect test management (VectorCAST, dSPACE) via --links-from adapters.
• Store calibration, diagnostic, and vehicle logs as attachments with hashes for authenticity.

Combine this domain guide with the regulatory pages for ISO 26262, Automotive SPICE, and UN-R155/R156.