You provide
The working beta from MAES Factory, agreed requirements and project constraints: existing tools, data, access and intended uses.
MAES ARCHITECTURE
See the whole system. Plan the right build order.
MAES Architecture works out how to turn the beta into a robust solution. It assesses the entire project: connections between features, data, dependencies and risks. It prepares a step-by-step construction plan for MAES Build.
MAES software supports work carried out by people, AI agents or both. Your business defines the roles, permissions and approvals required.
In development
Tell us what you needWhat the software does
It examines what depends on what, technical risks, security and data protection, including GDPR considerations. It divides the build into work packages, called “slices”: defined parts to build and verify separately. It proposes their sequence.
You approve
You review the construction choices, priorities, risks and planned checks before authorising implementation.
You receive
A plan for MAES Build: scoped slices, their dependencies, sequence and acceptance conditions. The analyses and their reasoning are recorded.
MAKE IT CONCRETE
A slice: a defined piece of work to build and verify.
A fictional example showing what the software does. This is not a software interface.
MAES Architecture Example record
- A clear scope
- For example, saving an exercise result. The slice defines the work and the conditions it must meet to be considered verified.
- A reasoned sequence
- The user and exercise must be identifiable before the result can be saved. Progress tracking then relies on those saved results.
- Checks planned in advance
- Define permitted access, the data needed, expected tests and how failures will be handled. MAES Build receives a coherent plan.
Each action records who carried it out, whether a person or an AI agent, along with its date, context, rationale and supporting evidence.
WORKING WITH OTHER MAES SOFTWARE
The project continues.
MAES Build implements the slices according to the authorised plan. If a new constraint requires a change, the analysis and plan are updated with the reasons recorded.