Exploration report
Probe the local files and produce a readable report: ready workflows, needs-review paths, blocked paths, customer questions, and next commands.
Start with one local back-office workflow. The probe maps where automation fits, then Vigil turns approved Excel or CSV files into clean outputs, archive records, error evidence, and support diagnostics through an assisted package handoff. No hosted upload service, no hosted account area, no unpredictable agent, and no change to your source files.
The pilot is intentionally narrow: explore the file reality, choose the repeatable task, install the local runtime, prove the output, then support the run with evidence.
Probe the local files and produce a readable report: ready workflows, needs-review paths, blocked paths, customer questions, and next commands.
Install the local Vigil runtime, configure folders, templates, SMTP when needed, receipts, and the support-bundle path from the handoff package.
Review the install receipt, first-workflow dry run, readiness gate, activation artifact, progress check, and support evidence.
Record what was installed, where it lives, and which local folders it uses.
Run one approved source file non-destructively and review the generated outputs.
Confirm row counts, output counts, archive behavior, and error isolation before activation.
Turn on monitoring only after the customer reviews the activation artifacts.
Verify the live workflow behaves like the dry run while the manual process remains available.
Keep a redacted support path ready if the workflow needs operator review.
Bring one repetitive spreadsheet or folder-based task. Vigil will explore it, install locally, prove the output, and keep the evidence visible before expanding scope.