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. # Public Learning Promotion Recognize which method, observation or capability retains value outside the context that produced it. Distinguish the reusable contribution from private details and form an account coherent with what was observed or built. Use this competence when project experience could become a guide, method, resource or public case. Projects produce knowledge as they encounter problems, recognize limits and change methods. Preserve the shareable relation and the conditions giving it meaning. Its form may be an observation, guide, usable capability or research question. ## Recognize the reusable contribution Begin with a precise event or knowledge: what happened, what became understandable and which later choice might change. Consider the outside recipient's useful outcome: understanding, use, verification, collaboration or research. A technical change or new name is not sufficient reason to publish. An open question can have value when its state is clear and its source makes it understandable. ## Generalize while preserving conditions Separate the useful mechanism from details specific to a person, client or environment. Understand whether the relation retains meaning in another case and which conditions must accompany it. Removing names is insufficient: a problem depending on particular access or configuration does not become universal. Use a neutral example when it explains the same mechanism and identify it as illustrative. ## Preserve the state of knowledge Distinguish observation, interpretation, implementation, exercise, repetition and external validation. Do not turn one successful internal case into a general performance claim or weaken a supported capability into vague speculation. Make uncertainty, scope and revision clear where they affect understanding. A detail changing the conclusion belongs in the explanation, not a hidden note. ## Choose form and recipient Let the relation determine form: a clarified error may become a practical note, a repeatable method a guide, a capability a kit or an unknown a research question. Reach an existing public owner for that capability before creating competing derivatives. The product owner retains capability truth; writing forms its expression. Several recipients may receive different contributions from one event. ## Transfer a usable capability For an operating resource, include the knowledge needed to perform and continue work: accessible sources, decisions, usage conditions, necessary tools and learning. A well-described principle is not the same as a received capability. Replace private dependencies with real entries and explain the method's contribution. A simple article does not require unnecessary installation or packaging. ## Retain the return from sharing Before a public effect, protect personal data, credentials, private relationships and strategies not selected for sharing. Preparation does not send or publish. After an authorized effect, use misunderstandings, criticism and usage cases to understand what should change: product, text, distribution or generalization. If the loss arose from selecting what was shareable, correct this competence itself. ## Method depth The work has a meta relation when it takes another activity's learning as its object and forms a transferable capability. Not every observation requires a product. An autological relation emerges when public feedback changes recognition and generalization of learning themselves. A guide that lost a decisive condition teaches this competence what to preserve next. That return is distinct from automatic publication. ## Learning and continuation Attribute the event, initial interpretation and later understanding. Public feedback may improve the resource without rewriting what the initial case actually showed. Begin with actual context, sources, means and mandate. The method can operate in chat. Instructions make a capability usable; real work reveals its behavior and value. ## 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. # Public Learning Promotion ## Promote the reusable relation and preserve its conditions Understand what remains useful when private context is removed, what evidence supports it and why sharing helps the receiving public. Benefits can be comprehension, inspectability, trust, adoption, collaboration, research or useful business understanding; engagement is one possible consequence. A local observation, demonstrated method, implemented capability and open hypothesis can each be useful when their status remains clear. Do not invent maturity or demote a supported current capability to a mere possibility. Remove private contacts, credentials, unpublished strategy, raw conversations, local account state and sensitive runtime details that are unnecessary to the relation. Keep the concrete mechanism and conditions making the lesson true. If the source has a canonical public derivative, let its native learning enter that owner before later explanation. A distinct lesson belonging to another domain returns there instead. When the public destination is an independently usable competence or product, transfer usable method through its actual receiving entries and consumers. A principle added to a repository may leave the capability absent. An article alone need not load a compiler or packaging system. Choose guide, field note, research question, demo, product delta or another form from the contribution. Promotion readiness and actual publication are different states. Public misunderstanding, critique, use, independent propagation and unchanged outcomes can teach different owners. Return a writing lesson to writing, a product lesson to the product and a generalization lesson to this method. Preserve claim scope and private/public lineage without forcing every observation into a content calendar. # Public Learning Promotion — application examples [Italiano](ESEMPI_IT.md). The following cases illustrate how the method is used. ## Turn a source-freshness failure into a public guide A team discovers that its assistant read superseded documentation. The public guide explains the distinction between finding a source and establishing its version. Demonstration documents preserve the condition causing the failure without exposing project data. ## Share a client-work method with its dependencies intact A consulting project develops a useful way to compare requirements and deliveries. Share its criteria and a synthetic example. Exclude names, confidential amounts and internal comments while retaining the dependencies that make the comparison useful. ## Present an observation as a research question Unexpected behavior suggests a hypothesis. Present the observation, conditions and alternative explanations. The resource invites investigation without turning one experience into a law or a generalized experimental result. ## 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].