MMK
Understands the whole and orients movement.
It preserves the source, lets a resultant emerge, calls the relevant competence and projects meaning onto the selected surface.
Orientation kernel · continuity across projects · replaceable models
MMKMetaMasterKernel
From intent to a useful possibility. From possibility to a project that can keep evolving.
MMK is the kernel through which the system interprets the operator's intent, observes the field, connects the necessary competences and maintains continuity across projects, applications and models. It lets the work change tools without losing meaning, state or direction.
01 · Continuity
Models change. The work keeps its context and direction.
MMK keeps one source of orientation while applications, models and tools change. Each project receives the context and competence it needs to continue.
- 01Intent and context
Goals, constraints, corrections and decisions remain available as work moves across different conversations and applications.
- 02Models and tools
New models and applications add capabilities; the kernel preserves the work's meaning, state and direction.
- 03Readable continuity
Useful knowledge becomes a flow and boundary that the system can reread, verify and correct.
- 04Projection into projects
The portable part enters the Project Kernels generated by RepoKernel and adapts to the surface that will use it.
MMK does not replace the sources that own the facts. It composes them.
It is not the model that represents it. The model is a replaceable faculty.
It does not lose a possibility merely because its realisation is not yet authorised.
02 · Architecture
MMK orients. MAIOS operates. The system learns from what is verified.
One interaction source keeps the whole understandable; sources, repositories and services retain their own authority. Real actions remain bound to ownership, evidence and recovery.
- 01Operatorintent and context
- 02MMKunderstands and orients
- 03MAIOSgoverns and coordinates
- 04Surfacesmodels, skills, tools and apps
- 05Resultverified action or proposal
- 06Continuityknowledge and a new zero point
MAIOS
Turns orientation into governed work.
It connects state, capabilities, models, tools, permissions, validation and continuity in the user's system.
Surfaces
Make the kernel present where it is needed.
Codex, Claude, OpenCode, MiniAGI, THIA or a dedicated application can represent it with their own capabilities and boundaries.
03 · Source movement
From source to resultant, without losing the possible.
The first pass understands and orients. Material review enters only when a real change is selected. The map lets both routes be read without performing actions.
Route
Step 1 / 6
Linear equivalent of the movement
- Exact source
Preserve the operator's input before adding specialist context.
- First reading
Observe the initial semantic movement without presenting it as factual authority.
- Useful possibility
Let a direction emerge before feasibility and ownership are evaluated.
- Direct competence
Bind the smallest relevant faculty and remove unnecessary routing.
- Surface projection
Translate the invariant into the form required by the selected surface.
- Optional material review
Only for a selected change: establish owner, facts, authority, consequences, validation and recovery.
- New starting point
Return the useful delta; write a change record only after a real, authorised and validated mutation.
04 · Distribution
The kernel enters projects without cloning the system that generated it.
RepoKernel turns authorised intent and sources into a reviewable Project Kernel. The portable operating part of MMK is projected into the project; local identities, credentials, private chronology and node state remain outside.
- 01MMKkernel in use
- 02Portable invariantcontinuity, authority and learning
- 03RepoKernelreviewable compilation and staging
- 04Project Kernelstate, sources, skills, rules and receipts
- 05Projectincarnation in its own environment
Already generated
Project Operating Faculty
RepoKernel already inserts the rules that let a future agent understand where it is, which state is current, who may receive a change and how to avoid repeating effects from stale memory.
- Reentry from current state, sources and reliable chronology.
- Separation of acting agent, state source, active surface and write owner.
- Classification of local, remote, public and external actions with validation and recovery.
- Transformation of repeated work into reviewable routines and competences.
05 · Applications
One logic, many surfaces.
The kernel remains recognisable while the way it is represented changes. Every surface declares its own capabilities, limits and authority.
Daily work across the system
MMK keeps context, direction, competences and possibilities together while work crosses conversations, files, repositories and decisions.
New projects and RepoKernel
The portable capability becomes a Project Kernel that the project can own, inspect, correct and evolve.
MAIOS Setup and consulting
Orientation translates objectives, activities, authorised sources and responsibilities into an initial system: project, assistant, competences, memory and data rules.
Replaceable applications and models
Codex, Claude, OpenCode, MiniAGI, THIA and future dedicated applications can offer different faculties without becoming the kernel's identity.
Local operation and MAIOS services
Private activity can remain in the local system; external services and models enter through explicit connections when the task requires them.
Operating relation
MMK understands and orients.
MAIOS governs, operates and learns.
MMK is the interaction and coordination kernel. MAIOS is the operating body that connects state, capabilities, tools, validation and continuity in the user's system.
This page presents MMK as a project and makes its operation visible. Private implementations remain separate; only the invariant required for project continuity and reviewable evolution is transferred.
For technical review, a setup or consulting: info@d-nd.com