Work front
One current movement.
The selected object, purpose and boundary are visible before action begins.
Common operating metakernel
MMK — MetaMasterKernel.
Keeps a common direction across intent, work fronts, capabilities and results while applications, models and projects can change.
MMK is an operating form developed through three years of daily use and currently formalized as MMK v0.16 in the local TM9/Codex incarnation. It is not an installable repository or a central authority: every project, runtime and surface retains its own sources and gate.
- Form
- Common metakernel
- Current incarnation
- MMK v0.16 · TM9/Codex
- Role
- Understand and orient
- Boundary
- No background or automatic authority
Reason
Coordination must survive the passage between sessions and instruments.
A working field can involve several projects, instances, models, tools and sources. MMK gives the active movement a readable owner, boundary and return state.
The useful unit is one selected front: the work that is active now, the instance responsible for it, the faculties it requires and the state that must return to the project.
Operating relation
Five objects remain connected.
This sequence describes the coordination grammar. It does not grant a model, instance or tool authority beyond the selected work.
- 01Source and intent
The operator signal and verified context identify the movement.
- 02Active front
The current work is bounded before adjacent surfaces enter.
- 03Responsible instance
One owner acts for the front with explicit authority.
- 04Selected faculties
Skills, competences and tools serve the work that requires them.
- 05Result and re-entry
The useful result, evidence and next state return to the project.
Operating relation
MMK, MAIOS and RepoKernel perform different functions.
In the current composition, MMK understands and orients the movement; MAIOS governs, operates and learns in the user’s system; RepoKernel compiles a bounded portable form for an individual project. This is a relation between functions, not repository ownership or containment.
Responsibility
One explicit owner.
Coordination does not silently transfer authority between instances or projects.
Faculties
Capabilities enter by function.
Their availability does not imply activation; the selected front determines their role.
Continuity
State returns to its source.
Result, evidence, boundary and next movement remain readable after the handoff.
Current state and boundary
Verified local incarnation; no background authority.
MMK has a locally verified operating grammar and contracts. Other hosts require their own adapters and evidence; the local incarnation does not establish universal availability.
Boundary. MMK does not run in the background, observe every system, impersonate the operator or gain material authority by proximity. A selected action still requires a separate owner, evidence, authorization, validation and receipt.