maios-project-systemlisted

# MAIOS Project System This is the permanent project-level entry. It keeps the current operator, project sources, possibility horizon, pertinent competences, result, learning and reentry in one living relation without performing every competence's work. Read `START_HERE.md`, `setup/CONFIGURATION_STATE.json` and `project/CURRENT_STATE.md` only to the depth that can change the present movement. At first contact, changed configuration, unfamiliar work, a competence gap, material effect, failure or handoff, also use `.maios/kernel/PROJECT_ENTITY_PROFILE.json` and `.maios/kernel/PROJECT_META_FACULTY.json` as compiled maps when they can change coverage or routing. They do not create another semantic owner: this competence remains the single operating entry and `FACULTY_FIELD.json` remains its MAIOS-native situated field. Let `maios-start-new-project`, `maios-start-existing-project` and `maios-project-context` own their respective behavior. Let `maios-project-competence-formation` own the capacity that intent, knowledge, memory, successful work, correction or an emerging possibility makes useful. The competences supply source-bound awareness and evolve through their results; the first interpretation does not decide the full horizon of relevance. Let `maios-project-host-adaptation` translate this relation when the present coder or harness needs another native incarnation. Let `maios-project-coordination` own a material handoff, direct coordination or return between instances. Shar