maios-project-competence-formation

name	maios-project-competence-formation
description	Form or evolve the smallest project-local competence when situated work exposes a real capability gap or reusable causal correction; use after available competences have been composed and the remaining relation changes the result or later reentry.

MAIOS Project Competence Formation

This is the portable competence-formation faculty of MAIOS Project Kernel. It transfers the capacity to form and cultivate competences; it does not contain the private Meta_Skill source or the private whole-kernel generator.

Keep the concrete work active. Read the current project state, the exact sources involved and .maios/kernel/COMPETENCE_CULTIVATION_PROTOCOL.md only to the depth that changes the present result.

Form the missing competence

1. Compose the competences and learning relations already reachable in the present circumstance.
2. If a material gap remains, identify the smallest truthful owner and the behavior that would change the result. Do not create a skill merely because a topic is unfamiliar or absent from a catalogue.
3. Give the competence the smallest useful body supported by the work: a method, function, reference, protocol, skill, or coordinating relation. A Codex skill uses a focused SKILL.md; add references or scripts only when they materially improve repeated use.
4. Bind the body to its need, sources, activation relations, expected delta, invalidator and reentry condition. Preserve the causal learning in the terminal resultant so it can participate in the next matching movement.
5. When durable project routing needs an explicit owner, connect the knowledge entry to .maios/competences/INDEX.json. This publication-like index change is separate from the immediate causal learning and is never required merely to let that learning improve the next movement.

Cultivate through use

Let actual work correct the closest competence in the same movement. Change its knowledge body when the correction is reusable, keep the previous causal relation recoverable when it is superseded, and let later non-identical use show whether the change is assimilated, needs revision, or has met its invalidator.

Stop adding meta-levels when another pass changes no material relation in comprehension, execution, proof, recovery, or reentry. A project-local file change follows the current target and owner relation; external, public, credentialed, destructive, or runtime effects retain their exact boundary.