Static narrative simulator
No uploads · no tracking · no live engineDVS is the final stop before unsupported conclusions become downstream action.
This demo uses synthetic data and simplified public-facing examples. It illustrates DVS boundary behavior without exposing private engine internals, source code, rule bundles, customer data, or production enforcement systems.
What this demo proves
This demo shows how DVS treats unsupported conclusions before they move downstream.
It does not evaluate live user data. It does not expose the engine. It uses synthetic, pre-authored scenarios to show boundary behavior:
source posture → conclusion authority → contradiction/gap state → propagation decision → diagnostic output
What this demo does not do
This public demo does not process real files, collect user data, call an API, run the private DVS engine, or make production enforcement promises.
It is a static educational simulation designed to explain boundary behavior without exposing implementation details.
Why this matters
They move quietly: into reports, summaries, workflows, recommendations, alerts, records, and decisions.
DVS is built to stop that movement when the support state is incomplete, contradicted, unresolved, or outside the allowed boundary.
API direction
DVS is being designed as a boundary layer that can return machine-readable decisions before downstream propagation.
This public demo shows the shape of that decision without connecting to the private engine.
Boundary path
Select a scenario and run the boundary check.
No state rendered yet.
Illustrative only. This public demo makes no network call and is not using the real DVS API.
No preview rendered yet.
Preview-only diagnostic export
Run a scenario, then open a preview. This v0.1 demo shows previews only. It does not download, save, upload, transmit, or generate files.
Next step
This page is the public boundary explanation. The private engine remains protected.
