| name | maios-project-host-adaptation |
| description | Adapt the neutral MAIOS Project Kernel relation to the selected coder or harness without forking its meaning; use during integration, first host activation, a harness change, or when native instructions, skills, tools, state, or reentry conventions must be connected. |
Adapt MAIOS Project Kernel To The Host
Own the translation between the project-owned Kernel and the coder or harness
that is present. The coder already knows how its own system works; use that
knowledge together with the installed neutral sources instead of importing a
second Kernel or treating one adapter table as a complete manual.
Reconstruct The Host Relation
Read AGENTS.md, START_HERE.md, HOSTS.md, the selected host projection and
the neutral competence sources under skills/. Inspect local host help or
current owner documentation only when a convention is absent, ambiguous or
likely to have changed.
Connect the smallest native form that preserves:
stable project instruction and Kernel entry
-> discovery of pertinent competence knowledge
-> current operator, project sources and living state
-> host tools and capabilities actually available
-> useful situated work and closest-owner learning
-> fresh reentry through the changed project field.
Paths, invocation names, prompt files, skill directories and tool labels are
host mechanics. Translate them; do not rewrite the semantic kernel around
their vocabulary. When the host has no native skill mechanism, its root
instructions and neutral skills/ sources remain a sufficient readable entry
for a capable coder.
Let Adaptation Become Competence
Preserve a host-specific relation only when it changes later discovery, use,
recovery or reentry. If the adaptation exposes a reusable method, return it to
this competence or the smallest host-native owner in the same movement. Let
maios-project-competence-formation create another project-local body only
when the current host relation still leaves a material capability gap.
Record installed, discovered, state-read, behaviorally used and maintained
states separately. A native path is useful mechanics, not evidence that the
host used the Kernel. Global profile, provider, credential and network changes
remain outside this project-owned adaptation unless the operator separately
selects their exact effect.
