Run everything inside your network.
Fully air-gappedThe 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
The same research, applied to each domain’s evidence, rules and owners.
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.
The questionBoard rev C goes to the design gate on Friday. Which requirements are verified, and what did last week’s ECO make stale?
Link each requirement to its constraints and design objects.
Find the simulations, tests and reviews that verify each one.
Compare each evidence revision with the current design and flag what an ECO made stale.
List missing evidence, with an owner and the test that would close it.
A coverage matrix and gap list, every cell linked to its source.
ECO-311 changed the stack-up, so SI-118 and eight other results predate the current design. REQ-204 has no lab evidence yet.
An engineer accepts, edits or rejects each suggested requirement-to-evidence link. No silent graph changes.
The gate owner signs off. Blocked requirements stay blocked until the evidence exists.
Requirements down the side, evidence across. Current, needs review, stale after a change, or missing, with the gate state each one implies.
| Requirement | Constraint | ECAD | Simulation | Lab test | Review | Gate |
|---|---|---|---|---|---|---|
| REQ-042Power integrity | Current | Current | Stale after change | Current | Needs review | Re-run PI |
| REQ-118High-speed link | Current | Current | Stale after change | Current | Current | Re-run SI |
| REQ-204Thermal shutdown | Current | Current | Current | Missing | Missing | Blocked |
| REQ-287ESD protection | Current | Current | Current | Current | Current | Ready |
| REQ-311Clock jitter | Current | Needs review | Current | Current | Current | Review |
| REQ-350Connector retention | Current | Current | Current | Current | Current | Ready |
Constraints, design objects, simulations, tests, reviews and change history, without piecing the trail together by hand.
Agent Hive
Agent HiveRequirement records, ECOs and review history.
ECAD exports, BOMs and constraint files by revision.
Simulation results and lab test reports.
Mapping, linking and freshness checks run in parallel. Proposed links and the gate itself wait for people.
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.
Link REQ-042 to simulation SI-118.
Accept, edit or reject.
The approved relation is added, with its source.
Missing evidence returns to its owner.
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.
Questions agreed with the engineering team check coverage, evidence freshness and the impact of recent changes.
| Question | v1 | v2 | v3 | v4 |
|---|---|---|---|---|
| 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 | ✗ | ✗ | ✗ | ✓ |
Every requirement maps to its evidence or a named gap.
Evidence revision matches the design revision.
ECO effects are found before the gate, not at it.
Each conclusion keeps its source revision and model version.
Run locally, or use approved models through a gateway. The evidence, permissions and review history stay under your control.
The knowledge graph, agents and models run locally. Updates arrive as signed offline packages and no data leaves the site.
A policy gateway controls what is sent, which model receives it and what comes back into the workflow.
Point at a part no egress · signed bundles in · data stays inside