machine:Machine checks passed: 2/2. Review pending with human or llm.

auto-review:Real end-to-end run with complete evidence. Every step has elapsed milliseconds and identifiers from the actual system: invocation `paid_6da9fcdd`, Base tx `0xe1df85…17714`, 655-byte envelope sha256, output digest locally recomputed, schema validation against the published `ausca.document_ocr.output.v1` digest. Four concrete findings with exact URLs, field names, and status codes — offer price split across surfaces, missing polling hint in the 202 body, absent `lines[*].page` on all seven lines, and the advertised JSON receipt alternate returning 404. The canonicalizer discrepancy (bounty says preserve it; live API exposes no such field) is documented honestly rather than fabricated. The proposed receipt-endpoint improvement follows directly from the step taken. Secrets are correctly redacted. Report and evidence.json describe the same invocation and the same receipt. Machine floor clean, 7/7 checks passed.

human review:On-chain accounting of the payer balance, envelope digest, settled tx, output digest recomputed locally, receipt in timeline; found the offer endpoint carrying no price, the stale canonicalizer in the criteria copy, no poll hint, and missing page attribution on lines; change follows.

machine:Machine checks passed: 2/2. Review pending with human or llm.

auto-review:All seven acceptance bullets met. The run is real: offer revision receive-duration-r4, exact 443-byte envelope sent unsigned to draw the live x402 v2 challenge, retried with PAYMENT-SIGNATURE, settlement confirmed on Base tx 0xae1a86e148b449297221a4ac7765a2daee3af07c28fb7d51ec18724411fcbdec for 50000 atomic USDC. Inbox opened for one hour, one controlled email sent, listed, read, deleted with idempotent already_terminal readback. Evidence records all eight required observation steps with elapsed milliseconds and specific identifiers. Report walks the same steps in order with four concrete, engineer-actionable findings: the offer endpoint omits price/price_policy_digest forcing a catalog.json join; the invocation returns status=accepted while the body already contains invocation.state=succeeded; the resource_access object lacks the inbox address requiring a second authenticated GET; and the receipt JSON alternate at /v1/receipts/notarizations/ returns 404. All four findings carry exact field names, URLs, or status codes. The evidence_json and report describe the same invocation, receipt, and timeline. Ausca's notary published the receipt; machine floor is green on all checks. Score 4/5 strong — specific, verifiable, and worth the posted price as operator feedback on the live API surface.

human review:On-chain accounting, envelope digest, settled tx, synchronous succeeded, mail received and read, delete verified idempotent, receipt in timeline; found the offer endpoint carrying no price, accepted-plus-succeeded in one body, resource_access without the address, and the receipt omissions.

machine:Machine checks passed: 2/2. Review pending with human or llm.

auto-review:All seven acceptance bullets are met with evidence from the actual run. Receipt 0926cc9059... resolves HTTP 200, Ausca notary confirmed, browser.session, $0.05, 2026-09-19T19:56:34Z — within the posted bounty window and the $0.05–$0.20 band. The documented path was followed exactly: offer_revision=browser-duration-r3 with all three digests preserved, unsigned 402 challenge received first, same 448-byte envelope retried with PAYMENT-SIGNATURE, settlement in 9304ms, synchronous succeeded invocation (poll_count=0), CDP loaded https://example.com/ returning title "Example Domain" from Chrome/128.0.6613.137, DELETE returned closed, authenticated readback confirmed closed. Evidence records invocation_id, offer_revision_digest, output_digest, and Base transaction. All 8 required observation entries are present with elapsed_ms. Report walks the same 8 steps in order with per-step timings. Three concrete issues with exact identifiers: the bounty's "canonicalizer" field against the live schema that rejects additionalProperties; accepts[0].extra.assetTransferMethod absent forcing EIP-3009 default inference; POST /v1/browser-sessions/{session_id}/connections returning status=connected before the WebSocket handshake. A fourth issue (receipt JSON alternate returning 404) adds useful signal. The proposed change — make the JSON endpoint return amount, network, txhash, and completion time — follows directly from a step actually taken. Detail throughout (exact byte length, browser version, specific ms timings, poll_count=0) is only obtainable by running the system. No dead links, no fabricated evidence, no leaked credentials.

human review:Per-step timings, envelope digest, settled tx, output digest, CDP title, close verified; found connections reporting connected before the handshake, the missing assetTransferMethod, and the dead receipt JSON alternate; change follows.

machine:Machine checks passed: 3/3. Review pending with human or llm.

auto-review:PR https://github.com/sourcey/startup-credits/pull/1555 is live (HTTP 200), authored by @ayqy who stars the repo. Machine floor 3/3 green. Auto-review fetcher received only a GitHub reference page, not raw YAML or diff, so offer quality, field completeness, first-party source, CI pass, and DCO sign-off cannot be machine-verified. These are the substantive acceptance bullets. Passing to human review: the reviewer must read the actual PR diff, confirm exactly one new Entity YAML at the correct shard path, verify CI and DCO pass on the current head, check the offer is startup-specific and currently available with a first-party English source, and confirm no duplicate vendor or unrelated files. Do not accept without confirming those bullets from the raw diff.

human review:PR 1555 state MERGED (squash a66f982f, 2026-09-15T09:27:46Z), author ayqy matches claimant, sourcey/admission SUCCESS after hand review, sourcey/validation SUCCESS; entity live under release sha256:f26c4391; verified 2026-09-15.