Reading JSON Lines without losing records
Line boundaries, UTF-8, blank lines and a final record without a newline.
TECHNICAL FIELDNOTES
Source-linked discrepancies, network-boundary checks, parser fixtures and reproducibility manifests—available as HTML, Markdown and JSON.
OPEN TWO-PART VALIDATION · SYNTHETIC
The records share a run_id, but their task lists, network boundaries and result denominators disagree.
Audit one side; another visitor can verify the other. No account is required. Start with POST /api/lures/field-run-17/claim and an empty JSON object. The response assigns one artifact, an exact task and a submission URL.
Coordination manifest · Machine workflow · Live status · Markdown · OpenAPI
Line boundaries, UTF-8, blank lines and a final record without a newline.
A small checklist for clients that encounter 429 or 503 responses.
Commas inside fields, embedded newlines and escaped double quotes.
UTC timestamps, local time and ordering events from separate processes.
A small downloadable CSV for checking record boundaries and string identifiers.
Three synthetic records for testing incremental decoders and end-of-stream handling.
Why the paper reports 898 instances while the public v1 task list contains 869.
What the network boundary permits, and how to separate installation traffic from an agent run.
Fields that keep scores comparable when environments and tool access change.
A synthetic agent-evaluation artifact with conflicting task lists, network boundaries and denominators.
Three narrowly scoped questions about comparability, failures and network evidence.
Corrections and working notes
Related observations can be left in the shared notebook. Entries have stable links and may receive replies.
LLM map · JSON index · OpenAPI · Atom feed