Agent Work.

SAMPLE DELIVERABLE · LOCAL DEMONSTRATION

One blocked task.
One reproducible finding.

This is the reporting format you can inspect before commissioning a review. It uses our deliberately broken local fixture; it is not paid customer work, a testimonial, or a finding about an external service.

Download the report and runnable fixture →

Agreed scope

Obtain the fixture’s current service status using one documented GET workflow. Local Node.js server, bound to the loopback interface. No external network requests, accounts, purchases or security testing. Rechecked on 10 September 2026.

FINDING 01 · WORKFLOW BLOCKED

The documented route does not exist.

Expected
GET /v1/agent_status returns 200 and a JSON status.
Observed
The documented path returns 404. The implemented path, /v1/agent-status, returns 200 with {"status":"ready"}.
Impact
A caller following the documented spelling cannot complete this task. The sample establishes no frequency, customer loss or revenue effect.
Suggested correction
Correct the documentation, or deliberately support a compatibility alias. Add a check that executes the documented example against the service.

Reproduce the finding

  1. Inspect the JavaScript included in the downloadable report. It creates only a local HTTP fixture.
  2. Save the code as sample-review.mjs and run it with Node.js 22 or later in your own authorized environment.
  3. The script checks the documented route’s 404, the implemented route’s 200, and the returned status value, then closes its server.
Documented route: 404. Implemented route: 200.

What this does not establish

The report demonstrates a narrow documentation mismatch and a reproducible evidence format. The successful alternate path is observed; a documentation edit or compatibility alias is proposed rather than implemented in this fixture. It does not certify a service’s security, reliability or compatibility with every agent client.

How a paid review differs

We agree on your public service, one intended workflow and up to five checks before accepting work. The report identifies dated observations, reproduction steps, impact, proposed fixes and untested areas. One clarification round is included; implementation of repairs is separate.

Describe a workflow for the C$20 CAD pilot → Requesting a review does not place an order. Scope acceptance comes before a private payment link.

For a real observation from our own launch, read MCP works locally but fails after deployment.