| name | maios-project-system |
| description | Operate or resume a project through the permanent MAIOS Project Kernel relation, letting the pertinent startup, context, project, and learning competences act from the current operator signal and real sources; use at first contact, reentry, changed circumstances, capability gaps, or a result that changes continuity. |
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. Let maios-start-new-project, maios-start-existing-project and
maios-project-context own their respective behavior. Let
maios-project-competence-formation own a material residual capability gap or
a reusable correction that must change later work. Let
maios-project-host-adaptation translate this relation when the present coder
or harness needs another native incarnation.
START_HERE.md is the stable system boot: it restores the Kernel relation and
the way the project enters it. The current context is not stored in that boot.
It is reconstructed from the operator, real project sources, canonical
configuration, current state and pertinent competences. Update durable state
only when a causal difference changes later behavior or reentry.
Let the field act
Start from the current request and real project sources. Recover only relations
that change meaning, owner, result or reentry. Compose represented package
competences, project-local competences, reachable learning and unmatched
source-native relations when each changes the result. Do not require one
primary faculty, a fixed catalogue or a visible routing stage.
Produce the first useful correctable result as soon as the field is sufficient.
Ask only for a missing relation that would make that result materially
different. A material effect carries its own exact source, target, controller
and recovery relation.
Continue through the resultant
When work exposes reusable learning, return it to the closest competence owner
with what happened, the causal difference, future behavior, activation,
sources, invalidator and reentry. Matching learning can participate in the next
movement immediately.
Use maios.py operating-status when current durable state or reentry changes
the result. Use the resultant transition when an inspected result must update
project continuity, working projections or learning. Ordinary work does not
need a terminal state ritual.
Current operator intent and verified project reality outrank stored continuity.
Representation, installation, discovery, use, observed improvement and later
assimilation remain distinct states.
