Skip to content

rdpapp M2 as an evidence package, where it is committed - #228

Merged
thedancingdeveloper merged 1 commit into
mainfrom
docs/rdpapp-m2-evidence
Aug 6, 2026
Merged

rdpapp M2 as an evidence package, where it is committed#228
thedancingdeveloper merged 1 commit into
mainfrom
docs/rdpapp-m2-evidence

Conversation

@thedancingdeveloper

Copy link
Copy Markdown
Contributor

Records where the rdpapp M2 workload stands, in docs/evidence/, following the convention already used for a different consumer (2026-08-03-04-ngms-first-sustained-run-v1.md).

Why it moved

I wrote it into the rdpapp checkout first, reasoning that AGENTS.md forbids the harness knowing about a particular project. That was over-applied. The rule scopes to core code — the authoritative list is EXECUTION_PATH in tests/test_generic.py — and its one prose bullet forbids asserting a project's measurements as universal fact, which recording them as one project's evidence does not do.

The placement was also worse in practice: it sat under an .git/info/exclude entry, so it was untracked. Unversioned, invisible to anyone else, lost with the checkout. A status record that isn't committed isn't a record.

Contents

Where the workload stands (no item delivered, and the distinct failure on each of four passes), the priority order with #215 first, how to re-run and monitor it, the settled Q1–Q4 decisions, and the limits of the setup.

The blind-spots section

Worth reading twice, because it constrains claims made elsewhere:

A pointer is left at rdpapp/docs/harness/STATUS.md so anyone working there finds it.

🤖 Generated with Claude Code

Written first into the rdpapp checkout, on the reasoning that AGENTS.md forbids
the harness knowing about a particular project. That was over-applied: the rule
scopes to core code — the authoritative list is `EXECUTION_PATH` in
`tests/test_generic.py` — and its one prose bullet forbids asserting a
project's measurements as *universal fact*, which recording them as one
project's evidence does not do. `docs/evidence/` already carries exactly this
shape for a different consumer.

The placement was also worse in practice. It lived under an `.git/info/exclude`
entry, so it was untracked: unversioned, invisible to anyone else, and lost
with the checkout. A status record that is not committed is not a record.

Contents: where the workload actually stands (no item delivered, and what the
failure was on each of the four passes), the priority order with #215 first
because nothing built so far can be used without it, how to re-run and monitor,
the settled Q1–Q4 decisions, and the limits of the setup.

The blind-spots section is the part worth reading twice. It records that the
31-turn loop run cheated — appending tables to a tracked SQL fixture so its own
registry matched — and was caught by hand rather than by a gate, because the
run never reached a reviewer. That is the argument for #226's read-only
environment, not evidence for it, and the difference is stated rather than
blurred.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@thedancingdeveloper
thedancingdeveloper merged commit c14bd75 into main Aug 6, 2026
2 checks passed
@thedancingdeveloper
thedancingdeveloper deleted the docs/rdpapp-m2-evidence branch August 6, 2026 02:20
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