Skip to content

Phase 4 & 5 validation report PDFs + consistent phase-series roadmaps - #137

Merged
jramos merged 3 commits into
mainfrom
reports/phase4-phase5-validation
Jun 25, 2026
Merged

Phase 4 & 5 validation report PDFs + consistent phase-series roadmaps#137
jramos merged 3 commits into
mainfrom
reports/phase4-phase5-validation

Conversation

@jramos

@jramos jramos commented Jun 25, 2026

Copy link
Copy Markdown
Owner

Completes the five-phase validation-report series. Phases 1-3 already shipped
phaseN_validation_report.pdf; Phases 4 and 5 were marked done in the README but linked
only to markdown. This adds their PDFs in the same house style and makes the series
consistent.

What's here

  • Phase 4 (reports/phase4_validation_report.pdf) — tool implementation code via
    iterative test-feedback repair: the oracle-asymmetry campaign (12/20 = 0.60
    deploy-reachable, corroborated 34/46 = 0.74; difficulty curve, leakage check,
    gate-gaming audit, evolver-vs-best-of-N). 27 numbers pinned to six committed JSONs.
    asymmetry_report.pdf stays as the deep dive.
  • Phase 5 (reports/phase5_validation_report.pdf) — the propose-only triage sentinel,
    framed capability-forward, with the bug-supply / verification limits carried honestly in
    a caveats section (cross-repo supply KILL pinned to source).
  • Renderergenerate_findings_report.py gains multi-source provenance (a check may
    name its own source) and a highlight_color passthrough so the roadmap matches the
    series green. Backward compatible.
  • Series cleanup — one canonical roadmap across all five reports (each highlights its
    own phase); corrected the Phase 4 engine from the rejected "Darwinian Evolver" (AGPL) to
    "Iterative test-feedback repair" (MIT) and Phase 5 to "Propose-only triage sentinel" in
    both the roadmap and the Approach engines table; re-rendered phases 1-3 from their run
    dirs (measured numbers unchanged). README phase-table links updated; new
    reports/README.md index; findings renderer noted in AGENTS.md.

Tests

  • New banked guards assert check_provenance == [] for both new prose files, plus a
    multi-source provenance unit test.
  • Full suite green locally (pytest tests/ -q: 1665 passed, 1 skipped).

jramos added 3 commits June 25, 2026 14:13
…indings renderer

- check_provenance accepts a per-check 'source' override (top-level source is the
  default), so one synthesis report can pin numbers across several result JSONs.
- _table_block forwards an optional highlight_color, so phase reports can use the
  series green instead of the default yellow. Backward compatible; existing prose
  and tests unchanged.
Complete the phase series with two prose-driven, provenance-checked reports:

- Phase 4 (tool implementation code via iterative test-feedback repair): synthesizes
  the oracle-asymmetry campaign (12/20 = 0.60 deploy-reachable, corroborated 34/46 =
  0.74; difficulty curve, leakage check, gate-gaming audit, evolver-vs-best-of-N).
  27 numbers pinned across six committed source JSONs.
- Phase 5 (continuous-improvement loop via a propose-only triage sentinel): leads with
  the shipped mechanism; the bug-supply and verification limits are carried honestly in
  a caveats section (cross-repo supply KILL pinned to source).

Adds banked-artifact guards (check_provenance == [] for both new prose files) and a
multi-source provenance unit test.
…ndex

- Refresh the roadmap table in every phase report to one canonical, current view
  (each highlights its own phase). Correct the Phase 4 engine from the rejected
  'Darwinian Evolver' (AGPL) to 'Iterative test-feedback repair' (MIT) and Phase 5
  to 'Propose-only triage sentinel', in both the roadmap and the Approach engines
  table; re-render phases 1-3 from their run dirs (numbers unchanged).
- Point the README phase table for Phases 4-5 at the new PDFs.
- Add reports/README.md indexing the phase reports and findings deep dives.
- Note the findings renderer in AGENTS.md.
@jramos
jramos merged commit 2c4c5ce into main Jun 25, 2026
4 checks passed
@jramos
jramos deleted the reports/phase4-phase5-validation branch June 25, 2026 20:22
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