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 06 of 11Real example 2COMPLETE

What do we owe Bharat Polymers?

The important part is not merely arithmetic. EKA must understand that “what do we owe?” means open_amount, not invoice face value.

The question, exactly as entered

What do we owe Bharat Polymers, across how many invoices?

Result
COMPLETE
Tool calls
3
Evidence
3
Duration
4.4s
What EKA understood
The user is asking for the total outstanding amount owed to Bharat Polymers and the count of invoices associated with this counterparty. First, we need to resolve 'Bharat Polymers' to a canonical organization record, then list or aggregate the invoices associated with that counterparty entity ID.
Part p1  What do we owe Bharat Polymers?
         required: OPEN_AMOUNT, CURRENCY

Part p2  Across how many invoices?
         required: none declared — a count is a calculation, not a feature

The runtime also mechanically inferred the COUNTERPARTY and currency requirements from the actual aggregate steps.

Reference resolution
"Bharat Polymers"
→ UNIQUE
→ canonical.Organization ORG-000001

This produces governed RESOLUTION_EVIDENCE; the name itself is not used as an unverified identity.

Validated plan
Step 1
resolve_reference("Bharat Polymers")
→ ORG-000001

Step 2
aggregate canonical.Invoice
filter counterparty_entity_id = ORG-000001
SUM(open_amount)
GROUP BY currency_code

Step 3
aggregate canonical.Invoice
same population
COUNT(*)
GROUP BY currency_code

Money policy GROUP_BY_CURRENCY, so EKA cannot silently add unlike currencies.

Evidence: EVD-RES-0bd67988Kind: RESOLUTION_EVIDENCEAuthority: CANONICAL

canonical.Organization ORG-000001: {"matched_text":"Bharat Polymers","display_name":"Bharat Polymers","state":"UNIQUE"}

Evidence: EVD-DER-dedd90fdKind: DERIVED_RESULTAuthority: DERIVED

SUM(open_amount) over counterparty_entity_id EQ "ORG-000001" (11 row(s)) = {"amount":"0.00","currency":"INR"}

Evidence: EVD-DER-3b8f48f2Kind: DERIVED_RESULTAuthority: DERIVED

COUNT(*) over counterparty_entity_id EQ "ORG-000001" (11 row(s)) = {"count":11}

The invoice face-value total for the same seeded population is a different measure; the question asked what remains owed.

What is established — and what is not

  • Bharat Polymers is canonical organization ORG-000001.

    ESTABLISHEDEVD-RES-0bd67988

  • The total open amount owed is 0.00 INR.

    ESTABLISHEDEVD-DER-dedd90fd

  • The total number of invoices is 11.

    ESTABLISHEDEVD-DER-3b8f48f2

outstanding amount ≠ invoice face value

Result

COMPLETE

Both requested parts were answered from deterministic, currency-aware calculations over a governed population.

The answer, twice
Captured model answer · runtime output

We owe Bharat Polymers (canonical organization ORG-000001) a total of 0.00 INR across 11 invoices.

Reviewed public wording · editorial

Across 11 invoices, the total outstanding amount for Bharat Polymers is INR 0.00.

The captured wording already keeps the calculation exact: it counts 11 invoices without calling them open invoices, so it implies no invoice-status filter the calculation did not apply. The reviewed wording only restates the figure as an outstanding amount.

Why this example matters

One run demonstrates natural-language measure selection, governed identity resolution, declared and mechanically implied features, canonical aggregation, currency-aware calculation and derived evidence.

Its plan is the golden plan for this question, step for step: the model chose the outstanding amount rather than the face value, and the runtime had nothing to refuse.

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 without sound, in replay. The transcript below describes it.
Transcript
  1. The question is typed and sent: What do we owe Bharat Polymers, across how many invoices?
  2. The activity rail runs, then the answer arrives with its result: COMPLETE.
  3. The answer reads: We owe Bharat Polymers (canonical organization ORG-000001) a total of 0.00 INR across 11 invoices.
  4. The steps are opened: Resolving the reference · Calculating · Calculating · Writing the answer.
  5. The evidence is opened: 3 items.
  6. The view returns to the answer.
The question, as entered — EKA Workspace replaying the captured run for “What do we owe Bharat Polymers, across how many invoices?”
The question, as entered
The activity rail, mid-run — EKA Workspace replaying the captured run for “What do we owe Bharat Polymers, across how many invoices?”
The activity rail, mid-run
The answer and its result — EKA Workspace replaying the captured run for “What do we owe Bharat Polymers, across how many invoices?”
The answer and its result
The evidence, expanded — EKA Workspace replaying the captured run for “What do we owe Bharat Polymers, across how many invoices?”
The evidence, expanded