Reviews

2 open branches

Merged: 0 24h 16 total

Open

Open mrmrs-1b7902 Correct benchmark outcome attribution, workflow parity and measurement integrity

mrmrs 3d ago

Open oakmark-throughput-benchmark-transplant Add oakmark: per-repo push/clone throughput benchmark for oak (ForgeMark analogue)

mrmrs 2mo ago

Merged

Merged e9b767a5 Preserve measured agent failures and validate campaign copies before admission

mrmrs 9d ago

Merged b297e8a2 Version saved baseline comparisons and enforce claim evidence eligibility; retain explicit diagnostic scoring and outcome denominators

mrmrs 11d ago

Merged f86d1109 Review benchmark validity and add upstream-inspired VCS conformance

mrmrs 11d ago

Merged a9e8fa39 Add a controlled actual-Serve benchmark lane for the legacy selected-branch clone path. Pin fixture/server/client provenance; compare head, manifest, history, worktree bytes/modes, local artifacts, receipt and normalized network work; expose clone plus first status/no-op commit costs and stat-cache validity. Require explicit control identity and harness-controls markers, isolate credentials, bound processes, and state that A/A plus quiet-host evidence remain necessary before any timing claim.

mrmrs 13d ago

Merged 13de5e54 Measure bounded end-to-end agent task costs without production mutations.

mrmrs 13d ago

Merged 88e86b3f Rebuild benchmarks as a clean single-root repository from oak/benchmarks main@009dead264ca; source tree verified by SHA-256 manifest 1cc497d666f1a1c8e27b040edfab9e7730dd48c3b47567e616943e471570a5c8.

mrmrs 2mo ago

Closed

closed without merging

Closed mrmrs-d7b59e Add reproducible end-to-end agent campaigns

mrmrs 12d ago

Closed mrmrs-f0d825 Add frozen local agent campaign plans and resumable durable journals. Validate exact manifests, safe names and paths, deterministic counterbalanced schedules, pinned configuration/harness/binaries, mandatory measurement locking, explicit real-run attestation, bounded admission and agent timeout, started/finished fsync checkpoints, artifact hashes and terminal-row identity. Never silently rerun interrupted episodes. Rebuild derived rows on no-op resume after a journal-to-rows crash. Fourteen contract tests pass; earlier full985 sandbox run had only18 known loopback permission errors and3 skips; combined unrestricted QA runs in integration worker. Carries reviewed foundation; report and subprocess modules integrate from sibling branches. No paid runs.

mrmrs 12d ago

Closed mrmrs-999547 Bound real-agent subprocess execution and capture; isolate per-trial HOME, sanitize Git plumbing, and mark incomplete usage honestly. Includes reviewed benchmark quality foundation.

mrmrs 12d ago

Closed mrmrs-1ed996 Add diagnostic agent campaign accounting, paired outcome and efficiency reports, and staged qualification plan

mrmrs 12d ago

Closed mrmrs-benchmark-gaps-20260910 Close benchmark correctness and saved-comparison gaps

mrmrs 12d ago

Closed mrmrs-473c2f Require exact output path identities and verify full patches against pristine trees; record oracle versions and fail closed on lost application proof

mrmrs 12d ago

Closed mrmrs-8b790b Close config and asset task false passes with shared trusted external oracles. Verify exact 600 config outputs, four binary contents and manifest identities, fixture validator preservation, and complete Git committed task trees. Run real-agent validation with isolated Python outside editable fixtures; version correctness semantics. Negative partial-commit and bypass cases plus Git/Oak workflow and mock-agent positives pass. Carries reviewed benchmark foundation; full sandbox suite930 has only18 known loopback permission errors and3 skips pending unrestricted integration.

mrmrs 12d ago

Closed mrmrs-9d1d51 Harden agent correctness observations: fail closed on failed or unsupported status, parse current Oak structured history and status, require new snapshots for mutating tasks, and detect mode/type/symlink changes. Version oracle semantics, retain null dirtiness, add negative tests and a source-based coverage audit. Targeted 23 tests and actual Oak 0.103.0 tiny commit/status probe pass; full sandbox run has socket permission errors pending unrestricted integration validation.

mrmrs 12d ago

Closed mrmrs-9df99c Reject incompatible measurement populations in statistics and scorecards; document methodology audit and acceptance criteria

mrmrs 12d ago

Closed mrmrs-dfa321 Add exact VCS preservation diagnostics and pinned upstream test review

mrmrs 12d ago

docs/adr/0005-scenario-operation-name-immutability.md 27 lines · 1.0 KB

ADR-0005: Scenario and operation names are immutable identity

Status: accepted
Date: 2026-06-10 (rule predates in docs; recorded as ADR)

Context

Historical charts and regression baselines key on profile + scenario + operation. If a name silently changes meaning (new fixture shape, different command, different semantics), every trend line through that point becomes a lie.

Decision

A scenario or operation name, once published in results, never changes meaning. Material changes to fixture shape, commands, or semantics require a new scenario/operation name (or a fixture/prompt/semantics version bump where the schema provides one: fixture_version, scenario_version, command_semantics_version). Old names may be retired but never reused.

Consequences

Refactors must be measurement-identical or introduce new names.
The command-semantics contract lives in config/command_semantics.json; changing a mapped command requires bumping its version, which all rows record.
Reviewers can reject renames-in-place by citing this ADR.

# ADR-0005: Scenario and operation names are immutable identity

- Status: accepted
- Date: 2026-06-10 (rule predates in docs; recorded as ADR)

## Context

Historical charts and regression baselines key on
`profile + scenario + operation`. If a name silently changes meaning (new
fixture shape, different command, different semantics), every trend line
through that point becomes a lie.

## Decision

A scenario or operation name, once published in results, never changes
meaning. Material changes to fixture shape, commands, or semantics require a
new scenario/operation name (or a fixture/prompt/semantics version bump where
the schema provides one: `fixture_version`, `scenario_version`,
`command_semantics_version`). Old names may be retired but never reused.

## Consequences

- Refactors must be measurement-identical or introduce new names.
- The command-semantics contract lives in `config/command_semantics.json`;
  changing a mapped command requires bumping its version, which all rows
  record.
- Reviewers can reject renames-in-place by citing this ADR.

1	`# ADR-0005: Scenario and operation names are immutable identity`
2
3	`- Status: accepted`
4	`- Date: 2026-06-10 (rule predates in docs; recorded as ADR)`
5
6	`## Context`
7
8	`Historical charts and regression baselines key on`
9	`profile + scenario + operation`. If a name silently changes meaning (new
10	`fixture shape, different command, different semantics), every trend line`
11	`through that point becomes a lie.`
12
13	`## Decision`
14
15	`A scenario or operation name, once published in results, never changes`
16	`meaning. Material changes to fixture shape, commands, or semantics require a`
17	`new scenario/operation name (or a fixture/prompt/semantics version bump where`
18	the schema provides one: `fixture_version`, `scenario_version`,
19	`command_semantics_version`). Old names may be retired but never reused.
20
21	`## Consequences`
22
23	`- Refactors must be measurement-identical or introduce new names.`
24	- The command-semantics contract lives in `config/command_semantics.json`;
25	`changing a mapped command requires bumping its version, which all rows`
26	`record.`
27	`- Reviewers can reject renames-in-place by citing this ADR.`