maios-project-kernel-sourcelisted

# MAIOS Project Kernel Source Read `CURRENT_STATE.md` and the selected architecture before changing source or build files. Treat another dirty worktree as separately owned material, not as an input or cleanup target for the current source. Keep meaning, product composition and delivery connected. Current native owners reach the distribution through `release/PROJECTION.json`; the ordinary builder composes them with current contracts, templates, adapters and runtime. No old generated selection silently decides what a current source change means. For receiving feedback, understand the instructions and data the host actually consumed. Return a change to the owner that should act differently, then follow the affected entries, consumers, state and proof until they agree on the new resultant. Bind proof to the identity exercised; independent-looking checks that share one wrong assumption do not supply independent evidence. A kernel correction can cross semantic knowledge, logical elements, state, registry descriptors, tools and host entries. Follow the contributing function through those consumers; the skill catalogue alone does not cover it. A general useful-result method, for example, also needs a general result descriptor in the field exposed by compose. Preserve stable identifiers and intentional recipient translations. Compare every selected delivered method with its current native owner so a self-consistent retained plan cannot silently keep superseded bodies. The install