Skip to content

Launch Evidence-Based AI Engineering - #25

Merged
jadercorrea merged 3 commits into
mainfrom
research/agent-evidence-scanner
Jul 29, 2026
Merged

Launch Evidence-Based AI Engineering#25
jadercorrea merged 3 commits into
mainfrom
research/agent-evidence-scanner

Conversation

@jadercorrea

Copy link
Copy Markdown
Owner

What changed

  • adds replayable, failure-inclusive local-agent evaluation infrastructure
  • publishes the filesystem-containment position paper and a 1,071-word technical brief
  • adds an accessible, reusable capability-versus-reliability result figure
  • prepares evidence-linked copy for LinkedIn, X, Hacker News, and a five-minute video
  • links the analysis to the immutable ai-experiments release 2026.07.29.1

Why

A selected successful run demonstrated bounded capability but could not support a reliability claim. The following three-run campaign timed out every time. Publishing both campaigns, their negative artifacts, and their limitations makes the engineering claim inspectable instead of promotional.

Validation

  • make verify
  • Jekyll production build
  • 17 site tests with 241 assertions
  • Go race detector on the public example
  • 100% statement coverage on the public example
  • full-resolution review of the SVG and PNG result figure
  • all ten X posts measured below 280 characters

Limitations

The historical runner predates a retained immutable build revision, and the successful filesystem patch retains a possible symlink check-to-write race. Both limitations are documented. The capability check and repeatability campaign remain separate because they served different experimental purposes.

Test and others added 3 commits July 28, 2026 16:25
Add a content-free Codex evidence scanner and a TDD-built, path-safe ordered patch replayer. Validate repository and turn-level evidence across the local corpus, exercise verification inside a locked-down Docker container, and document the critical finding that legacy sessions omit the initial dirty-worktree baseline required for deterministic replay.
Local agent runs were not credible evidence: historical sessions lacked reproducible baselines, fresh runs hid progress until completion, Ollama used a fixed timeout, and retry budgets could be exhausted without measurable improvement. The same gaps made local execution slower, opaque, and easy to overstate.

Build deterministic, replayable evaluation bundles around clean fixtures; ground planning and retries in repository contracts; stream verbose stages while preserving captured output; tune Ollama timeout and context for available hardware; and stop equivalent verification plateaus early. Strengthened fixtures retain false positives and failures, while reviewed Qwen cache and Devstral filesystem results demonstrate bounded, zero-API-cost capability.

General reliability still requires repeatability across more fixtures. The Devstral filesystem result is one reviewed contract pass, and its generated patch is not claimed as a race-free filesystem primitive against an actively hostile concurrent process.
The local-agent study had the depth of an engineering paper but made its central capability-versus-reliability result expensive to discover and difficult to distribute outside the site.

Launch Evidence-Based AI Engineering with an executive summary, accessible experiment figure, stronger conclusion, 1,071-word technical brief, and measured copy for LinkedIn, X, Hacker News, and a five-minute video. Tie every format back to the immutable evidence release and protect the editorial contract with site tests.

The paper remains the canonical technical account and the brief is an entry point, not a replacement. Browser-based page inspection was unavailable in this session, so the generated HTML, responsive markup, full-resolution graphic, Jekyll build, and repository quality gate were verified independently.
@jadercorrea
jadercorrea merged commit af9c947 into main Jul 29, 2026
1 check passed
@jadercorrea
jadercorrea deleted the research/agent-evidence-scanner branch July 29, 2026 17:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant