Assay

Verification and quality control

1.0Purpose

What it does

Assay decides whether a record can be trusted. It runs rule-based and model-based checks on incoming data, with provenance and manipulation detection on images.

A review queue routes only what the automated checks cannot settle to a qualified person, and records the decision they make.

2.0Input

What it accepts

Typed records: The records Conduit emits, with their fields and ingest history.
Rule sets and models: Versioned rule sets and versioned models with their configurations. Which checks run against which records is configuration.

3.0Output

What it emits

Check records: One record per check binding the input digest, the rule set version, the model and configuration version, the outcome, the reason, the actor and the timestamp.
Review queue entries: The cases the automated checks cannot settle, routed to a qualified reviewer with the evidence attached.

4.0Config

The configuration surface

Configuration belongs to the client. It encodes what your specialists already know, and it is versioned like code.

Check selection: Which rules and models run against which record types.
Thresholds: Where a score becomes a finding and where a finding becomes a routing.
Routing rules: What goes to the review queue and to whom.

5.0Evidence

What it produces as evidence

Scores and findings: A scored outcome for every check, with the reason recorded alongside the result.

6.0Acceptance

What it is tested against

Assay is tested against acceptance criteria agreed in the statement of work: defined check classes produce the agreed outcome on the agreed cases, the check record carries every field listed above, and the review queue routes what the criteria say it routes. The same criteria are the PQ tests.