You provide
The project defined with MAES Decide: users, features, priorities and constraints.
MAES FACTORY
Build the beta. Try it out and refine it.
MAES Factory builds a first working version of the agreed app or feature: the beta. Screens, features and user journeys are built, tried out and refined to establish how the solution should work.
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 builds the beta, explores alternatives and improves features through testing. People and AI agents can contribute within their authorised roles.
You approve
You check that the journeys and features meet the need. This stage prioritises experimentation; MAES Build applies stricter construction and validation requirements.
You receive
A working beta and its record: versions, trials, selected approaches, discarded alternatives and known limitations. The work stays accounted for to inform the next stage.
MAKE IT CONCRETE
Try out the learning experience.
A fictional example showing what the software does. This is not a software interface.
MAES Factory Example record
- What is built
- Screens for choosing a lesson, answering an exercise and viewing the result.
- What is tried out
- The screen sequence, instructions and feedback after an answer. Trials guide changes to the beta.
- What goes to MAES Architecture
- The agreed behaviour, versions and limitations. MAES Architecture can then assess the solution as a whole before rigorous implementation.
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 Architecture takes the beta and assesses the whole project: feature dependencies, risks and the build sequence to propose to MAES Build.