Skip to content
Blueprint · Semiconductor

What is verified? What is missing?

A worked example: follow each board requirement to its constraints, design outputs, simulations and tests. Agents find stale or missing evidence after a change. An engineer makes the call at the design gate.

Semiconductor
The question

Board rev C goes to the design gate on Friday. Which requirements are verified, and what did last week’s ECO make stale?

Inputs

What the agents read.

Requirements
System, interface and safety requirements
Constraints
Design rules, stack-up and routing constraints
ECAD outputs
Schematic, layout and BOM by revision
Simulation
Signal integrity, power integrity and thermal
Lab tests
Test reports and results, by board revision
Change records
ECOs and design review history
Run

What happens, step by step. Each step is logged with its sources.

  1. 01

    Map the requirements

    Link each requirement to its constraints and design objects.

  2. 02

    Link the evidence

    Find the simulations, tests and reviews that verify each one.

  3. 03

    Check freshness

    Compare each evidence revision with the current design and flag what an ECO made stale.

  4. 04

    Find the gaps

    List missing evidence, with an owner and the test that would close it.

  5. 05

    Prepare the gate review

    A coverage matrix and gap list, every cell linked to its source.

Agent Hive · Run 0311
Which requirements on rev C are verified, and what did ECO-311 make stale?
  1. Readrev C baseline · 48 requirements0.6s
  2. Linked131 evidence items2.4s
  3. Comparedevidence revision vs stack-up rev 41.1s
  4. Flagged9 stale after ECO-3110.5s
  5. Builtcoverage matrix and gap list0.7s
Answer4 sources
39 of 48current
Requirements with current evidence, rev C

ECO-311 changed the stack-up, so SI-118 and eight other results predate the current design. REQ-204 has no lab evidence yet.

requirementsECO-311SI-118TEST-204
Ask a follow-up…
Approvals

Where people decide.

  • Needs you

    Proposed links

    An engineer accepts, edits or rejects each suggested requirement-to-evidence link. No silent graph changes.

  • Needs you

    Design gate

    The gate owner signs off. Blocked requirements stay blocked until the evidence exists.

Outputs

What you get back.

Coverage matrix
Requirement × evidence: current, stale or missing
Gap list
Missing evidence with owners and the closing test
Gate review pack
Matrix, gaps and change impact, source-linked
Run trace
Source revision, model version and evidence used
Coverage

One matrix for the gate. Every cell opens its evidence.

Requirements down the side, evidence across. Current, needs review, stale after a change, or missing, with the gate state each one implies.

Fig. 1 · Verification coverage, board rev CIllustrative data
Evidence state by requirement
RequirementConstraintECADSimulationLab testReviewGate
REQ-042Power integrityCurrentCurrentStale after changeCurrentNeeds reviewRe-run PI
REQ-118High-speed linkCurrentCurrentStale after changeCurrentCurrentRe-run SI
REQ-204Thermal shutdownCurrentCurrentCurrentMissingMissingBlocked
REQ-287ESD protectionCurrentCurrentCurrentCurrentCurrentReady
REQ-311Clock jitterCurrentNeeds reviewCurrentCurrentCurrentReview
REQ-350Connector retentionCurrentCurrentCurrentCurrentCurrentReady
ECO-311 changed the stack-up, so simulation results run on the old stack-up are stale. REQ-204 has no lab evidence yet.
Data sources

Follow every requirement to the evidence behind it.

Constraints, design objects, simulations, tests, reviews and change history, without piecing the trail together by hand.

Fig. 2 · Connected sources
Sources stay in place; Agent Hive reads them through read-only connectors and builds one shared model. Logos are trademarks of their respective owners.
  • Requirements and changes

    Requirement records, ECOs and review history.

  • Design outputs

    ECAD exports, BOMs and constraint files by revision.

  • Verification evidence

    Simulation results and lab test reports.

Agent workflow

Agents organise the evidence. Engineers make the call.

Mapping, linking and freshness checks run in parallel. Proposed links and the gate itself wait for people.

Fig. 3 · Workflow runIllustrative data
The run as the platform draws it: tool steps, specialist agents, joins, branches and the approval it is waiting on. Drag to pan; Ctrl or ⌘ + wheel to zoom.
Knowledge model

A traceability graph, versioned and permission-aware.

Requirements, constraints, design objects and evidence, each tied to the revision it describes. Agents suggest links; engineers approve them before they enter the shared model.

Fig. 4 · Knowledge modelIllustrative data
The traceability graph around ECO-311: requirements, constraints, design objects, simulations and tests, and what the change touched.
  • 01

    Agent proposal

    Link REQ-042 to simulation SI-118.

  • 02

    Engineer review

    Accept, edit or reject.

  • 03

    Shared model

    The approved relation is added, with its source.

  • 04

    Gap feedback

    Missing evidence returns to its owner.

Document checks

Read the document. Check it against the rule.

Values are read off datasheets, drawings and reports, then checked against the constraint they must satisfy. Each check is a step a reviewer can replay.

Fig. 5 · Reading a drawingIllustrative data
Dimensions and limits are read off drawings and reports, compared with their tolerance, and linked to the constraint they must satisfy.
Fig. 6 · Checked before acceptedIllustrative data
The rule every run must keep, checked over every reachable state: nothing is published without a current approval, and editing an approved item clears its approval.
Evaluation

Catch stale evidence before a design gate.

Questions agreed with the engineering team check coverage, evidence freshness and the impact of recent changes.

Fig. 7 · Question set by versionIllustrative data
Evaluation results by question and version
Questionv1v2v3v4
Which tests verify REQ-118 on rev C?Coverage✓✓✓✓
Which evidence did ECO-311 make stale?Change impact✗✗✓✓
Was SI-118 run on the current stack-up?Freshness~✗✓✓
List requirements with no lab evidenceGaps~✓✓✓
Does the datasheet thermal limit match REQ-204?Document check✗~~✓
Who owns the missing power-integrity run?Gaps✓~✓✓
Is rev C ready for the gate?Gate✗✗✗✓
v4: 7 of 7 pass · release needs all 7
Each row is a question agreed with the team; each column a version of the workflow. The candidate ships only if it holds the release bar.
  • 01

    Coverage

    Every requirement maps to its evidence or a named gap.

  • 02

    Freshness

    Evidence revision matches the design revision.

  • 03

    Change impact

    ECO effects are found before the gate, not at it.

  • 04

    Replayable

    Each conclusion keeps its source revision and model version.

Outcomes

Gate reviews start from the matrix, not a spreadsheet hunt.

To a gate review pack
1 day
from a week of collation
Stale items found
9
after one ECO, before the gate
Cells source-linked
100%
every status opens its evidence
Eval pass, v4
7 of 7
release bar
Illustrative data
Deployment

Choose the model setup that fits your engineering network.

Run locally, or use approved models through a gateway. The evidence, permissions and review history stay under your control.

Run everything inside your network.

Fully air-gapped

The knowledge graph, agents and models run locally. Updates arrive as signed offline packages and no data leaves the site.

  • Local model serving
  • Read-only connectors
  • Your SSO, roles and audit

Keep the data local, use approved models.

Hybrid model access

A policy gateway controls what is sent, which model receives it and what comes back into the workflow.

  • Model choice per agent role
  • One controlled egress path
  • Graph and sources stay local
Fig. 8 · Air-gapped perimeter
Air-gapped deploymentEverything runs inside the customer’s perimeter with no outbound internet: users, the agent runtime, local models, the knowledge graph, the audit log and read-only connectors to on-prem systems. Updates come in as signed offline bundles. Point at a part to see what it holds and what is blocked.OUTSIDEReleasesigned bundlevX.Y · checksumcarried on offline mediano network linkINTERNEThosted model APIsCUSTOMER PERIMETERNO EGRESSUsersSSO · RBACcustomer identityAGENT HIVE RUNTIMEAgents · workflowsApproval gatesPoliciesEvals · tracesLocal modelsGPU servinginside the siteKnowledge graphdocuments + systemsstored locallyAudit logwho · what · whenevery approvalON-PREM SYSTEMSREAD-ONLY CONNECTORSERPData lakeDocumentsagents read through approved, read-only accessREADUpdate importverify signatureadmin approvesAPPROVED UPGRADEno outbounddata, models, graph and audit never leave the line

Point at a part no egress · signed bundles in · data stays inside

Fully air-gapped: models, the traceability graph and every trace inside the engineering network.

Run this blueprint on your data. We set up the first one with you.