IIntakeFlowTechnical proof

RECRUITER PROOF SURFACE

A trustworthy workflow is
more than a model call.

These are the engineering decisions behind the IntakeFlow demo: explicit boundaries, measurable behavior, and failure paths that remain safe to retry.

Launch the live workspace →Read the sourceInspect CI runs
Model boundaryExtract only

Provider output is untrusted. Deterministic policy owns routing and export.

Evidence trailPage + quote

Model proposals and exact reviewer matches point to the source; ungrounded overrides stay explicit.

Human gateRequired

A versioned reviewer decision unlocks downstream export.

RecoveryExactly once

The same idempotency key safely survives a retryable failure.

ARCHITECTURE TRAIL

Document → evidence → policy → action

synthetic-only
01IngestPDF validation
native text or OCR
→
02ProposeTyped fields
page evidence
→
03ValidateRules, conflicts
prompt injection
→
04ReviewVersioned correction
explicit approval
→
05ExportOutbox, retry
audit event

MEASURED QUALITY

Evaluation scoreboard

locked challenge suite
The deployment has not persisted its locked challenge evaluation yet.

BUILD PROVENANCE

What is running

API version
Loading…
API commit
Not reported
Frontend commit
5ca191a54757145d2791e2f62fdf8dc0ba20f8db
Build time
2026-08-28T01:21:04.787Z
Record schema
intake-record/2
Demo scenario
v2
Provider
Not reported
Data policy
Synthetic only
This page reads the persisted locked challenge evaluation. CI independently regenerates the same gates and publishes the machine-readable proof artifact.

INTENTIONAL LIMITS

What this project does not claim

× No diagnosis, treatment, urgency, or coverage decisions.× No real patient data or production EHR connection.× No HIPAA-compliance claim; the public environment is synthetic and TTL-scoped.× Live model comparison is optional and never authoritative.