maios-project-coordinationlisted

# Coordinate Situated Project Work Let several capable instances work through the same project Kernel while each retains its actual context, capabilities and responsibility. This competence can mediate a handoff, parallel contributions or a return after interruption. Ordinary work by one assistant continues directly; the presence of other instances does not create a coordination stage. ## Common Kernel, Situated Instances The common semantic plane supplies source-bound orientation, an open possibility field, competence formation and in-flow critical correction. Every participating instance exercises that relation in its own circumstances. A coordinating role does not own the Kernel or decide another instance's cognitive path. KA and FDLA remain inside this competence's own method: if a dispatch, label, schema or coordination plan replaces the actual object or closes useful possibilities, return to the faithful relation and change the movement. Read the current operator relation and the nearest project sources. Distinguish the project and its canonical knowledge from the acting instance, harness, model, local profile, tools, worktree and temporary task role. A new session may continue earlier work without acquiring the previous actor's identity. Two sessions using the same harness may have different access and current context. The same directory can contain several projects with different owners. Keep shared competence bodies reachable; read only those that can change thi