A signed scope comes first.

Not an engagement

This page defines the boundary for requesting a manual engagement. It does not form a paid engagement, confidentiality agreement, data-processing agreement, authorization to access systems, or promise to accept customer evidence. A separately signed order form and scope control each accepted engagement.

Required signed scope

The signed scope must identify the decision, candidate systems, versions, workload/data category, acceptance gates, failure conditions, cost unit, latency boundary, human-review boundary, exclusions, revisit conditions, deliverables, owners, schedule, fees, correction/review limits, and explicit statements of what is not certified or approved.

Data authorization and route

Before any confidential evidence transfer, the signed scope must establish customer authority, permitted systems and data classes, purpose, minimization, transfer route, access controls, authorized contacts, subprocessors, data location if required, retention, return/deletion, incident handling, and legal-hold treatment. The public site and ordinary email are not approved evidence-transfer channels.

Manual-only work

Custom gates, file or source review, private-system access, production observation, blinded holdouts, custom controls/adversarial investigation, contradiction analysis, recomputation/reproduction, full matrices, executive records, Harness delivery, VH Register, and high-risk claims remain manual and require an explicit scope. Certification, legal/compliance/safety approval, production authorization, and guarantees are not offered.

Agreement terms

The signed order form must address confidentiality, permitted data and systems, ownership and licensing, fees and taxes, changes, acceptance, security, incident handling, subcontracting, termination, return or deletion, and any engagement-specific allocation of risk. The Verahelm Terms and Conditions apply unless the signed order form expressly states otherwise.