Before anything is tested, it needs somewhere real to run. The Environment provisioner builds staging as code, straight from the architecture, and the Test data agent fills it with realistic, anonymized data and test accounts. Everything after this runs against a working system, without ever touching real customer data.
The environment registry is shared with Operate, so production and staging are described the same way.
Infrastructure first, from the architecture Plan wrote. Then the data and accounts the test agents need to sign in and work.
Each one has a codename, one job and a record of everything it did. These views show a sample project.
It reads the architecture written in Plan and turns it into infrastructure as code: networks, services, databases and the rest, planned, reviewed and applied. Every environment it creates goes into a registry, so you always know what is running where, and which build it carries.
It profiles the data model and seeds staging with representative records and the test accounts the test agents need to sign in. Names, emails and anything personal are generated or masked, and nothing is copied from production. It is the agent most teams forget, and the one that keeps testing from stalling at the login screen.
Verify only starts on an environment a person has declared ready: live, migrated, smoke-tested and seeded.
The build on staging knows which requirements it closes, so Verify knows exactly what to prove.
We open Orlian on a live project and walk you through the Stage wing: what goes in, what the agents produce, and where a person signs. No slides.
