What shipped
A standalone Node.js 20 CLI creates, generates, validates, and bundles a strict ten-case before/after evidence pack for one local workflow. It includes a conspicuously fictional five-system fixture, exact schemas, closed state semantics, deterministic exception and diff logic, source/artifact SHA-256 binding, atomic directory publication, static service collateral, and a dependency-free verifier.
Architecture
The package uses only Node built-ins and POSIX Bash. Inputs are parsed strictly before normalization; JSON duplicate keys and unsafe CSV cells fail closed. Outputs are rendered into a sibling candidate, validated against hashes and deterministic regeneration, source-hashed again, then atomically renamed. Read-only validation rebuilds expected bytes instead of trusting the manifest. The parent export is consumed only as a copied-by-value input with narrow field resolution.
Trimmed scope
There is no UI, API, connector, provider adapter, browser automation, database, model call, monitoring, scheduler, credential flow, deployment, billing, outreach, or external mutation. The workflow is one linear chain with three to seven steps; the fixed service accepts one location, up to five systems, exactly ten cases, and one recorded repair.
Limitations
Facts and observations are supplied or synthetic. The tool records but does not execute repairs. Ten cases do not establish future reliability. Queued is not sent, sent is not delivered, and completed is not paid. Before/after sequence does not prove causation. No reliability, delivery, payment, revenue, or recovered-revenue guarantee is made. Evidence references are opaque strings and attachments are not ingested.
Verification
bash verify.sh passes on Node.js 20+ with no installation, credentials, network, browser, model, or external service. The suite runs 23 assertions/subtests plus end-to-end sample, generation, read-only validation, bundle, mutation, deterministic-directory, fixed-claim, parent-integrity, and standalone-copy checks. Final result: VERIFY PASS: deterministic local evidence-pack workflow.
Suggested next steps
Keep the package frozen until Michael explicitly unfreezes it. Hold the fixed offer constant for no more than three approved qualified offers. Extend only after one paid sprint or one qualified usable sanitized evidence set identifies a repeated handoff; then consider a narrowly scoped read-only import format before any provider adapter.