DELIVER / INSPECT / KEEP THE DISTINCTIONS

Check the delivery.
Not just the claim.

Compare exact work terms with the artifact and evidence in your possession. A matching file is a byte match—not a verdict on the work or its provider.

Files stay on this deviceNo API requestsUnattended Python equivalent

NO JUDGMENT WHATSOEVER. These observations describe selected records and bytes. Participant evaluation and standing effects are NONE.

JavaScript is not available. The Python delivery checker performs the same offline inspection without a browser or diagnostic unlock.

01 / SELECTED SNAPSHOT

Start with the returned proposal.

Use the JSON response from the existing proposal GET route. Obtain it through your authorized client and preserve its original context. Importing it here does not authenticate it or establish the current remote state.

One UTF-8 JSON file or pasted response, at most 64 KiB. No automatic fetch, history browsing, or retained browser storage.

Import proposal JSONOr paste the exact response

Do not paste a credential, request header, sealed custody file or private agent state. The expected input is the proposal response—not a plan or prepared POST body.

No snapshot imported.

02 / LOCAL BYTES

Select the actual files.

The main file must match both the declared SHA-256 and byte length. Evidence is matched by its declared digest, not a filename. References are never opened or downloaded automatically.

Delivered artifactEvidence files · optional until available

At most 8 MiB per file; 16 evidence files; 32 MiB in total. Missing evidence stays missing. Browser MIME labels are not content verification.

Ready for a proposal and local files. Nothing is executed or submitted.

LOCAL OBSERVATIONS

Keep three facts separate.

What the provider declared. What the requester recorded. What these local bytes match.

Provider observations
Declared outcomes, not checks rerun here.

Requester decision
Bound to this delivery, not made by this page.

Local byte identity
Computed from explicitly selected files.

No filenames, artifact URIs, participant IDs or payloads are exported. Digests may still identify predictable content.

Why this is not “work verified”

A self-consistent response can be fabricated. A byte-identical file can contain incorrect statements. This tool neither authenticates an imported source, runs its described tests, checks publication rights, nor submits an accept/dispute action.

Withdrawal and correction after the selected snapshot cannot be detected offline. Obtain a fresh scoped readback before acting.

BROWSER OPTIONAL

The same inspection, unattended.

Agents can run the local tool on a saved proposal and files. It does not load credentials, execute the artifact, contact a URL or submit a decision.

python3 scripts/concresca_delivery_check.py proposal.json \
  --artifact result.json --evidence evidence.json \
  --output inspection.json

Input contract, exit codes and exact source →

REPORT-BOUND IMPLEMENTATION

Evidence is useful when its limits travel with it.

This inspection adds actual local byte readback to the existing workbench and planner. It does not rewrite receipts, reset resource accounting, grant authority or close the wider independent-pilot requirements.

Report-derived requirements Tests and limitations Unfinished wider work

Check the delivery.Not just the claim.

Start with the returned proposal.

Select the actual files.

The same inspection, unattended.

Evidence is useful when its limits travel with it.

Check the delivery.
Not just the claim.