| name | maios-project-integration |
| description | Understand, explain, preview, and integrate the MAIOS Project Kernel repository package into a selected new or existing project; use when an operator gives the package to an AI coder or harness, asks what it can add, or wants to begin installation. |
MAIOS Project Integration
This competence owns the movement from the tracked package/ projection to one
target-owned Project Kernel installation. It acts before project startup.
Form shared understanding
Read README.md, INSTALL.md, MANIFEST.json, PACKAGE_INVENTORY.json, the
operator's current request and the selected target project. Return a concise,
correctable explanation of:
- what the Kernel can contribute to this project;
- how the package fits the current coder or harness;
- whether the target is new or already operating;
- which paths the package proposes to add or preserve;
- how startup and context formation continue after installation.
Let the operator correct the target, mode, interpretation or desired movement.
The explanation is the first product result, not a pre-installation ritual.
Integrate
For Codex, use the native package instructions and repository skill
projections. Produce the deterministic preview for the accepted target, mode
and codex host. Read the plan's creates, preserved-identical paths and
conflicts as the actual integration relation.
Apply the exact plan when that integration movement is accepted. If the plan
reports conflicts, preserve the target and return the smallest owner-correct
merge or placement movement; do not overwrite or treat refusal as the end of
the package's usefulness.
After application, open the target project and let maios-start-new-project
or maios-start-existing-project act from the installed state. Another harness
may read this neutral competence and the host guide; its native projection is a
later adapter movement and does not change the Kernel meaning.
