FID-A · Session 0 validation lab — Trustee OS (synthetic)

FALL VALIDATIONFounder/team-only synthetic dry runSYNTHETIC · NON-PRODUCTION

Bounded two-source reconciliation exercise on an immutable fictional fixture. No backend, no network call, no analytics, no browser storage. Lab state and session events are not persisted automatically; choosing Export writes one JSON file to the operator's device. Theme preference is outside the lab data model. Every action is simulated and requires explicit confirmation.

Fixture: FID-A · v1.0.0
Matter / claim: DEMO-FID-BR-001 · C-017
Session (ephemeral): S-R5PAQ-0
SHA-256 checksum (canonical JSON): computing…

Validating…

Source A — claimant filing

claimant_filingSRC-A-CLAIMANT2026-06-02

Source B — debtor ledger

debtor_ledgerSRC-B-LEDGER2026-06-01

Observation prompts — no legal conclusion is proposed

Select what you observe. These are prompts for professional judgement, not determinations.

Reported balance differs between sourcesDifference of R$ 49.800,00 between claimant filing and debtor ledger. Observation only.
NF-8122 present in filing, absent from ledgerOne invoice reference appears in only one source. Observation only.
Ambiguous interaction: R$ 25.000,00 payment note vs R$ 24.800,00 adjustmentRelationship between the ledger payment note and the filing adjustment is undetermined.

Reviewer controls — bounded, no free text

Uncertainty

Professional review required before any consequential step

Bounded next action — simulated

Prototype only — no external effect. Bounded actions unlock only once both sources are open, all three observations are selected, uncertainty is set and professional review is checked. Confirmation is required before anything is recorded locally.

Dry-run readiness

OPENFixture schema valid
OPENBoth sources opened
OPENAll three observations selected (0/3)
OPENUncertainty set
OPENProfessional review required — checked
OPENBounded next action confirmed

Evidence-producing candidate commit SHA

Copy the exact candidate SHA from the release board and verify it against that entry before exporting. A build cannot embed its own final SHA, so this binding is operator-verified (OPERATOR_VERIFIED_RELEASE_BOARD). This field is evidence metadata only and never enters the event recorder.

Terminal event not yet recorded.

Export is manual only and unlocks once exactly one TASK_COMPLETED exists and a valid candidate commit SHA is entered. Choosing Export writes one JSON file to this device. Allowlisted fields: session_id, fixture_id, fixture_version, fixture_checksum, task_id, event_type, step_id, uncertainty, abstention, professional_review, outcome, error_code, timestamp, elapsed_ms. Schema 1.0.0.

Session event trail — in memory only

No events recorded yet.

Data boundary

No private data feeds public search, another tenant, cross-client training or benchmarking. This prototype contains synthetic records only; it makes no claim of tenant isolation, production security, court integration, AI accuracy or real ingestion. It demonstrates UX and workflow only.