Claude Opus 4.8 introduces dynamic workflows for
verifiable tasks
Make your legacy software
verifiable.
Surveyor extracts a behavioural specification from your undocumented
legacy code. Assay runs that same specification against both the
legacy system and its rewrite — so nothing breaks in translation.
Two tools, one promise
Surveyor
Scans a legacy codebase, drives an LLM through architectural
discovery, and emits a behavioural specification, schemas, and
binding skeletons. Read-only on the source. Every artefact ships
as a draft for human review before it becomes canonical.
Assay
Runs the behavioural specification against any target. Same
scenarios, two systems, two passing test runs. Specs are the
contract; only the binding changes between the legacy and the
rewrite.
How it works
-
Legacy code
Undocumented, untested, years old.
-
Surveyor extracts
An architectural model, tech-choice MADRs, and behavioural scenarios.
-
.assay specification
A runnable behavioural contract you can review, edit, and version.
-
Verified rewrite
Same specs, two systems — both green.