Agency Data Trust Series

Synthetic review package

Review each evidence stream before making a release decision. Source completeness, excluded records, identity uncertainty, financial totals, and human decisions answer different questions.

Review an evidence snapshot

Load the example or import a package to review its source evidence. Read-only; no approval or release action is taken.

This Intake-only example contains the committed demo run. Readiness, identity and finance evidence remain unavailable unless supplied in the package.

No package loaded. Load the example or import a package to begin.

Validation and storage details

Hashes prove consistency, not authenticity. This view clears on refresh. Same-run imports retain existing pins; clear the summary before changing a snapshot.

Source freshness

Unavailable: no run-bound expected source inventory

Accepted and excluded records

Accepted clean output rows: Unavailable

Distinct source rows with error evidence: Unavailable

How these counts are derived

Error rows are deduplicated by source, row number and raw hash. They are not subtracted from raw input counts: mapping changes row granularity. Blocked runs have no accepted output.

Unresolved identities

Unavailable: no bound identity partition

Counts cover only supplied groups. Automatic resolution still requires human confirmation.

Signed financial totals

Unavailable: no bound finance review

Positive and negative amounts are retained. No ERP posting or authenticated financial approval.

Review state and next actions

Identity groups without declared approval: Unavailable

Declared reviewer states are unauthenticated. Missing evidence remains unresolved; obtain a human decision before release.

Evidence guide and production limits

Keep the evidence in scope

The summary above validates only its imported package, with no aggregate go-live verdict. The links below are a separate review guide. Sources, exceptions, and tie-out show the demo or the run loaded in this browser. Source readiness imports a separate dated snapshot; it does not automatically correspond to the loaded Intake run. The receipt ledger also opens its own export and does not inherit the loaded run. Companion dashboards open separate demos and do not inherit that run, agency, or review state. Plan Diff also offers a separately selected public Texas run; public carrier evidence does not establish a client's enrollment.

Local package tools must use the same explicit agency and Intake run IDs, verify pinned artifact hashes, and retain provenance. Hashes establish snapshot consistency, not authenticity. Client plan worklists need separately supplied synthetic coverage evidence; missing county or plan year stays unresolved.

Source completeness

Compare required sources, expected and received rows, and the mapping used for this snapshot. A successful row check does not prove that all agency records were received.

Inspect source evidence

Readiness checks expected-file coverage and freshness from a separately imported package. Verify its agency, Intake run, and as-of date against the evidence you intend to review.

Review source readiness snapshot

Excluded records

Inspect errors, unresolved references, and records kept out of the clean outputs. Keep warnings and unsupported records visible; exclusion does not resolve their business meaning.

Inspect exceptions

Identity uncertainty

Bob's deterministic links preserve match evidence and conflicts. Resolved does not mean human-confirmed; singleton, ambiguous, and unsupported identities remain review work.

Separate Bob demo; no shared agency run is loaded.

In the local Bob dashboard, open Evidence workflow for separately supplied review context. Its browser-memory drafts and declared reviewer names are unauthenticated; accepting evidence does not merge people or resolve identity.

Financial totals

Check statement groups, matched transactions, unmapped evidence, and variance by the stated basis. A tie-out result does not settle identity, source completeness, or permission to post to an ERP.

Inspect financial tie-out

The receipt ledger opens a separate synthetic JSON export; its bundled example is a committed demo snapshot. The page uses browser memory. Durable receipt storage uses the local SQLite finance command, with no hosted persistence.

Inspect receipt ledger snapshot

Human review

Record an evidenced human decision separately from automatic checks. Browser review labels are not authenticated approval. Plan change flags identify evidence to review; they are not suitability or purchase recommendations. Incomplete benefits, missing citations, unresolved identities, and missing coverage still require attention.

Separate Plan Diff demo; select its run and inspect citations before interpreting a flag.

Production access gates

These gates need separate authorization and implementation before production use.

  • Real authentication. Verify reviewer identity, roles, and evidence of approval.
  • Hosted storage. Establish authorized storage, retention, and access controls for agency artifacts.
  • ERP posting. Approve the destination, posting basis, and controlled release process.
  • Agency data. Obtain explicit permission for real data and validate the agency-specific sources and mappings.