Capture real work
Good evaluation tasks begin with work that actually occurs. Merion captures aWorkEpisode: a versioned record connecting a request, starting state, execution context, trajectory evidence, and human-reviewed outcome.
Before work begins
Run:.merion, .git, dependency trees, and common build outputs. It does not follow symlinks or copy source-file contents into the manifest.
During the work
Continue through Codex, OpenCode, a manual process, or another harness. Preserve evidence that helps explain the outcome:- tool calls and external actions;
- corrections and retries;
- human interventions;
- relevant artifacts and changed state;
- runtime, cost, and latency when available.
Close with human outcome evidence
Run:- whether the result was accepted, corrected, rejected, or abandoned;
- observable success criteria;
- unacceptable outcomes;
- the corrections that were required;
- whether the episode represents normal work;
- recurrence and economic value.
Do not promote a single anecdote
After review, runmerion next. Merion asks for related examples before suggesting evaluation formation. The current workflow requires at least three reviewed episodes before opening the task-formation path.
Continue with forming an evaluation.