EKA Public Guidev0.2 · real-run integrated
Reader level controls how much run anatomy is shown. It is a reading aid, not an access control.
Chapter 12 of 14Real run · EKA-CUR-012UNAVAILABLE

Resolving a name is not finding the record

The name resolves to exactly one organization, and the question still cannot be answered. What was asked for is a CRM account, and knowing the organization does not tell you which account represents it.

This chapter is the same at every reader level — it records no run anatomy to reveal.

The question, exactly as entered

Show me the account for the customer named Kestrel.

ResultUNAVAILABLE
What the run established, and where it stopped
  • the canonical organization for Kestrel is ORG-000012, Kestrel Auto Retail — established, from resolution evidence
  • which CRM accounts represent that organization is entity-resolution mapping membership, and no governed read exposes it in V1
  • so the specific CRM account asked for is not held

The runtime states the reason rather than rounding the answer off: more than one account may represent one Organization, so the Organization is never a substitute for the account. Metrolane contains exactly that case by design — two CRM accounts resolving to one canonical organization is the estate's own duplicate-account scenario.

one organization was resolvedone account was identified

Why this matters

Chapter takeaway

  • A near-answer is the dangerous one: the organization is right there, and returning it would answer a question nobody asked.
  • Unique resolution says the name was understood. It says nothing about how many records of the requested type stand behind it.
  • The missing capability is named — a governed read of resolution membership — so the limit is a backlog item rather than a mystery.

This case failed its first review for the opposite behaviour and was corrected before it was promoted, which is why it is here: the guide shows the run that refuses, not the one that guessed.

In the Workspace

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.

Recorded walkthrough

38 seconds, without sound, in replay. The transcript below describes it.
Transcript
  1. The question is typed and sent: Show me the account for the customer named Kestrel.
  2. The activity rail runs, then the answer arrives with its result: UNAVAILABLE.
  3. The answer reads: The evidence establishes that the canonical organization for Kestrel is Organization ORG-000012, named Kestrel Auto Retail. However, the runtime notes state that finding CRM accounts for a canonical organization is not supported in V1, and the organization is never a substitute for the account. Therefore, I do not have the specific CRM account for Kestrel.
  4. The steps are opened: Resolving the reference · COMPLETED · Finding matching records · Could not run as planned · FAILED · Resolving the reference · COMPLETED · Writing the answer · COMPLETED.
  5. The evidence is opened: 1 item.
  6. The view returns to the answer.

Screenshots

Four moments of the run, one tab each.

The question, as entered — EKA Workspace replaying the captured run for “Show me the account for the customer named Kestrel.”
The question, as entered
The activity rail, mid-run — EKA Workspace replaying the captured run for “Show me the account for the customer named Kestrel.”
The activity rail, mid-run
The answer and its result — EKA Workspace replaying the captured run for “Show me the account for the customer named Kestrel.”
The answer and its result
The evidence, expanded — EKA Workspace replaying the captured run for “Show me the account for the customer named Kestrel.”
The evidence, expanded