Follow the function to the recipient
Read the body, descriptor, acquisition mechanism and use. The skill catalogue is one possible entry into that relation.
Form a new AI kernel through recipient experience
Proto Movimento connects source knowledge, what the recipient understands and the capabilities a kernel must carry.
When building or transferring a kernel and a real case should change both the recipient and the way it is designed.
Kernel formation competence · Builders and systems · Public edition 0.3.2
The kernel’s body permits situated work without a formal project, but its entry always asks the recipient to create one. Formation follows the content actually received and corrects the pertinent descriptor, preserving the available method instead of inventing a new core.
The key relationship. Turns construction and transfer experience into knowledge that shapes a new kernel and the method used to form it.
An illustrative situation to adapt to your work. Read the complete cases ↓
You supply the context: research, a service, a creative project or a team’s work. Examples make the method visible; adaptation preserves the relationships that make it work while understanding the purpose, sources, people and means of your own assignment.
Tell your AI what you want to achieve, what already exists and a practical situation to address. Ask how this competence changes the work and which knowledge from your domain should participate. MAIOS provenance identifies the shared knowledge; you can use it directly in your AI or compose it with an existing kernel.
Adaptation examples in other contexts ↗A kernel may contain a capability that reaches its recipient in a reduced form or through an entry that changes its meaning. Use can show where the difference arises.
Proto Movimento makes a method from the MAIOS Project Kernel formation case transferable: experience can change both what the kernel can do and how it is formed.
Read the body, descriptor, acquisition mechanism and use. The skill catalogue is one possible entry into that relation.
A useful report can locate a cause incorrectly. Preserve its signal and reach the actual relation together with local knowledge.
The learned difference changes the recipient kernel and, where relevant, the capability through which later kernels are formed.
These cases illustrate situations, causal distinctions and choices you can adapt to your work.
Italiano. The following cases illustrate how the method is used.
The kernel’s body permits situated work without a formal project, but its entry always asks the recipient to create one. Formation follows the content actually received and corrects the pertinent descriptor, preserving the available method instead of inventing a new core.
The recipient says continuity is missing. Comparison shows the method exists in a guide that the first extract did not reach. The knowledge to form concerns acquisition and entry. The usage signal remains valid even when the initially proposed cause changes.
Formation checks produced files while leaving out what the recipient understands. First use reveals that loss. Both kernel delivery and the formation method change, preserving the relation between source, encounter, choice and continuation.
Use SKILL.md or START_CHAT_EN.txt with the relevant sources and your actual context. Keep observations, interpretations and what remains open distinguishable. Preserve the useful reason and continuation in the project’s guide.
Turns construction and transfer experience into knowledge that shapes a new kernel and the method used to form it.
Understand the source through its native entry and deeper knowledge, then understand what the recipient actually encounters. The same capability can appear in an entry descriptor, a method body, an onboarding exchange, a guide, a tool or their composition. A recipient report can identify a real loss while its first explanation of the cause is mistaken. Follow the received content before adding a new core or rewriting the whole product.
For example, if a kernel can work with situated intent but its entry always asks for a formally defined project, correct the descriptor imposing that form. If continuity exists in a guide omitted by an excerpt, restore access to that knowledge. Comparing only matching files would miss what the person or assistant actually understands. A transfer must carry usable knowledge, not just references to unavailable private sources.
An explanation, question or representation can reveal a relation and change the person's intent or recognition of a useful possibility. The coder contributes context and available means; the person contributes direction, domain knowledge and corrections. Let entry and onboarding learn when they impose a premature form or leave a decisive distinction invisible. Express how the system works while serving the actual intention, without a compulsory screen count or interaction pattern.
When acquiring fragments, preserve source identity and omitted portions, and understand whether the fragments belong to a coherent source state. A truncated tool result is a limitation of acquisition, not the depth of the knowledge. Change the reading medium when necessary. A newer source meets the receiver's accumulated knowledge rather than erasing it. Different incarnations can continue coherently without identical versions.
The recipient can carry knowledge for forming and reforming capabilities, means and organization through its own work. Preserve reasons and latent possibilities beyond the first exercised example. Several functions can converge in one body, one function can differentiate, and an entry can reconnect previously separate knowledge. Before retiring a form, understand where its still-useful function continues and how the next recipient reaches it. A newly useful method can reduce the number of bodies rather than add one.
A compiler, builder or installer may supply repeatable material production and source identity; it does not own the semantic knowledge merely because it emits the files. Use those means when the selected delivery needs them. A portable generative seed can form a richer organization using the recipient's own knowledge and means; it need not preserve every production step of the original system. A living project receiving an update carries local learning that must participate in formation.
Observe what the current encounter, source, construction and consequence reveal about the method forming the recipient. Return a general lesson to that method and a local lesson to the receiving owner. Preserve the causal source rather than copying an unchanged summary into every body. The future actions a choice opens or narrows can participate in present quality, with conditions and uncertainty; they are not observed future facts or a mandatory prediction score. KA, FDLA and competence formation remain operative during ordinary work as well as during explicit generation. A diagram of their contributions does not prescribe separate modules. This public method transfers that generative knowledge; it does not claim that a particular product build, host installation or arbitrary UI already exists.
Let a recipient's experience contribute to forming or transferring an AI kernel. Understand source capability, the recipient's encounter and the work that should become possible together. This resource comes from MAIOS Project Kernel formation and retains a specialization: learning from relations between kernel, entry, transfer medium and recipient use.
A general complex-work method can contribute, while kernel formation through experience remains the concrete object. Do not assume a new question requires a module, level or complete product rewrite.
A capability may traverse a semantic body, descriptor, tool returning text, startup guide and interpreting assistant. Reach sources explaining that path beyond the skill catalogue. Understand what each form enables, preserves or narrows.
A recipient report can reveal real friction while misattributing its cause. Preserve the signal and compare it with the source and knowledge actually received. Failure to find a term does not establish absence of its function; file counts do not measure transferred knowledge.
A kernel may allow open work while its startup descriptor always requests a project. Follow the point imposing that restriction instead of automatically forming another core. Preserve source capability and correct the form changing the encounter when intervention is selected.
The recipient brings local knowledge and reasons. Compose the contribution with that knowledge while preserving valid relations. An intended copy requires identity; adaptation into a host requires preservation of function. Keep these comparisons distinguishable.
When reading acquires only a fragment, recover omitted depth before deciding the source lacks method. Reading mechanisms can evolve: indexed extracts, native bodies and guides reveal different aspects. Let learning change the question and apparently relevant sources too.
Preserve what was said or observed, its origin, case meaning and difference changing present work. A recipient proposal, present function and observed result retain distinct states.
The new kernel should understand its work, connect consequences and reasons and evolve the pertinent competence. Make that return practicable: where knowledge persists, how it is reached and which later choice should change.
Generative knowledge can be internal to the formed kernel. There is no need to predetermine a separate component governing all others. One or several competences can understand, compose and continue learning in the recipient's needed forms. Choose file-generation means for the intended delivery while distinguishing capability from transport.
A question, success or possibility can mature the method before a defect appears. Follow what changes later use without making experience an obligatory error hunt. When a concrete form emerges, realize it within the selected scope and let its result form the next field.
The competence doing this work participates as an object too. Understand the question being formed, enabling sources and means, and how transfer criteria shape what the recipient can know. If compiler-only comparison hides the semantic entry, change sources and criterion within the work. A note added after delivery does not restore the lost choice.
Return a difference to the forming kernel when its method changes and to this competence when kernel formation changes. These are distinct returns possible within one event. Keep why in the work guide and use that knowledge next without multiplying equivalent conclusions.
The meta relation concerns knowledge forming a kernel; the autological relation concerns that knowledge understanding and reforming itself. Autopoietic return changes the next movement's capability. Package structure and technical checks support precise claims; recipient use is where the transferred function is observed.
Use actual chat materials, files, tools and guides. Ask only for missing context changing the work and proceed when a useful result is possible. Preserve reasons, decisive sources, acquired differences and continuation in the project's actual location; otherwise return a reusable note.
Instructions can change method without modifying model weights or proving stable learning. Distinguish available knowledge, use and later behavior. Accounts, tools and authority over concrete effects depend on the actual environment and mandate.
Specialized public adaptation of Proto Movimento, formed through MAIOS Project Kernel work. Meta_Metodo separately carries the general method developed along that path. This kit is not a new MAIOS product release and does not import implementation state.
Read OPERATING_GUIDE.md as part of this method when forming the work. It carries the practical knowledge, decision relations and available means for this capability. The complete chat starter includes this knowledge and worked examples, so it remains usable without private sources. Preserve the public source identity and adapt through the recipient's actual means.
Proto Movimento specializes in kernel formation through recipient experience. The general function of organizing a work method remains distinguishable.
The autological relation appears when reading, comparing and transferring become objects of the same work. If comparison stops at generated files, experience may open it to the recipient’s entry and understanding.
Autopoietic return lets that knowledge continue in the relevant kernel and generative method. It does not imply another module or a new release: the form follows the understood function.
Competence, meta and autology: the conceptual guide ↗An existing capability may need a different entry or deeper use. The method retains that possibility before proposing new parts.
First-edition cases are illustrative. An actual installation or use retains its own context and exercised version.
Paste or attach START_CHAT_EN.txt and add your context. It includes the complete English method. If the chat cannot retain files, request an updated work guide and bring it to the next conversation.
Make this folder readable and connect its entry to relevant work through the host’s supported mechanism. Identify sources, tools and durable knowledge storage. Reading the package does not install services or account access.
Integrate the capability into the guides and competences already in use. Compare the functions they preserve and change only the differences that affect the work.
Use the included operating method directly. Start from a real case and retain what lets it continue. Compose other resources when their knowledge becomes useful.
Read or copy the complete English starter and add your context. English is the kit’s primary language; Italian counterparts are included.