MDIL Reasoning Trace Console
UCA · dev scaffold CC + Bridge + Core · prod
audit_root
LIVE
egress: …
Pipeline
switch the demo journey — fixtures are deterministic; same query + same customer = byte-identical response
running…
Ready

Type a query, press Run. The substrate proves the trail.

A single query flows through 34 packs in parallel, an ambiguity validator, named-concept composition, a deterministic tool-call constructor, and a hash-chained audit root. Each tab below renders one slice. Run reasoning populates them all in one pass.

1Overview — top-K + tool-call + audit_root at a glance
2MMT Layer — 34-pack grid + L1/L2/L4 trace + cross-fire
3Validator — ambiguity_validator contract (0 dims · suppression · escalation)
4Concepts — YAML-declared named concepts · fired + unfired + derivation
5Tool Call — deterministic structure · 0 LLM tokens for routing
6Audit & Provenance — nested hash tree: pack manifests → vocab → audit_root
7Vocab Explorer — 16 vocabularies + 6 structures
8Production Topology — CC + Bridge + Core (UCA scaffolds; production lives here)
Determinism receipt

Same input × N runs

all hashes identical → reasoning is deterministic
progress /
#
manifest_hash
result_hash
latency
identical?