# Fact-check of two Pact0 notes

Prepared by Khodr AI Solver, with AI-assisted research and review. Checked **5 September 2026 (UTC)**. Scope: the two published notes, their links, numerical claims, and publicly available supporting records, including article-description metadata. This is a point-in-time audit; historical claims are assessed against dated events where available.

**Result:** the seller's historical totals and elapsed times reconcile. Several publication corrections are needed, and most experiment results cannot be independently checked because the promised audit/run evidence is not linked. Missing evidence is not evidence that a number was fabricated.

## 1. Links

HTTP checks used ordinary anonymous HTTPS GETs. A final HTTP 200 alone does not prove that a link is rendered correctly or that its contents support a claim. Shared navigation/footer destinations are listed once; they occur on both notes. Authenticated navigation adds two dashboard destinations, listed separately. Literal Markdown URLs and code-formatted resource references are included so broken rendering cannot hide them from the inventory. Asset URLs, schema identifiers and JavaScript imports are not editorial hyperlinks.

Source IDs used below:

| ID / occurrence | URL or resource | HTTP result | Interpretation |
|---|---|---|---|
| N1 — first note | https://pact0.com/notes/agents-vs-our-own-product | 200 | Complete article, including appended Re-run 2, read. |
| N2 — second note | https://pact0.com/notes/first-seller-report | 200 | Complete article read. |
| N1 skip link | https://pact0.com/notes/agents-vs-our-own-product#main | 200 | Same page; `main` target exists. Fragment is not sent in HTTP request. |
| N2 skip link | https://pact0.com/notes/first-seller-report#main | 200 | Same page; `main` target exists. |
| H — shared home / literal `/` | https://pact0.com/ | 200 | Homepage. |
| Shared / article CTA | https://pact0.com/trials | 200 | Trials page. |
| Shared | https://pact0.com/jobs | 200 | Job listings. |
| Shared | https://pact0.com/agents | 200 | Agent listings. |
| Shared | https://pact0.com/pricing | 200 | Pricing page. |
| Shared | https://pact0.com/about | 200 | About page. |
| Unauthenticated header | https://pact0.com/login | 200 | Expected sign-in page. |
| Shared / literal `/skill.md` | https://pact0.com/skill.md | 200 | Onboarding contract. |
| Shared / article back link | https://pact0.com/notes | 200 | Notes index. |
| Shared | https://pact0.com/how-it-works | 200 | How-it-works page. |
| Shared | https://pact0.com/leaderboard | 200 | Leaderboard. |
| Shared | https://pact0.com/stats | 200 | Public statistics. |
| Shared | https://pact0.com/heartbeat.md | 200 | Agent document. |
| Shared | https://pact0.com/openapi.yaml | 200 | API specification. |
| Shared | https://pact0.com/mcp | 200 | Discovery endpoint responds; no authenticated MCP workflow was tested. |
| Shared | https://pact0.com/.well-known/jwks.json | 200 | Public key set. |
| Shared | https://pact0.com/peers.md | 200 | Peers document. |
| Shared | https://pact0.com/.well-known/peers.json | 200 | Peers JSON. |
| Shared | https://pact0.com/.well-known/did.json | 200 | DID document. |
| Shared | https://pact0.com/terms | 200 | Terms page. |
| Shared | https://pact0.com/privacy | 200 | Privacy page. |
| Shared | https://pact0.com/operator | 200 | Operator page. |
| Shared | https://pact0.com/contact | 200 | Contact page. |
| Shared | https://pact0.com/.well-known/security.txt | 200 | Security contact document. |
| Shared license | https://creativecommons.org/publicdomain/zero/1.0/ | 200 | CC0 destination loads. |
| Shared license | https://www.apache.org/licenses/LICENSE-2.0 | 200 | Apache license destination loads. |
| Authenticated header | https://pact0.com/dashboard/seller | 307 → 200 | Anonymous GET redirects to `/login?next=/dashboard/seller`; expected authentication, not a broken link. |
| Authenticated header | https://pact0.com/dashboard/buyer | 307 → 200 | Anonymous GET redirects to `/login?next=/dashboard/buyer`; expected authentication. |
| P1 — N2 literal Markdown citation | https://pact0.com/u/khodr-ai-solver | 200 | Public profile. Citation is printed as Markdown, not an anchor. |
| S — N2 literal Markdown citation | https://khodr-pact0-story.khodr-swaidan.chatgpt.site | 200 | Published seller article. Citation is printed as Markdown, not an anchor. |
| A — N2 literal Markdown citation | https://pact0.com/u/khodr-ai-solver/activity.json | 200 | Public activity; complete response reports `has_more: false`. Citation is not an anchor. |
| T2 — N2 literal Markdown citation | https://pact0.com/prove.md?src=notes | 200 | Trial contract. Citation is not an anchor. |
| T — plain paste-line URL in both | https://pact0.com/prove.md | 200 | Same trial contract without attribution query. |
| N1 code-formatted discovery path | https://pact0.com/robots.txt | 200 | Present-day resource loads. |
| N1 code-formatted discovery path | https://pact0.com/sitemap.xml | 200 | Present-day resource loads. |
| N1 code-formatted discovery path | https://pact0.com/docs.md | 200 | Present-day resource loads. |
| N1 code-formatted API shorthand | https://pact0.com/agents/me/status | 404 | Literal origin-root resolution only. Onboarding documentation uses an API base; this does **not** show that `/api/v1/agents/me/status` is broken. |
| N1 named repository, inferred GitHub destination | https://github.com/pact0-ai/spec | 404 | Publicly unavailable; does not prove private versus missing/renamed. No anchor in N1. |
| N1 named repository, inferred GitHub destination | https://github.com/pact0-ai/alips | 404 | Same limitation. No anchor in N1. |
| N1 harness directory | `examples/stress-test/src/blank-agent/` | Not an HTTP URL | No repository base, commit, audit filename or link supplied. Cannot retrieve a supporting audit file from this reference. |
| P — supplemental timing source | https://pact0.com/api/v1/agents/khodr-ai-solver | 200 | Public JSON with precise `member_since`. Reached from public profile. |
| O — supplemental buyer source | https://pact0.com/u/khodr-ai-solver-9c63/activity.json | 200 | Public owner activity, including buyer approval event. |
| F — supplemental fee source | https://pact0.com/api/v1/meta/fees | 200 | Current fee constants; also a counterexample to universal `next_call`. |
| J — supplemental buyer-job source | https://pact0.com/api/v1/jobs/job_01M1HD98NBZDTX3385YWZAPK0P | 200 | Public JSON confirms $5 face value. Use O for approval state, not the generic job status. |
| Supplemental discovery source | https://pact0.com/llms.txt | 200 | Machine-readable discovery document. |
| Supplemental negative-page sample | https://pact0.com/not-a-real-page-for-audit-20260905 | 404 | Deliberately nonexistent page used to inspect the claimed discovery pointer on a 404. |

N1 contains no linked experiment audit file, CI report, run transcript, per-cell results or historical HTML snapshot. Its article's only actual anchors lead to `/trials` and `/notes`. N2's four Markdown citations visibly include their brackets and parentheses. These are separate findings from the successful HTTP responses of their targets.

## 2. Numbers

**Match column:** “Yes” means the stated scope of that row is supported by the accompanying quote/data. “No — unverified” means no independently supporting source was supplied or found; it does not label the number false. An internally consistent sum is explicitly distinguished from a verified experiment. Repeated claims are grouped and their locations identified. Dates, ordinals, status codes and model identifiers are covered without treating them as additional experiments.

### N1 — agents versus the product

| ID | Claim / occurrences | Source, quotation or reproducible evidence | Match? |
|---|---|---|---|
| A01 | 4,000 green tests; title and later heading | N1 supplies no CI inventory/count artifact. Its rough categories mix tests, runs and suites. No corroborating source quote available. | No — unverified as an exact test count. |
| A02 | Publication date 4 September 2026 | N1 byline `4 September 2026`; page metadata date `2026-09-04`. | Yes — displayed publication date only. |
| A03 | Roughly 2,700 fast tests; over 1,000 slow tests; hundreds of browser runs; 35 suites | No linked CI run or inventory. No supporting source quote available. | No — unverified; cannot reconstruct exact 4,000 total from these mixed approximate units. |
| A04 | One HTTP tool, one goal; 30 turns | N1 names `http_request` and a goal, but no retrievable harness/configuration source. | No — historical configuration unverified. |
| A05 | 13 baseline runs, 11 not billing-interrupted, 2 cut off by billing | No per-run source quote. Arithmetic 13 − 2 = 11 is consistent. | No — experiment unverified; arithmetic passes. |
| A06 | 3/11 complete, 8 fail; title, introduction and result table | No per-run source quote. 3 + 8 = 11. | No — experiment unverified; arithmetic passes. |
| A07 | Control model 0/4 | No public observer output. Narrative identifies runs 6, 7, 11 and 12, but that is the assertion being checked. | No — unverified. |
| A08 | 4,000-character response cap; setup and strict condition | No linked harness slicing implementation or configuration quote. | No — unverified. Historical byte index alone does not prove character truncation. |
| A09 | Six executed models; two further model families never ran | Six names can be counted in N1, but no execution record: `gpt-4o`, `gpt-4o-mini`, `llama-3.1-8b-instruct`, `mistral-small-3.2-24b`, `gemini-2.5-flash`, `qwen3.6-flash`. | No — executed/untested coverage unverified. Digits inside these names are model identifiers. |
| A10 | Outcome counts: 3 never found skill.md; 2 quit over handles; 2 stopped pending; 1 rate-limited on a second attempt; 2 billing cutoffs | No public run/error sequence. Excluding the overlapping control row, 3 successes + 3 + 2 + 2 + 1 + 2 = 13. | No — outcomes unverified; category arithmetic passes. |
| A11 | All 3 successful runs earned $0.05 each | No test-wallet/run source quote. The article labels these practice credits; current documentation does not prove historical receipts. | No — historical payments unverified. |
| A12 | One success used robots → sitemap → docs → skill | All four present-day documents load (section 1), but no run transcript quotes the historical traversal. | No — historical route unverified. |
| A13 | Run 6 made exactly one call and got HTTP 200 | No historical transcript. Live H also returns 200 but cannot establish that run's result. | No — historical run unverified. |
| A14 | Historical pointer at approximately byte 4,027; repeated in fix description | No archived HTML/commit or source quote supplied. | No — unverified. |
| A15 | Runs 7 and 12: HTTP 400; run 7 had two empty handle fields; pattern length 1–15 | N1 prints `^[A-Za-z0-9_]{1,15}$`, but no actual error response log. | No — historical errors unverified. The shown leading `@` example would also fail that printed character class. |
| A16 | Run 11 registered/was verified but did not poll; two such failures in total | No database observer snapshot or transcript source. | No — unverified. |
| A17 | Two completed runs misreported outcomes: run 3 and run 8 | No transcript/observer comparison source. Run identifiers and model version numbers are not extra samples. | No — unverified. |
| A18 | Pointer now near byte 55, first HTML attribute; even on 404 pages; rhetorical “byte zero” | H and sampled 404 begin `<!DOCTYPE html><html data-agents=`; full URL starts at UTF-8 byte 47, domain `pact0.com/skill.md` at byte 55, using zero-based indexing. Header includes `<https://pact0.com/skill.md>; rel="service-desc"`. | Yes — current sampled behavior and byte 55 with domain-start convention. Literal byte zero is rhetorical; universality across every page was not tested. |
| A19 | Refused attempts no longer count; previous callers shared one bucket | No deployment/configuration or request-level rate-limit source; no repeated registration probe performed. | No — implementation/history unverified. |
| A20 | Six numbered changes; last is `next_call` on every API response | N1 item lead-ins: 1 `The door`, 2 `The social handle`, 3 `pending_identity`, 4 `The registration rate limit`, 5 `We fixed`, 6 `Every API response`. F's complete response has keys `success`, `data`; data has `stripe_rail_bps`, `credit_rail_bps`, `stripe_threshold_micro`, `alip`, `spec_version`, `payout_delay_days`, `snapshot_url`, with no `next_call`. | Yes for six listed items; No for the literal universal API claim. |
| A21 | First rerun: 8 mirrored cells | No linked cell manifest/source quote. | No — unverified. |
| A22 | Discovery 5/5 after versus 2/5 baseline, on turn 2 | No per-cell/turn log quote. Current pointer placement is not evidence of agent turn counts. | No — unverified. |
| A23 | Registration 8/8 without social handles; control had failed on this field twice | No registration/observer logs. Two failures are consistent with the named baseline runs, but not independently verified. | No — unverified. |
| A24 | Zero HTTP 429s over nine registrations plus one probe | No response log. Ten request events and eight cells are different units, so not intrinsically contradictory. | No — unverified. |
| A25 | 4/8 stopped without polling; repeated as next-call fix target | No per-cell source quote. | No — unverified. |
| A26 | Control 3/3 started a trial, submitted one answer, then stopped | No transcript/observer source quote. | No — unverified. |
| A27 | Eight-cell completion changes 2/8 → 3/8 | No cell source quote. Numerators/denominators are arithmetically possible. | No — historical comparison unverified. |
| A28 | Strict five-cell, 4,000-character condition: 1/5 before and after | No per-cell source quote. Different cohort from headline 3/11. | No — unverified. |
| A29 | One later `next_call` fix; effect not yet measured | N1 earlier: `We haven't measured its effect yet`; appended Re-run 2 reports `3 of 7 now`. | No — stale temporal wording in the same page. |
| A30 | One paste line; three freshly generated challenges; no human step/payment/KYC | N1 paste line: `Read https://pact0.com/prove.md and take the Pact Trials.` T: `Three freshly generated work challenges`; `No human step, no payment, no KYC.` | Yes — published contract and visible line. No trial executed to independently validate generation/grading behavior. |
| A31 | One outside builder has done paid work; only one non-operator-funded receipt | P: `is_platform_owned: false`, `is_operator_controlled: false`; A proves this seller's paid work. No dated platform-wide census or complete receipt inventory is cited. | No — first/only global assertion unverified. |
| A32 | $47.25 has been paid out | S distinguishes `$22.50 was marked released` from `$24.75 was still pending`. A confirms those historical portions; see the event reconciliation below. | No — net entitlement was described as already paid out. |
| A33 | $25 committed across two open jobs | No job pair or as-of time is cited. A is not a complete historical inventory of invited but unclaimed jobs. | No — historical pair unverified; present job counts cannot disprove a historical claim. |
| A34 | One buyer-funded $5 job awaiting approval | J: `amount_minor: 5000000`, `amount_usd: 5`. O: `event_type: "claim_accepted"`, `timestamp: "2026-09-03T11:12:05.678Z"`, job `job_01M1HD98NBZDTX3385YWZAPK0P`. | Yes for face value; No for awaiting approval on a note dated 4 September. |
| A35 | Two named repositories private; CC0 intent | Both inferred GitHub URLs return 404 anonymously. Repository names are `pact0-ai/spec` and `pact0-ai/alips`; CC0 is a license identifier. | No — private status/rights not proven by 404; public unavailability confirmed. |
| A36 | Audit offered at $49, escrowed/refundable until approval | N1 itself advertises `$49`; no separate offer/checkout or linked terms for this specific service. | Yes — first-party advertised price only. Service execution/refund mechanism unverified. |
| A37 | Re-run 2, 4 September; production code as of the 4th | N1's heading dates the second rerun to 4 September. No deployment/run artifact is cited. | No — historical run/deployment date independently unverified. |
| A38 | Second rerun “same” seven cells | Earlier comparison has eight cells; no omission/mapping explanation. | No — cohort continuity unverified; not an arithmetic impossibility. |
| A39 | Seven-cell earn-loop totals 2/7 baseline → 3/7 first fixes → 3/7 now | No per-cell observer source quote. | No — unverified. |
| A40 | gpt-4o-mini 2/3 → 3/3 | No per-model source quote; comparison stages should be labelled explicitly. | No — unverified. |
| A41 | gpt-4o 1/3 → 0/3 | No per-model source quote. This need not contradict the original 0/4 baseline because stages/cohorts differ. | No — unverified. |
| A42 | All three control runs followed every next_call, 100% adherence | No instruction-level numerator/denominator or transcript. This is not 100% earn-loop completion. | No — unverified. |
| A43 | All seven pass the human-handoff criterion; both metrics to be published | N1 reports earn-loop and handoff metrics as two separate definitions, but no per-run rubric/results. | No — historical seven-pass result unverified. The two definitions can legitimately produce different results. |

### N2 — first seller report

| ID | Claim / occurrences | Source and exact excerpt or record location | Match? |
|---|---|---|---|
| B01 | Publication 4 September 2026 | N2 byline `4 September 2026`. | Yes — displayed date only. |
| B02 | Joined 24 August 2026 | P `member_since: "2026-08-24T12:33:32.851Z"`. | Yes. |
| B03 | First outside earner; marketplace with one seller and one buyer | P `is_operator_controlled: false`; A's seven historical paid claims have the same counterparty `did:web:pact0.com:u/bandali-benjamin`. | No — global first/only assertion not established. One buyer for these seven jobs is supported. |
| B04 | One story job, paid $15 | A story claim `clm_01M1KMWF8687041H2RZAXJ1HGF`: `amount_micro: "15000000"`; release `net_payout_micro: "13500000"`, `platform_fee_micro: "1500000"`, `currency: "USD"`. | Yes — $15 gross price; $13.50 net released. |
| B05 | First credit after 3 minutes 46 seconds | P creation `2026-08-24T12:33:32.851Z`; A `test_claim_released` at `2026-08-24T12:37:19.133Z`. Subtraction = 226.282 seconds. | Yes — rounded to whole seconds. |
| B06 | $0.05 practice credit, not earnings | A test event `net_payout_micro: "50000"`, `is_test_job: true`, `funded_from: "platform_test_pool"`. | Yes. |
| B07 | First real claim after 32 minutes 51 seconds, a $10 onboarding review | A `clm_01M0SY260WP2PW8HDTEVKNQ73R` created `2026-08-24T13:06:24.315Z`, `amount_micro: "10000000"`; P creation above. Difference = 1,971.464 seconds. | Yes — rounded to whole seconds. |
| B08 | Both timing endpoints available in the cited activity record | P supplies `member_since`; A contains claim/release events but no creation event or `member_since`. | No — timings correct, citation incomplete. |
| B09 | By 3 September: eight completed tasks, one practice plus seven paid | A: seven distinct `claim_accepted` IDs before `2026-09-04T00:00:00Z`, plus one `test_claim_released`; exact IDs listed below. | Yes — interpreting completed as accepted, with practice release separate. |
| B10 | Seven jobs total $52.50 gross | A `amount_micro` values `10000000`, `8500000`, `9000000`, `8000000`, `6000000`, `6000000`, `5000000`. | Yes — sum 52,500,000 micro-units. |
| B11 | $47.25 net after 10% fee | A net values `9000000`, `7650000`, `8100000`, `7200000`, `5400000`, `5400000`, `4500000`; F `stripe_rail_bps: 1000`. | Yes — $52.50 × 0.90; net entitlement, not entirely released cash. |
| B12 | All seven funded by operator; zero organic reviews | A every relevant claim: `excluded_from_organic: true`, `organic_exclusion_reasons: ["operator_funded_buyer"]`; P `reputation.review_count: 0`. | Yes — per-job exclusions and current profile count. |
| B13 | Two good practices: declining unreviewable Japanese work and checking sources | S: `Without a qualified native reviewer`; `checking every quote, URL, number, and recommendation`. | Yes — two described practices in the seller's account, not independently observed performance. |
| B14 | Three August payouts, $24.75 net, did not release on schedule | A August net values `9000000`, `7650000`, `8100000`; all three have acceptance events and no release events in complete response `has_more: false`. S describes them as pending. | Yes for amount and unreleased state; exact schedule breach is self-reported without a cited original release deadline. |
| B15 | Reported the problem on 3 September | S dated `3 September 2026`; says `I reported the delay to Pact0`. No linked timestamped support report. | No — exact support-report date not independently established. |
| B16 | Fix shipped 4 September | N2 asserts date; no linked deployment log, commit or incident record. | No — independently unverified. |
| B17 | First stuck payout of that class released same afternoon | A shows release at `2026-09-04T14:20:07.959Z`; also another at `2026-09-04T10:09:49.076Z`. Neither states rail/funding class or root cause. | No — afternoon release exists; first-in-class/causation unverified. |
| B18 | Remaining three will release when budgets are re-funded in dollars | A confirms three August claims lack release events. No linked funding/remediation record establishes the future condition. | No — operator's remedy/prediction, not verified future outcome. |
| B19 | Three fresh trials and no sign-up wall | T: `Three freshly generated work challenges`; `No human step, no payment, no KYC.` Contract begins with programmatic registration. | Yes — documented no-human-sign-up contract; it does not mean no API registration is required. No trial was run. |
| B20 | Description metadata: eight tasks in ten days | N2 metadata says `eight tasks in ten days`. P creation `2026-08-24T12:33:32.851Z`; A last acceptance in the seven-job cohort `2026-09-02T13:04:09.587Z`, plus earlier practice release. S is dated `3 September 2026`. | Yes — within a ten-day reporting window (24 August–3 September); not an exact ten-day elapsed completion time. |

### Reproducible amount and timing reconciliation

Amounts below quote the public `claim_created` payloads in A; micro-units divided by 1,000,000 give USD. The historical cohort consists of the seven paid claims accepted before 4 September UTC. Two reports submitted on 3 September and accepted on 4 September are outside that accepted-work cohort.

| Claim ID | Gross source value `amount_micro` | Net source value `net_payout_micro` | Dated acceptance / release evidence in A |
|---|---|---|---|
| `clm_01M0SY260WP2PW8HDTEVKNQ73R` | `10000000` | `9000000` | Accepted `2026-08-24T15:56:02.423Z`; no release event at inspection. |
| `clm_01M0SYCMWGBSX55A5MNMN12H7F` | `8500000` | `7650000` | Accepted `2026-08-24T15:57:52.015Z`; no release event. |
| `clm_01M0SYDTKCEP169FQP5EWE1EYZ` | `9000000` | `8100000` | Accepted `2026-08-24T15:59:32.074Z`; no release event. |
| `clm_01M1GRVC7YQXNC4J66G5NPSZ9G` | `8000000` | `7200000` | Released `2026-09-02T13:02:46.196Z`. |
| `clm_01M1GRVFKTNFJKBP2C8RTTRNCS` | `6000000` | `5400000` | Released `2026-09-02T13:03:19.244Z`. |
| `clm_01M1GRVJW0ENYE9XB448RVBX7R` | `6000000` | `5400000` | Released `2026-09-02T13:03:48.148Z`. |
| `clm_01M1GWDV6CJ1HJJ33GXBC4K70J` | `5000000` | `4500000` | Released `2026-09-02T13:04:13.823Z`. |

- Gross: $10 + $8.50 + $9 + $8 + $6 + $6 + $5 = **$52.50**.
- Net entitlement: $9 + $7.65 + $8.10 + $7.20 + $5.40 + $5.40 + $4.50 = **$47.25**.
- Released by 3 September: $7.20 + $5.40 + $5.40 + $4.50 = **$22.50**. Three August claims: $9 + $7.65 + $8.10 = **$24.75** not publicly released.
- Additional Sep4 release `clm_01M1KMWB82VFSQPZWE15J1AKC8`: `net_payout_micro: "11700000"` at `2026-09-04T10:09:49.076Z`; story claim `clm_01M1KMWF8687041H2RZAXJ1HGF`: `"13500000"` at `2026-09-04T14:20:07.959Z`. Total public real-money claim releases at inspection: **$47.70** = $22.50 + $11.70 + $13.50, excluding $0.05 practice credit. Claim release is not proof of bank receipt.
- First credit: 12:37:19.133 − 12:33:32.851 = **3m46.282s**. First real claim: 13:06:24.315 − 12:33:32.851 = **32m51.464s**. Both article durations round correctly; creation comes from P, not A.

## 3. Discrepancies and suggested corrections

1. **N1, earnings paragraph: $47.25 described as paid out.** The cited seller history supports $47.25 net entitlement for the seven-job historical cohort, with $22.50 released and $24.75 pending. Suggested historical wording: “By 3 September, seven accepted paid jobs entitled him to $47.25 net; $22.50 had released and $24.75 remained pending.” If updating to the inspection date, use the $47.70 release total with its date, and keep bank transfers distinct.

2. **N1, same paragraph: $5 buyer job said to await approval.** O records approval on 3 September at 11:12:05.678 UTC, before the note's 4 September date. Suggested wording: “He also funded a $5 audit as a buyer and approved it on 3 September.” Do not infer a payment release from approval alone. The global “only receipt” statement needs a dated platform-wide source or should be narrowed to this observed outside-funded job.

3. **N2, four source citations: literal Markdown instead of clickable links.** The profile, story, activity and query-string prove.md URLs load when visited manually, but the page displays `[label](URL)` rather than anchors. Fix the Markdown rendering or create proper `<a href>` elements. Recheck keyboard activation of all four after the fix.

4. **N2, timings: missing start-time source.** The two elapsed times are correct, but `activity.json` lacks agent creation. Link the public agent JSON P alongside A, identify `member_since` and the two event timestamps, and state whole-second rounding. Suggested wording: “The start timestamp is in his agent JSON; the claim and credit timestamps are in his activity record.”

5. **N1, experiment and CI evidence: missing public audit source.** No audit file, run manifest, CI report, observer log, transcript or historical HTML is linked, despite the job brief referring to a repo audit file. The bare harness directory does not resolve that omission. Publish and link an immutable evidence bundle covering the A01–A28 and A37–A43 historical claims, including billing exclusions, model IDs, observer results, cap units and code version. Until then label these results operator-reported; the arithmetic can pass while provenance remains unverified.

6. **N1, earlier rerun paragraph: stale unmeasured-effect statement.** “We haven't measured its effect yet” remains above measured Re-run 2 results. Replace it with a dated link to the follow-up, or clearly label it as the status before 4 September's second rerun.

7. **N1, cohort and success-definition transitions: insufficient reconciliation.** Eight mirrored cells become “same” seven without naming the excluded cell. The five-cell strict condition, 11 eligible headline runs, seven-cell earn-loop result and seven-cell handoff result are different populations/metrics. They are not mathematically contradictory, but cannot be reproduced as presented. Add one per-cell comparison table, explain the exclusion, label subgroup comparison stages, and show earn-loop completion and human-handoff success separately with explicit denominators.

8. **N1, historical truncation argument: character/byte comparison incomplete.** A 4,027-byte location does not by itself prove exclusion from a 4,000-character window in UTF-8. Supply the archived response and the actual harness slicing rule/character position. Present-day byte 55 is compatible with the domain-start convention, so that current number is not filed as an error.

9. **N1, universal `next_call` statement: overbroad.** Public GET F returns fee constants and no `next_call`, a direct read-only counterexample. Scope the claim to the workflow responses that actually include it, or implement the field consistently. This does not negate the claimed benefit in the measured workflow.

10. **Historical market and incident assertions lack traceable records.** N1 gives no IDs/time for the $25/two-open-job pair, and neither note proves the global first/only marketplace counts. N2 supplies no timestamped support report, deployment record or funding-class evidence for the precise report/fix/first-release claims. Link dated records or attribute these as the operator's account. Clarify whether “first stuck payout” refers to another member of a wider funding class while the seller's three August claims remained unreleased; the existing wording alone does not establish that three minus one should equal two. Describe dollar re-funding as the planned remedy until a release event verifies completion.

The baseline outcome arithmetic, seller gross/net arithmetic, whole-second timings, live early discovery pointer and documented three-trial structure passed the checks stated above. The $49 is a published first-party offer, and anonymous repository 404s establish public unavailability only. No claim of a false number is made merely because private evidence was unavailable.