Specification-to-package reconciliation with an audit trail.
Closeout QA converts supplied O&M / closeout obligations into a requirement matrix, searches the declared package for qualifying evidence, preserves file/page citations, and forces uncertainty to remain visible until it can be resolved.
Try the product logicFree 3-requirement micro-scanRequest CAD $99 preflightWhat the product actually does
1. Preflight
Records the governing specification/revision, exact file manifest, page count, searchability, cross-references, and whether the supplied package is declared complete enough to support a missing finding.
2. Requirement extraction
Creates stable requirement IDs from explicit obligations and retains source filename, page, operative wording, modality, and identifiers such as equipment tags/model numbers.
3. Evidence retrieval
Finds candidate evidence from the declared package. File names and tables of contents are not treated as proof of required content.
4. Fail-closed classification
PRESENT needs defensible evidence. MISSING needs adequate declared scope. Ambiguous applicability, incomplete scope, weak matches, or identifier mismatch stay UNCLEAR.
5. Second-pass QA
Challenges each citation and status, verifies identifiers, rechecks missing claims, detects duplicates/conflicts, and blocks delivery when the row cannot survive review.
6. Delivery
Returns a concise summary plus the requirement/evidence matrix. Administrative next actions stay clerical and evidence-directed.
Evaluate before you buy
Interactive demo: synthetic, browser-local, no email and no customer documents. It lets you test PRESENT, MISSING, UNCLEAR, identifier mismatch, and competing-revision behavior.
Free micro-scan: one project, up to 10 total pages and 3 explicit requirements, after scope preflight. It uses the same finding structure as the paid pilot and exists to prove capability on a small real slice of work.
Paid pilot: CAD $99 after scope acceptance, target ≤250 total pages and ≤100 explicit requirements/findings.
Try interactive demoRequest free micro-scanStatus semantics
| Status | Meaning | What prevents overclaiming |
|---|---|---|
| PRESENT | Direct package evidence supports the explicit administrative requirement. | A reproducible evidence citation is mandatory and remains subject to second-pass QA. |
| MISSING | An explicit requirement has no qualifying evidence in the declared package. | AVF cannot use MISSING when package completeness itself is uncertain. |
| UNCLEAR | Evidence may exist, but identity, completeness, applicability, revision, cross-reference, or meaning cannot be established without inference. | UNCLEAR is the default failure-safe state instead of guessing. |
| CONFLICT | Supplied sources or evidence materially disagree. | Both sides remain visible; the system does not silently choose a governing source. |
Acceptance boundary
Controlled pilot: CAD $99 after scope acceptance. Target ≤250 total pages and ≤100 explicit requirements/findings. Searchable/readable inputs with stable page references are required.
Excluded: engineering/design judgment, code or regulatory compliance, legal/contract interpretation, warranty validation, professional certification, as-built certification, and owner/consultant acceptance guarantees.
Data protection
Minimum necessary: AVF uses only business files intentionally supplied for the accepted scan. Customer content is not reused for public examples, model training, unrelated benchmarking, unrelated research, or another customer's work without separate explicit permission.
No public upload shortcut: the current public intake does not accept customer files. A hosted upload path will not launch until storage, access control, encryption, retention, deletion, logging, secret handling, and adversarial security tests are explicitly implemented and verified.
Synthetic demo: the public interactive demo contains no customer data and sends no document content or interaction telemetry to AVF.
Security and privacy claims are limited to controls actually implemented and verified; AVF does not claim certifications or residency guarantees that have not been established.
Current QA posture
The product core is versioned and test-driven. Its deterministic layer covers preflight, explicit-requirement extraction, candidate-evidence retrieval, status validation, citation requirements, fail-closed missing logic, and report generation. Semantic conclusions remain reviewable; the system is designed not to automate confidence into certainty.
This page describes the current controlled pilot, not a claim of customer adoption or guaranteed acceptance.