Six gates, and a record clears every one of them.
The release contract
The gates are a release contract, not a checklist someone signs off. A refusal comes back naming the requirement that was not met, rather than failing quietly. Each gate below states what it requires, what it carries, and how the record is built to satisfy it.
Executive verdict.
The operator can state the record posture without caveat hunting.
Released, blocked, source-review, or human-QA required. This is the record's release state, not an evidence posture and not a ClearGate decision.
The record opens with the posture a human can act on, not a hidden conclusion.
Evidence map.
Every material claim points to a source file, row, field, or explicit limitation.
Order, API and product, lot, COA, supplier packet, reviewer, and source file.
Material observations point back to source files, fields, hashes, or explicit limitations.
Evidence replay.
The artifact shows how intake, extraction, reconciliation, QA, release, and archive state produced the decision.
Source intake, extraction, reconciliation, QA, release, and archive state.
A mechanical, repeatable process, so two reviewers reach the same record and an inspector can follow it.
Risk boundary.
The artifact excludes product approval, safety, legal, medical, and purchase language.
Documentation evidence only. No product-quality or supplier-approval claim.
Every output excludes product approval, safety, legal, medical, or purchase language.
Next action.
The client knows exactly what to ask, hold, route, review, or release next.
Attach missing file, ask supplier, release customer link, or hold reliance.
The client sees the supplier ask, hold, review, or release step tied to the evidence. At receiving that ask is drafted for them, composed from the specific gaps the gates found.
Export package.
The record can be forwarded, archived, audited, or attached to a workspace.
Passport link, evidence room, audit trail, weekly rollup, and usage event.
The output becomes a reliance hold, a supplier question, an evidence memo, or an Evidence Passport. Never supplier approval or product certification.
What the gates keep out.
The boundary is enforced by the fourth gate and repeated on the face of every output, so a reader never has to infer it. Veritura reads and connects the paperwork behind an order. It never tests, grades, or endorses the medicine itself, and it never releases anything on its own.
- No product approval, safety, legal, medical, or purchase language.
- No subjective or paid ranking, no vendor scoring, and no certification of product quality.
- No supplier approval. A qualification file records what was evaluated and what was attested.
- Absence of a public-source match is never recorded as proof of absence.
The rule every output ships under.
No Veritura output ships as customer-safe until the verdict, evidence map, replay path, boundary language, next action, and export package are present and consistent with the source record.
Release is not a status a person sets. It is a gate, and a refusal names the requirement that was not met. Where the gates are applied to a real lot, the same six appear on the face of the record, in the same order.