Media · Twindexers EKA: What Happens When an AI Assistant Has to Understand an Enterprise?

Evidence before explanation1 video

The recorded run: the Closed Won status and the missing ERP continuation are both stated, and the answer says the evidence does not establish why. Result: COMPLETE.
Video

The recorded run: the reference is resolved, the runtime performs the SUM and COUNT, and the answer reports an open amount of 0.00 INR across 11 invoices. Result: COMPLETE.
Video

Ask EKA on a CRM opportunity: the chip names the opportunity, and the answer is the recorded operational handoff to ERP.
Video
Move to another opportunity: the thread still carries the first, the new page is only offered, and it becomes the context when the reader chooses it.
Video
Ask in the Sidecar, open the thread in the Workspace, reload: the same saved conversation every time.
Video
On a person whose name is HR-restricted, ask for their HR employment record: the Sidecar knows the page, and the read is refused.
Video
The same contextual Ask at phone width: the overlay covers the page and answers the same; closed and reopened, it starts from the same record.
Video
Complete one turn, stop the next, open the thread in the Workspace: the stopped turn is gone and the conversation still answers.
Video

The recorded decision reason and the policy passage, kept apart: impact damage is excluded under the extended policy. Result: COMPLETE.
Video
The record is found, but the canonical amount is not present, so the total is not established. Result: PARTIAL.
Video
The ERP source has a value, but answering the canonical question from it would be an unlabelled authority substitution. Result: UNAVAILABLE.
Video
A permitted query that matched nothing: no open invoices, so there is nothing to total. Result: COMPLETE.
Video
The cross-system link to ERP sales order SO-2026-000001, returned as structured output. Result: COMPLETE.
Video
Document versions carry no effective dates, so the evidence cannot say which version applied. Result: UNAVAILABLE.
Video
The organization is resolved, but it is never a substitute for the CRM account, which V1 cannot look up. Result: UNAVAILABLE.
Video

Ask EKA. The entry point sits on the record page itself.
Image
The Sidecar. It opens beside the page and names the page as its context.
Image
An answer in place. Activity, records, evidence and result, without leaving the page.
Image
Open in Workspace. A Sidecar thread can move to the full Workspace.
Image
The same conversation. Continued in the Workspace, current in the saved rail.
Image
Before the turn. The conversation rail, the question in the composer, and suggestions to start from.
Image
Visible activity. Each step is a governed tool the plan named, with the status the runtime gave it.
Image
A calculation the runtime performed. The figure is the runtime’s; the model did not add anything up.
Image
Absence, not a cause. The limitation stays explicit instead of becoming an explanation.
Image
Two authorities, kept apart. Source records and a policy passage in one answer, not one summarised paragraph.
Image
Access still governs. The HR record is refused, and nothing of it is shown.
Image
Re-gated on reopen. A saved conversation is replayed under current access, so a turn can be withheld.
Image