| name | maios-project-kernel-source |
| description | Build, inspect, validate, or evolve the manual MAIOS Project Kernel package from its sole source repository while preserving open faculty composition, deterministic installation, proof levels, contamination boundaries, and compact reentry. |
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:
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 a later independent comparison, not a source or fixture for manual 2.0.0.
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, or old adapter. A relation
outside the registry remains admissible with source, reason, expected delta,
invalidator, and reentry condition.
Generate package/ only through release/PROJECTION.json and the builder; do
not hand-author behavior in the payload. Use the package-owned installer for
preview, apply, verify, and recovery. It
must refuse ambiguous targets, global writes, changed plans, and divergent
content. Validate the exact result with the source tests and disposable target
fixtures before changing version or release state.
