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 11 of 14Real run · EKA-CUR-011UNAVAILABLE

A policy version on a date

A question can name a document the reader may open, and still ask for something the enterprise never wrote down. The warranty policy is readable. Which version was in force on a particular day is not recorded anywhere.

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

The question, exactly as entered

Which version of the warranty policy was effective on 2026-07-15?

ResultUNAVAILABLE
What the runtime answered, and what it refused

The search ran and returned five passages of the policy, all readable by this viewer. The run still refused the question, because the feature it needed is one the model of a document does not carry:

  • EFFECTIVE_AT on a document — NOT_SUPPORTED: document versions carry no effective-from or effective-to
  • TITLE on a document — AVAILABLE, and only for records this reader may see

The reason the runtime gives is the part worth keeping: published-by-date is a different claim and must not be substituted for it.

when a version was published≠when a version was in force

Why this matters

Chapter takeaway

  • Readable is not the same as answerable: every passage here was permitted, and the question still could not be answered.
  • The nearest available date would have produced a confident, plausible, wrong answer — which is exactly what an assistant without a feature model does.
  • UNAVAILABLE names a limit in the enterprise's records, not a failure of the run or of the reader's access.

Effective-dated policy is a modelling gap the estate records rather than hides: EKA V1 does not determine a historical effective policy without explicit effective-date data, which the guide takeaway lists among its stated limits.

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

34 seconds, without sound, in replay. The transcript below describes it.
Transcript
  1. The question is typed and sent: Which version of the warranty policy was effective on 2026-07-15?
  2. The activity rail runs, then the answer arrives with its result: UNAVAILABLE.
  3. The answer reads: Based on the provided runtime notes, the effective date for any document (canonical.Document.EFFECTIVE_AT) is NOT_SUPPORTED, as document versions carry no effective-from/effective-to dates. Therefore, the evidence does not establish which version of the warranty policy was effective on 2026-07-15.
  4. The steps are opened: Searching documents · COMPLETED · Writing the answer · COMPLETED.
  5. The evidence is opened: 5 items.
  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 “Which version of the warranty policy was effective on 2026-07-15?”
The question, as entered
The activity rail, mid-run — EKA Workspace replaying the captured run for “Which version of the warranty policy was effective on 2026-07-15?”
The activity rail, mid-run
The answer and its result — EKA Workspace replaying the captured run for “Which version of the warranty policy was effective on 2026-07-15?”
The answer and its result
The evidence, expanded — EKA Workspace replaying the captured run for “Which version of the warranty policy was effective on 2026-07-15?”
The evidence, expanded