You provide
MAES Architecture’s slices: what to build, in which order, with which dependencies, permissions and acceptance conditions.
MAES BUILD
MAES Build implements the solution from MAES Architecture’s plan. It builds in work packages, called “slices”: each part is implemented, tested and corrected, using people, AI agents or both. Completed work must have the checks and evidence needed for approval.
Your business defines the roles, permissions and approvals required.
Used in our internal work · In development
Tell us what you needMAES Architecture’s slices: what to build, in which order, with which dependencies, permissions and acceptance conditions.
It carries out the planned work, runs tests, addresses failures and arranges further verification. Builds, versions, actions and evidence are accounted for as work progresses.
Implementation, review and authorisation have distinct roles. Authorised people examine the evidence and any outstanding issues before release and closeout.
Verified work and its history: contributors, dates, versions, tests, fixes, approvals and outcomes. A cycle summary explains what happened and what still needs follow-up.
MAKE IT CONCRETE
A fictional example showing what the software does. This is not a software interface.
MAES Build Example record
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
Closeout preserves the outcomes and any outstanding issues. Kallistos Pilot provides the overall view; MAES Decide can use the learning to prepare the next improvements.