Evidence engine

Candidate claims should stay attached to where they came from.

CVault is designed to make reviewer confidence visible: source snippets, parser state, role criteria, and decision history stay together.

How does CVault link claims to source evidence?

Source evidence
Candidate claimPostgreSQL search experiencesupported
“Built backend services for candidate matching, SQL search, and reviewer exports.”
Confidence HighReviewer ConfirmAudit Exportable

Evidence is useful only when it survives the workflow.

The same context that helps parsing also helps review, scoring, export, and deletion decisions.

Source snippets

Reviewer-facing evidence can point back to the text that supported a claim.

Confidence and gaps

Low-confidence fields and missing must-haves are review prompts, not hidden internals.

Decision trail

Reviewer notes and shortlist state stay connected to the candidate context.

Decision areaCVaultGeneric parsing
SkillsMapped to resume context where available.Keyword list with unclear origin.
ExperienceTimeline and role context remain visible for review.Flattened years-of-experience summary.
ExceptionsGaps and uncertainty are shown to reviewers.Missing context often disappears.

Reviewed rollout

Make shortlist review easier to defend.

Use a pilot to inspect the evidence loop before broader process change.

Review access options