← ClaudeAtlas

maios-project-kernel-sourcelisted

Build, inspect, validate, or evolve the autonomous self-configuring MAIOS Project Kernel package from its sole source repository while preserving open faculty composition, deterministic installation, proof levels, contamination boundaries, and compact reentry.
GrazianoGuiducci/maios-project-kernel · ★ 0 · AI & Automation · score 70
Install: claude install-skill GrazianoGuiducci/maios-project-kernel
# 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 one vertical connected: ```text living source -> generated package inventory -> install plan -> target receipt -> host discovery -> behavioral use -> maintained reentry ``` Never claim a later state from an earlier proof. Treat the Form-generated route as the preconfigured projection of the same Kernel family, not as the source or fixture of the autonomous package. The autonomous entry reconstructs and validates context with the operator; the Form entry starts from accepted configuration and refines it. Differences after entry must remain situated configuration, not divergent Kernel behavior. A compact, collision with an existing public artifact, or an assistant's publication plan cannot select a new product version. Preserve useful source corrections in the current living line and keep version, tag and Release claims unselected until the operator chooses that product identity. A rewritten label without changed kernel behavior is not a new kernel. The source system exposes one semantic host faculty, an open causal faculty field, a situated configuration engine, and reciprocal competence cultivation. Preserve result-changing functions and their proof contracts; do not copy every workspace skill, private topology, temporal state, o