Decision owner
Chief engineer and systems authority
The named role remains accountable for the consequential decision.
Automotive & Mobility
Designed for Systems engineer
Keep automotive systems requirements traceable and testable by linking each requirement to design decisions, verification cases, and applicable regulations, with engineering review before a baseline is frozen.
Contract AUT-02 · primary aggregate RequirementBaseline · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Chief engineer and systems authority
The named role remains accountable for the consequential decision.
Governed evidence
5 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
1 approval gate
Approval gates prevent the copilot from making consequential decisions.
Ahead of a design freeze the copilot shows that 14 ASIL-C braking requirements have no passing verification case, links three of them to a superseded design decision on pedal feel, surfaces a newly effective UN regulation clause for the European market with no allocated requirement, and the chief engineer withholds the freeze until the gaps are closed..
Keep automotive systems requirements traceable and testable by linking each requirement to design decisions, verification cases, and applicable regulations, with engineering review before a baseline is frozen.
Frozen baseline released to development partners gives Chief engineer and systems authority the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Chief engineer and systems authority verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Systems engineer performs author or import the requirement using Requirement text with allocation and verification method and produces SystemRequirement in the working baseline. The transition is deterministic and does not require autonomous model approval.
Why it matters: SystemRequirement in the working baseline gives Requirement quality agent the evidence needed to begin Check quality, ambiguity, and duplication, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/author-or-import-the-requirement
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Requirement quality agent performs check quality, ambiguity, and duplication using Requirement text and existing baseline and produces Quality findings and near-duplicate candidates. The transition is deterministic and does not require autonomous model approval.
Why it matters: Quality findings and near-duplicate candidates gives Traceability agent the evidence needed to begin Link regulations and design decisions, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/check-quality-ambiguity-and-duplication
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Traceability agent performs link regulations and design decisions using Requirement, regulation clauses, decision records and produces Bidirectional trace links with confidence. The transition is deterministic and does not require autonomous model approval.
Why it matters: Bidirectional trace links with confidence gives Verification analytics service the evidence needed to begin Assess verification coverage, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/link-regulations-and-design-decisions
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Verification analytics service performs assess verification coverage using Requirements and verification cases and produces Coverage report with unverified requirements. The transition is deterministic and does not require autonomous model approval.
Why it matters: Coverage report with unverified requirements gives Chief engineer and systems authority the evidence needed to begin Freeze the baseline, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/assess-verification-coverage
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Chief engineer and systems authority performs freeze the baseline using Coverage report and open change requests and produces Frozen baseline released to development partners. A named human approver must review the evidence before the transition completes.
Why it matters: Frozen baseline released to development partners gives Chief engineer and systems authority the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/freeze-the-baseline
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved RequirementBaseline evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
requirementBaselines/tenantId + /vehicleProgramIdAhead of a design freeze the copilot shows that 14 ASIL-C braking requirements have no passing verification case, links three of them to a superseded design decision on pedal feel, surfaces a newly effective UN regulation clause for the European market with no allocated requirement, and the chief engineer withholds the freeze until the gaps are closed.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
requirementBaselines |
Primary | /tenantId + /vehicleProgramId |
RequirementBaseline, SystemRequirement, DesignDecisionRecord, VerificationCase |
homologationRegulationLibrary |
Reference | /tenantId + /marketCode |
RegulatoryRequirementClause |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
RequirementBaseline |
requirementBaselines |
/tenantId + /vehicleProgramId |
baseline::{vehicleProgramId}::{baselineLabel} |
None |
SystemRequirement |
requirementBaselines |
/tenantId + /vehicleProgramId |
requirement::{vehicleProgramId}::{requirementId} |
requirementVector |
DesignDecisionRecord |
requirementBaselines |
/tenantId + /vehicleProgramId |
decision::{vehicleProgramId}::{decisionId} |
rationaleVector |
VerificationCase |
requirementBaselines |
/tenantId + /vehicleProgramId |
verification::{vehicleProgramId}::{caseId} |
None |
RegulatoryRequirementClause |
homologationRegulationLibrary |
/tenantId + /marketCode |
regulation::{marketCode}::{regulationId}::{clauseRef} |
clauseVector |
Read a requirement with its decisions and verification cases in a single program partition query.
requirementBaselines
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.vehicleProgramId = @vehicleProgramId AND c.type IN ('SystemRequirement','DesignDecisionRecord','VerificationCase') ORDER BY c.requirementId ASC
Find high integrity level requirements without a passing verification case.
requirementBaselines
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.vehicleProgramId = @vehicleProgramId AND c.type = 'SystemRequirement' AND c.safetyIntegrityLevel IN ('ASIL-C','ASIL-D') ORDER BY c.safetyIntegrityLevel DESC
Knowledge-container query against homologationRegulationLibrary (partition-aligned to /tenantId + /marketCode): list regulation clauses in force for a target market, then diff them against the programme's linked requirements; the library stores one clause document per market so the market read is partition-aligned.
homologationRegulationLibrary
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.marketCode = @targetMarket AND c.type = 'RegulatoryRequirementClause' AND c.effectiveFromUtc <= @programStartOfProductionUtc ORDER BY c.effectiveFromUtc ASC
Surface verification cases that failed since the last baseline review.
requirementBaselines
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.vehicleProgramId = @vehicleProgramId AND c.type = 'VerificationCase' AND c.executionStatus = 'failed' AND c.lastRunUtc > @reviewCutoffUtc ORDER BY c.lastRunUtc DESC