L1 · Interpret
A constrained mapper proposes targets, transforms, confidence and evidence. Today's provider is a deterministic fixture; live model adapters are planned. It cannot edit rows or decide results.
Architecture
One uncertain boundary. One deterministic core.
The model narrows semantic ambiguity; it never owns the replay result. Invalid or unapproved proposals stop before deterministic execution.
From source rows to evidence
- Committed source rows Untrusted input
- Schema mapper Fixture proposal
- Mapping approval Person · exact proposal hash
- Canonical event set Code · re-derived from approved mapping
- Dataset profile Code · bounded facts
- Bounded case proposer Planned · authored manifests today
- Case approval Person · exact scope hash
- Replay engine Code · five rule gates
- Finding source trace Code · original rows
- Evidence Bundle assembly Planned
A refused request carries a review state and no result hash.
L2 · Approve
A person approves the exact mapping and authored case proposal by hash. Flagged fields require a justified override. Approval cannot edit a computed result.
L3 · Decide
Versioned code owns ordering, deduplication, calculation, evaluation, and hashes.
L4 · Evidence
The server resolves findings to canonical eventId, rawRowHash, artifact coordinates and unchanged raw values. Unresolvable lineage is refused. INCONCLUSIVE has no finding evidence.
What the canonical hash covers
canonicalReplayResultHash hashes the engine version, semantic event projection and evaluation when present. Volatile run metadata is excluded.
Complete approval records, all mapping and manifest fields, and source trace are not protected by this result hash. A future bundle hash and independent bundle assembly and verification remain planned.
The browser's guide progress is presentation state. Each API replay creates a request-local workflow; durable audit history is not implemented.
Walk through a case