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

  1. Legacy code

    Undocumented, untested, years old.

  2. Surveyor extracts

    An architectural model, tech-choice MADRs, and behavioural scenarios.

  3. .assay specification

    A runnable behavioural contract you can review, edit, and version.

  4. Verified rewrite

    Same specs, two systems — both green.

Get in touch

Join the early access program

Stop guessing what your legacy system actually does. Get Surveyor and Assay before public release — we onboard you on your first legacy system and learn from your feedback.

Thanks — we'll get back to you soon.
We'll invite you to the Surveyor GitHub project so you can run it on your own codebase.
We'll only contact you about Surveyor early-access updates.

We use Brevo as our email platform. By submitting this form you agree that your data will be transferred to Brevo for processing per Brevo's privacy policy.