Reconstructs the field
Reads requests, files, sources, state and relations without reducing the project to the first available description.
Self-configuring package 2.0.0
MAIOS Project Kernel
Bring an operating Kernel into the folder: one that understands the project, composes pertinent competences and preserves the point from which work can continue. It does not impose a final form; it grows with the work, its results and the possibilities that emerge.
- 01Context
- 02Composition
- 03Continuity
An operating brain for the project
Its logics work together when the moment calls for them.
The Kernel is not a pre-packaged answer. It is the system that lets the project understand, act, read itself back and evolve.
Composes competences
Selects and combines skills, competences and meta-competences when they can materially change the result.
Produces a first result
Turns understanding into a useful, concrete and correctable movement instead of stopping at an abstract plan.
Preserves state and continuity
Keeps decisions, open elements, provenance and a re-entry point across sessions and stages of work.
Governs effects
Separates what it can understand and prepare from what requires authorization at the moment of real action.
Cultivates evolution
Makes useful corrections reusable and can welcome new hosts, tools, competences and operating forms.
What it contains
A distribution, an installed project and a core that remains legible.
Entry and manifest
The distribution declares version, inventory, files, installation modes and boundaries before entering the project.
Semantic Kernel
Principles, state and logic that keep context, possibilities, sources and result inside the same movement.
Competences and meta-skills
Operating faculties for understanding, building, verifying, coordinating and creating new competences when needed.
Project state
Brief, configuration, decisions, open questions, results and re-entry points that the coder can evolve with the work.
Host adapters
Local entries for Codex, Claude Code, OpenCode, Hermes, DeepSeek Harness and generic systems, without hidden global writes.
Verification and recovery
A reviewable plan, explicit conflicts, receipts, verification and conservative uninstall protect existing files and work.
Inside the folder. After installation you will find project entries such as AGENTS.md, START_HERE.md and HOSTS.md; the .maios core holds Kernel, runtime, state and competences. This structure is an evolutionary foundation, not the limit of future combinations.
With your coder
You choose the project. The coder handles the technical work.
You do not need to check Python, remember commands or interpret the inventory. Put the package in a working folder and ask the coder to prepare a readable plan before applying it.
01 · New project
Begin in a new folder
The coder selects an empty destination, checks the environment, shows what will be created and installs the Kernel in the new project.
- Download the package into a working folder.
- Open that folder with the coder.
- Send the message below.
02 · Existing project
Bring the Kernel into existing work
The coder inventories files first, preserves identical ones and stops on conflicts. Nothing should silently overwrite the project.
- Identify the real project folder.
- Ask to see the plan and conflicts.
- Confirm only the movement you recognize.
Message for the coder
This folder contains the MAIOS Project Kernel 2.0.0 distribution. Read INSTALL.md and the manifest, check the technical requirements yourself and ask me which project I want to prepare. Show me in plain language the target folder, what will be created or preserved and any conflicts. Proceed only after my confirmation; then open the installed project, read START_HERE.md and give me the first useful, correctable result.
The package is self-configuring through the work with the coder, but it does not execute by itself: the target folder, plan and every effect remain explicit.
Version 2.0.0 on GitHub
Get the package from the official repository.
The public repository contains the source, architecture, technical guide and project history. The Release contains the installable package.
The Release includes the installable ZIP and SHA256SUMS. If the project is useful to you, star the original repository so more people can find it.