Closed Won, but no ERP continuation
This is the strongest introductory example because it demonstrates a central EKA rule: evidence can establish that something has not happened without establishing why it has not happened.
This opportunity is Closed Won. Why hasn't it reached ERP?
Page contextSOURCE / CRM / opportunity / OPP-2026-900006
- Result
- COMPLETE
- Tool calls
- 3
- Evidence
- 9
- Duration
- 5.4s
The user is asking why opportunity OPP-2026-900006 in CRM, which is Closed Won, has not reached ERP. To answer this, we need to inspect the CRM opportunity record, check its operational links or journey to see whether it has reached ERP, and evaluate the integration state.
subject source.CRM.opportunity record OPP-2026-900006 required features STAGE, ESTIMATED_AMOUNT, ERP_CONTINUATION
One requested part.
Read from the CRM opportunity.
Read from the CRM opportunity.
Uses the declared authoritative alternate: integration.source_link.relationship_type.
The registry explicitly says the nullable erp_sales_order_ref is only an operational hint. Whether the opportunity reached ERP must be established through the operational-link or canonical-relationship evidence path.
- Round 1
- s1 get_source_record — read the CRM opportunity
- s2 get_operational_links — any operational link from OPP-2026-900006
- s3 get_operational_journey — the records the opportunity travelled through, depth 3
- validated as proposed: no refusal, no re-plan
Model proposes → runtime validates → governed execution. This plan was accepted on its first round. When a plan or a tool input is invalid, the runtime refuses it and the model replans, and the trace keeps both; this run needed neither.
Called with no relationship_type filter, so an operational link of any type from OPP-2026-900006 would have counted. None is recorded.
The journey has one step: the opportunity's own close date. It travelled to no other record.
No match — any operational link from OPP-2026-900006; checked integration.source_link.
CRM.opportunity OPP-2026-900006: stage_code = "CLOSED_WON".
CRM.opportunity OPP-2026-900006: status = "CLOSED_WON".
CRM.opportunity OPP-2026-900006: actual_close_date (journey step 1 of 1) = "2026-07-31".
The full run also captured the opportunity number, estimated amount, currency and both close dates, giving 9 evidence items in total.
Opportunity OPP-2026-900006 has stage code CLOSED_WON and status CLOSED_WON in CRM.
ESTABLISHEDEVD-FACT-53c971b2, EVD-FACT-77f5ee61
There is no operational link from OPP-2026-900006 in integration.source_link.
ESTABLISHEDEVD-ABS-b9d33772
The reason why the opportunity has not reached ERP is not established by the evidence.
NOT_ESTABLISHEDEVD-ABS-b9d33772 — absence does not establish cause
absence ≠ cause
COMPLETE
The requested investigation was completed: EKA established the current CRM state and the absence of the authoritative ERP continuation, while explicitly refusing to invent a cause.
Opportunity OPP-2026-900006 is marked as CLOSED_WON in the CRM system, but the evidence does not establish why it has not reached the ERP system.
Opportunity OPP-2026-900006 is Closed Won. No operational link from it is recorded in integration.source_link, so no ERP continuation is recorded for it. The available evidence does not establish why it has not reached ERP.
The captured answer leaves the established absence to its claims. The reviewed wording states it in the answer, from the same ABSENCE evidence; the result is unchanged.
A conventional assistant can easily convert “expected continuation missing” into “integration failure”, because that explanation sounds plausible.
EKA instead shows what the enterprise actually establishes, and where explanation stops.
- Run ID
- RUN-02a51aa9-dac5-4b93-ac97-ceeec97d6c8f
- Result
- COMPLETE
- Model
- google:gemini-3.5-flash-lite
- Prompt
- PROMPT-EKA-0.4.6
- Planner hash
- 0fb08227cf1e04d7…
- Synthesis hash
- 2e56d7b0237722db…
- Build
- 093d195bbb15…
- Business now
- 2026-07-31 18:30:00+00
- Tool calls
- 3
- Evidence items
- 9
- Model calls
- 2
- Duration
- 5.4s
The EKA Workspace replaying this chapter's own captured run. No model is called in replay: what is on screen is the run described above, as the runtime returned it.
Transcript
- The question is typed and sent:
This opportunity is Closed Won. Why hasn't it reached ERP?
The run was sent with the page context CRM opportunity OPP-2026-900006. - The activity rail runs, then the answer arrives with its result: COMPLETE.
- The answer reads:
Opportunity OPP-2026-900006 is marked as CLOSED_WON in the CRM system, but the evidence does not establish why it has not reached the ERP system.
- The steps are opened: Reading the source record · Checking cross-system links · Nothing matched · Following the cross-system journey · Writing the answer.
- The evidence is opened: 9 items.
- The view returns to the answer.
