Demos / 03 bounded cases

Claims with their limits attached.

These cases distinguish public reproduction from private observation, and a read-only preflight from an approved update. None is presented as proof of production readiness.

01

Public fixture · Knowledge only

A source-grounded answer

A fictional local corpus demonstrates lexical retrieval, section expansion and an answer that names its source, scope and declared version.

Observed
The public fixture returned one supported answer and one explicit no-match result in an isolated check.
Reproducible
Yes — with the public release and downloadable fictional fixture.
Environment
No private Helix environment required.
Does not demonstrate
It does not test official-document accuracy, live state, Gateway policy or any action.
Read the case
02

Controlled validation · Approved DEV update

Evidence to one controlled update

Separate Knowledge and Gateway observations are joined into a reviewable method that includes an exact plan, later human approval, one bounded write and verification.

Observed
One authorised synthetic DEV update was planned, approved by a human, applied once and verified.
Reproducible
Method only — reproduction requires an installation's own authorised synthetic record and policy.
Environment
Private non-production environment and human reviewer required.
Does not demonstrate
It was not one uninterrupted autonomous run and does not establish production suitability.
Read the case
03

Observed integrated run · Read only

Integrated read-only preflight

One uninterrupted run used separate Knowledge and Gateway sessions to combine documentary evidence with a bounded live DEV observation, then stopped before planning.

Observed
The run ended at ready_for_human_review after AR System 26.1.01 was verified but the exact CMDB component version could not be attributed.
Reproducible
The authority chain is deterministic; the public account is sanitised and the exact live run requires private authorised inputs.
Environment
Private synthetic DEV environment required; QA and PROD were not contacted.
Does not demonstrate
It created no plan or write, used no SQL and is not evidence of production readiness.
Read the case

Reading the evidence

A stronger demo is not the one that does the most. It is the one that makes clear what happened, what did not happen and why the next boundary held.