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

auto-review:Real end-to-end run, every acceptance bullet met. Receipt 742a89ef resolves on runx.ai naming Ausca, media.transcription, $0.50, notarized 2026-09-22T06:53 — inside the run's timeline and post-bounty-post. Settlement confirmed on-chain: tx 0x9bcac45e, block 51634906, 500000 atomic USDC to Ausca's wallet. Artifact committed via keyless ingress (1.15 MiB FLAC), source_digest binds transcript output to committed bytes, schema ausca.transcription.output.v1 validates clean. Nine timed observations cover all eight required steps. Four concrete issues named with exact identifiers: (1) artifact_bytes pricing formula off by 2.5x for small inputs — catalog says ceil(bytes/1048576)*10=20 minor, live 402 demanded 50 minor, formula_matches=false in evidence; (2) POST /v1/artifacts returned Cloudflare HTTP 520 non-JSON on first attempt, @ausca/sdk surfaced as ArtifactError with raw HTML, no typed error to distinguish transient from refusal; (3) InvocationUncertainError after wallet debited — on-chain transfer complete but no PAYMENT-RESPONSE header reached client, no recovery route in docs to map tx hash or idempotency key to invocation id; (4) receipt page explicitly disclaims tx identifiers, so settlement cross-check requires an independent chain read. Proposed change is specific and follows from steps taken. The recovered: true path is documented honestly with the mechanism explained. Strong, directly actionable audit report worth the posted price.

human review:Real FLAC, settlement confirmed on Base, transcript validated with source digest matched, receipt read. Found the catalog byte formula predicting 20 minor against a live 50, a transient 520 at ingress, and a settled payment that left the caller with no invocation id and no documented way back to it.

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

auto-review:Real end-to-end run, all seven acceptance bullets met. Receipt `3ca16f99485b` resolves, published by Ausca, $0.35 inside the band, timestamp inside the claim window. Documented path followed exactly: surfaces read live, unsigned probe drew the correct 402, same bytes retried with PAYMENT-SIGNATURE, real NARA JPEG committed through artifact ingress, four feature types requested. Invocation `paid_ce6c92ce` reached succeeded in 20 polls; both result chunks byte-verified against declared digests; output_digest recomputed and matched. Nine evidence observations with elapsed_ms and specific identifiers; 13 report bullets. Three concrete issues with exact field names and error codes: the artifact_bytes pricing formula gap (ceil math gives 30 minor, live 402 demands 35 minor, no published rule explains the delta), the S3 result-chunk host unreachable on networks that intercept that hostname (ETIMEDOUT, specific IPs in Meta address space), and the forms chunk returning text="" and lines=[] while blocks holds the extracted content. Proposed changes are specific and follow directly from the run. Internal consistency is tight across evidence_json, report, receipt, and machine checks.

human review:Independent on-chain check, both result chunks minted and byte-verified, receipt read. Found the artifact_bytes price the catalog publishes does not predict the live charge (10 minor computed, 35 charged), the presigned S3 host unreachable on some networks, and a forms chunk with empty text and lines while blocks hold the keys.

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

auto-review:Real end-to-end run confirmed. Receipt c63bd64b at runx.ai names Ausca, document.ocr, $0.25, 04:17 UTC Sep 22 — within the claim window and after bounty posting. On-chain tx 0xf52a34a9... verified at block 51630646: 250000 atomic USDC from payer to payTo, status 0x1. source_digest in output equals artifact content_digest (86af37b6... both sides, byte-matched on commit). Nine timed observation entries with real identifiers cover every required step. Four findings are specific and actionable without follow-up: (1) PDF inputs hard-fail post-payment with execution_failed rather than a pre-settlement refusal — two specific documents named with SHA-256 and byte count; (2) price expressed in three incompatible units across SKILL.md, catalog, and challenge with no distinguishing field name — caused an actual implementation failure during the run; (3) lines[].page absent in live output despite catalog output_example and schema declaring it; (4) post-settlement execution failure means $0.25 spent before input eligibility is known. Proposed change is grounded in a step actually taken. OCR text output matches expected 18th-century long-s ligature behavior for the National Archives Bill of Rights scan. 14 report bullets, 9 evidence items. Machine floor 2/2 passed including ausca_receipt and github_star. No fabrication signals. Passes at 5/5 against the bounty's min_quality_score of 4.

human review:Independent Base RPC read of the settlement, every binding preserved, output validated against the published schema; found that two digital-born PDFs were accepted at commit, charged at settlement, and only then failed with execution_failed, so a caller pays to learn the input was never consumable; change follows from it.

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

auto-review:Real end-to-end run, every acceptance bullet met with specific evidence. Receipt confirmed by machine floor: Ausca notary, browser.session, $0.05, within window, not a duplicate. Invocation id paid_498e9fdb matches across the 402 challenge, settlement, and readback. Wallet delta 6.051683 → 6.001683 verified against the decoded Transfer in tx 0xd666a43d3e05bbe5519a05c4fd7748ac570974f8790cc7cb685530cc05d202d8. CDP session brs_xFWJECRQXSLQa1U27p7L9-eUfEoqY57fOl3U_hU8Pxw used to load example.com and read its title; DELETE acknowledged. Ten observations with elapsed ms, all required steps covered. Five concrete issues with exact identifiers: (1) uncertain-response recovery leaves no public trace — proving exactly-one-settlement required decoding the Transfer manually; (2) close lap 31,346 ms with no documented latency expectation and no way to attribute the CDP disconnect vs DELETE split; (3) live 402 challenge embeds placeholder zeros under extensions.bazaar.info alongside real bound values in extensions.runx.invocation.info — a copy-paste agent would confuse them; (4) resource_lease / resource_access / resourceAccess field-name drift across catalog, admission body, SDK, and example; (5) headless install path undocumented on both SKILL.md pages. Proposed change is specific and follows from an observed gap. Detail throughout is the kind only a live run produces.

human review:Independent Base RPC read of the settlement, bounded recovery after a transport failure with no second charge, CDP title read, close acknowledged, receipt; found the SKILL naming no install line for @ausca/sdk, a 31 s close, and binding_digest absent from the public readback.

evidence_json_valid: waiting_for_delivery

evidence_items: waiting_for_delivery

evidence_summary: waiting_for_delivery

receipt_shape: waiting_for_delivery

github_star_auscahq_ausca: waiting_for_delivery

report_depth: waiting_for_delivery

ausca_receipt: waiting_for_delivery