Software-build dependency
Leading- Supporting
- Starts after build R7 and lines up with CR-077.
- Contradictory
- Three vehicles on R7 show no symptom.
- Missing
- Dependency replay on hardware rev. B.
The same research, applied to each domain’s evidence, rules and owners.
A worked example: a symptom appears after a software update. The evidence sits across vehicle events, ECU state, software history, workshop records and engineering changes. Agents rebuild the case, engineers challenge it, and a named owner approves the next step.
The questionA camera function drops out after the latest software update. What caused it, and which vehicles share the conditions?
Order the events per vehicle, each linked to the record it came from.
Line up vehicle, build, configuration and service history in one view.
Keep supporting, contradictory and missing evidence with every hypothesis.
Find vehicles that share the build and configuration conditions.
Evidence, reasoning, alternatives, exposure and validation still needed.
Leading hypothesis: a software-build dependency introduced by CR-077. Three vehicles on R7 show no symptom; replay on rev. B is still needed.
Vehicle software, systems engineering, validation and supplier engineering each review the case in their own role.
The quality approver accepts or rejects the containment package. Agents never trigger a campaign or an OTA rollback.
The order matters. Each event stays connected to the record it came from, so an engineer can open the evidence behind the sequence.
Build R7 reaches the vehicle in rollout wave 3
OTA historyTwo restarts within ten minutes of start-up
TelemetryHardware rev. B, calibration set 12 active
ECU snapshotF-212 recorded after the second restart
DTC logBlank view reproduced after a restart
Service recordCR-077 changed a dependency of the camera service
Change recordAgent Hive keeps the relationships between vehicle identity, field records and engineering evidence visible, while every record keeps its source.
Agent Hive
Agent HiveTelemetry, DTCs, ECU configuration and software history per vehicle.
Service records, warranty claims and workshop notes.
Requirements, tests, change requests and supplier validation.
The leading explanation stays open to challenge. Supporting, contradictory and missing evidence travel with every hypothesis, and engineers can reject any of them.
Timeline, configuration and service agents work in parallel. Hypotheses go to specialist review, and containment stops at the quality approver.
Checks the recurring symptom and the exposure.
Build, package and rollout evidence.
Configuration and dependency evidence.
The evidence needed to reproduce the condition.
Bench tests and contradictory evidence.
Accepts or rejects the containment package.
Past investigations with a known root cause become the test set. A version that names the wrong cause, or drops contradictory evidence, does not ship.
| Question | v1 | v2 | v3 | v4 |
|---|---|---|---|---|
| Order the events for vehicle 0193 around the dropoutTimeline | ✓ | ✓ | ✓ | ✓ |
| Which build and calibration were active at the fault?Configuration | ~ | ✓ | ✓ | ✓ |
| Which vehicles share build R7 and hardware rev. B?Exposure | ✗ | ✗ | ✓ | ✓ |
| What contradicts the software-dependency hypothesis?Challenge | ✗ | ~ | ✗ | ✓ |
| Which change request touched the camera service?Engineering | ✓ | ~ | ✓ | ✓ |
| Did workshops reproduce the symptom after restart?Field | ~ | ✓ | ✓ | ✓ |
| What evidence is still missing to confirm the cause?Validation | ✗ | ✗ | ~ | ✓ |
The right vehicle, build and change records are present.
Contradictory evidence is shown, not dropped.
Closed investigations reproduce their root cause.
No action leaves the workflow without the approver.
Identity controls, source permissions, evidence traceability and deployment boundaries stay explicit in every option.
Agent Hive runs inside your private network, connected to your systems through approved paths.
The platform, the models and every trace stay on infrastructure you operate.
| Runs in | QpiAI managed environment | A dedicated network in your cloud | Your data centre (Docker / Compose) | An isolated network |
|---|---|---|---|---|
| Operated by | QpiAI | Agreed per engagement | Your team | Your team |
| Tenancy | Multi-tenant, isolated | Single-tenant | Single-tenant | Single-tenant |
| Data at rest | Managed environment | Your cloud and region | Your network | Inside the perimeter |
| Models | Managed models | Approved endpoints | Local, or via a policy gateway | Local models only |
| Outbound | Operated by QpiAI | Private connections | One controlled egress path (hybrid) | None |
| Identity | Your identity rules | Enterprise identity | SSO and RBAC | Local SSO and RBAC |
| Updates | Rolled out by QpiAI | Agreed per engagement | New image version, pulled | Signed offline packages |
| Audit | Audit history | Audit history | Local audit history | Local audit history |
Air-gapped Graph, agents and models run inside an isolated network; updates arrive as signed offline packages.