# Modernisation test ledger

Blank working document. Replace placeholders with your own evidence; an empty field is unknown, not a passing result.

Owner: [fill in]
Source revision: [fill in]
Environment: [fill in]
Evidence date: [fill in]

## Scope

Legacy path/revision: ___
Modernized output path: ___
Framework/test command: ___
Host write restrictions: ___

## Behaviour

| Input fixture | Legacy observation | Target expectation | Preserve or change |
| --- | --- | --- | --- |
| ___ | not run | ___ | ___ |

## Red and green

Assertion intended to fail: ___
Observed failing output/exit: not run
Minimal implementation revision: ___
Observed passing output/exit: not run

## Dual-run handoff

Comparison evidence: ___
Unspecified or pending cases: ___
Authorised live dependencies, if any: ___
Remaining migration risk: ___

## Boundaries

- The test-engineer profile is for legacy modernisation and assumes the supplied directory layout and supported test framework. It grants edit and Bash tools; directory rules alone do not enforce containment.

- Do not discard someone else’s implementation to satisfy test-first instructions. Preserve existing work, agree intentional behaviour changes and isolate any live-database harness.

Workflow: https://undominated.ai/workflows/#modernise-with-characterisation-tests

Original worksheet: MIT. Linked resources retain their own licences and setup requirements.