Mechanical Orchard

Business rules extracted by AWS Transform flow straight into Imogen's system overview and are mapped to the code that implements them, and a similar link with Google's Mainframe Assessment Tool feeds wave planning. During phased cutover, the modern batch framework reaches VSAM, DB2 and IMS data through standard data access APIs. Both platform links bring analysis into Imogen rather than acting elsewhere, and no repository, ticketing, chat or cloud console actions by the agents are named.

Sourcemechanical-orchard.com/insights/imogen-now-integrated-with-aws-transformread 2026-11-08

Rewrite runs as an autonomous pipeline drawn as a typed graph in which each node is an AI agent and each decision point is a gate, with a single batch job taking about three hours end to end. Parallel teams of agents work on code generation and verification at once, lanes fan out and back in, a monitor watches each worker's liveness, and the work advances slice by slice within the waves the migration plan sets.

Sourcemechanical-orchard.com/insights/the-software-dark-factory-modernizing-legacy-systems-with-no-humans-in-the-loopread 2026-11-08

A deterministic parser reads the legacy source directly and builds the execution flows, the data sources each job reads and writes, and the dependencies across the estate, a step that takes minutes and yields insight within hours. The result persists in the interface as a system overview, a dependency graph and a migration plan that updates itself, which people can query in plain language, and tests map back to the business rules extracted from the code.

Sourcemechanical-orchard.com/research/modernizing-mainframes-a-behavior-based-approach-to-verificationread 2026-11-08

People sit at two points by design: they shape the line before it runs and accept what it produces afterward, with every gate enforcing standards the customer's team set and coverage reports to review before anything ships. Engineers judge rule by rule which legacy behavior should carry forward, a cutover checklist sets the questions for whoever authorizes the switch, user acceptance testing included, and old and new systems run side by side during cutover. The company also says the pipeline removes the need for human code review.

Sourcemechanical-orchard.com/insights/the-cutover-checklistread 2026-11-08

Mechanical Orchard holds ISO/IEC 27001:2022 certification, audited by Schellman with a scope that includes the Imogen platform and its development and operational environments, and states a SOC 2 Type II attestation and a GDPR program, with the certificate and its statement of applicability held on a trust portal. Projects have run in an air gapped environment and the pipeline runs in a sandbox, but single sign on, roles, encryption and any use of customer code for model training go undescribed.

Sourcemechanical-orchard.com/insights/mechanical-orchard-iso-iec-certificationread 2026-11-08

The interface tracks progress by wave as completed, in flight or blocked, keeps a migration plan that updates itself and shows failing slices in a red and green view. After a run the full history remains, every decision, rejection and retry, and the government page promises an auditable trail at every step. Divergences between old and new behavior are logged and traced to a root cause, so program managers can share measured progress straight from the interface.

Sourcemechanical-orchard.com/insights/illuminating-the-dark-factoryread 2026-11-08

Pipeline state is checkpointed after every completed station, so a long autonomous run resumes from its last finished step rather than starting over. Workers share no memory with each other, and nothing describes agents learning from corrections or keeping preferences from one project to the next; the delivery data Mechanical Orchard draws from past engagements feeds its own estimates rather than the agents.

Sourcemechanical-orchard.com/insights/the-software-dark-factory-modernizing-legacy-systems-with-no-humans-in-the-loopread 2026-11-08

On AWS Marketplace, Imogen is offered as software as a service deployed on AWS and also as an on premises deployment with orchestration, and in a manufacturer's warranty project it ran inside the customer's own environment. One automotive project ran in a locked down, air gapped environment, while proofs of concept run in a cloud instance Mechanical Orchard controls. No hosting regions are named, and modernized applications land on AWS, Google Cloud or another cloud the customer picks.

Sourceaws.amazon.com/marketplace/pp/prodview-tcry42kis5gxqread 2026-11-08

Byte accurate COBOL to Java codecs, local shims that simulate mainframe services, a characterization testing framework, a modern batch framework with a data access layer, mainframe specific libraries and tuned agent skills all ship inside the pipeline. They are the platform's own machinery, tuned per program by Mechanical Orchard, and the customer does not pick from a catalog of agents or templates, though integrators can choose to use Analyze, Rewrite and Orchestrate together or apart.

Sourcemechanical-orchard.com/research/mainframe-modernization-is-a-verification-problemread 2026-11-08

Programs are configured and steered in the Imogen user interface, where teams change the migration plan in plain language and query the parsed system, and once people have designed the line the pipeline runs on its own until it hands back results. No API, command line, schedule or event that starts a run appears on Mechanical Orchard's pages, and with no public documentation, nothing beyond the interface shows how a run begins.

Sourcemechanical-orchard.com/media/imogen-demo-for-program-managersread 2026-11-08

Mechanical Orchard says Imogen combines several large language models across its pipeline, checks each candidate with committee models different from the one that built it, and turns to cheaper and open models where they are good enough, treating the agents themselves as interchangeable. No model or provider is named anywhere on its pages, and customers get no model picker, no routing setting and no way to bring their own model or keys.

Sourcemechanical-orchard.com/media/imogen-demo-for-modernization-engineersread 2026-11-08

No public documentation, console sign in, API, SDK, command line tool or MCP server could be found for Imogen. A characterization SDK built as a JUnit framework appears in Mechanical Orchard's research writing as internal tooling, and its GitHub organization holds mostly forks of other projects, with no Imogen client or library. Partners reach the platform through its interface and commercial agreements rather than through code.

Sourcemechanical-orchard.com/research/mainframe-modernization-is-a-verification-problemread 2026-11-08

Verification sits at the center of Imogen. Characterization tests, some built deterministically to exercise every reachable code path and some generated by models, pin the new code to the legacy behavior, and a second layer replays months of captured production data and compares outputs byte for byte. Backtesting and a diamond pattern of checks run before a slice is accepted, and the customer keeps the test suite drawn from real production behavior.

Sourcemechanical-orchard.com/research/modernizing-mainframes-a-behavior-based-approach-to-verificationread 2026-11-08

Imogen works on source code, data captures and batch jobs, and nothing on Mechanical Orchard's pages describes an agent that drives a browser, a desktop or a terminal screen through its interface. Screens appear only as one of the legacy workload types it rewrites, alongside batch and transactions, so the agents read and write code and data rather than operating any user interface.

Sourcemechanical-orchard.com/platformread 2026-11-08