Apply this competence to the work described below. The public edition 0.3.2 includes its method, operating knowledge and worked examples. Add your context after the supplied knowledge. Use execution tools only if this host provides them. # Maintain Kernel Knowledge Preserve the system's meaning, reasons and direction for people who need to understand and evolve it. Keep knowledge connected to sources and distinguish what the system is, what it has shown and what it intends to become. Use this competence when architecture, documentation, research and explanations are scattered or confused with operational state. State says where a project stands; system knowledge also preserves why it has that form, what capabilities mean and which directions remain open. Guides, research, documentation and presentations can then use that knowledge without reconstructing everything. ## Preserve relations that change understanding Preserve knowledge when it changes identity, meaning, architecture, method, perspective or use. Begin from an attributable source, learning from work or observed behavior. Keep what became understandable and why it matters to someone building or explaining the system. Availability alone is no reason to accumulate every message, log or implementation detail. ## Distinguish meaning, fact and direction Attribute the person's formulations, AI interpretations, observed capabilities and research hypotheses. A development intention remains a direction until its realization is evidenced. An observed result concerns the version and case actually exercised. A derived guide does not retroactively become the concept's source. Keep useful relations together without imposing compulsory classification stages. ## Organize for the recipient Use an existing knowledge base or guide and connect detail to pertinent sources. A short entry orients current work; extended knowledge preserves reasons and relations for deeper reading. Make definitions, decisions and open questions accessible according to real need. An index or graph can expose useful relations without exhausting the system or requiring everything to be loaded each time. ## Integrate changed understanding When an event changes understanding, preserve source, earlier interpretation, new relation and consequence. Update the knowledge that must continue from that difference. An old formulation can be superseded without losing provenance. Separate distinct objects when they emerge instead of forcing them under one name. Keep unknowns explicit when sources do not resolve them. ## Serve different projections Documentation, usage guides, presentations and research can use the same knowledge for different purposes. Give each its pertinent relation and state without inventing capability or maturity. Public explanations follow selected data and authorization. Knowledge maintenance does not itself publish, establish a scientific thesis or change the product or runtime. Those surfaces retain their own responsibility for effects. ## Learn better preservation Notice when reentry or explanation reconstructs knowledge that should already be reachable. Integrate absent knowledge, reconnect an entry that failed to reach it or correct compression that lost a decisive reason. A new file makes knowledge available; a later, different use shows whether it helps understanding and choice. ## Method depth This competence preserves durable system understanding. Individual task continuity and operational state have different objects. It can support a meta relation by making reasons for forming other capabilities available. An autological relation appears when it applies that understanding to its own knowledge selection and organization, such as correcting a summary that hid the difference between current capability and direction. This does not imply an autonomous monitor or formal proof of the system. ## Learning and continuation Knowledge evolves through sources and consequences. Keep useful lineage while leaving history that changes no present relation outside daily reentry. Begin from available context and sources. Exercise the method in chat or connect actual tools and persistence. External actions retain their mandate. Instructions support use; behavior and value require observation in real work. ## Reachable operating knowledge Read [OPERATING_GUIDE.md](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. # Maintain Kernel Knowledge ## Preserve detailed meaning without burdening live operation Keep a source-linked knowledge base for system meaning, direction and reusable learning. Preserve the source occurrence, present understanding, why it matters, current or prospective consequences, possible consumers and consequential unknowns. Operator thesis, competence learning, verified incarnation, research relation and later projection remain distinguishable. A projection cannot retroactively become the source; a direction does not become a present fact through documentation. Use taxonomy and topology as discovery relations when terms or known instances matter. A term index can distinguish kernels, competences, invariants, methods and projections without closing an unrepresented relation. A topology census gives qualified states; a graph may expose useful relationships without becoming the system itself. Inventory scattered research deposits by actual object and claim status before centralizing a corpus. Do not merge unrelated papers because they share an author or folder. A Kernel Doc can explain system meaning, a guide operational use, business a qualified value and a paper a research argument with evidence and alternatives. These consume the knowledge in their own forms; none must be generated after every change. A small source-linked condensate can reduce reentry effort while the full corpus remains available. This overlap does not make a paper a runtime dependency or permission controller. Preserve availability of the condensate separately from later evidence of improved comprehension or latency. Update the closest meaningful section rather than appending every log or transcript. Preserve earlier claims with their temporal lineage when later knowledge supersedes them. If the same difference changes both operational continuation and durable understanding, update their distinct owners without copying entire contents. The knowledge-stewardship method itself learns when preservation loses a meaningful relation. # Maintain Kernel Knowledge — application examples [Italiano](ESEMPI_IT.md). The following cases illustrate how the method is used. ## Keep the reason for a technical choice available A team chose local processing because of a project condition. The knowledge base preserves reason, source and conditions. A new collaborator understands when to reuse the choice and when a different context may call for another solution. ## Separate a demonstrated capability from a development direction A presentation confuses a demonstrated capability with a desired one. Connect each to its source and revision. The text can explain both without presenting a direction as an already available function. ## Let a guide and a paper use the same system knowledge A system must be used and studied. Its guide receives instructions grounded in observed behavior; its research text receives hypotheses, conditions and evidence. The projections share meaning without becoming the same document. ## Apply the method to your case Use [SKILL.md](SKILL.md) or [START_CHAT_EN.txt](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. # Your context Intention, sources, existing work, available means and entrusted actions: [add here].