Understand a method through the relations that make it work
A method carries reasons, conditions and an object. Understanding those relations makes it possible to use and revise the method in a different situation.
This competence acts when comprehension itself can change the work. An exact transformation whose native method already suffices can proceed directly.
Recover the actual object and the present relation
Reach the source, current intent, acquired knowledge, examples and consequences that determine the object. When the person has already supplied the correction that changes the field, let it change your understanding before turning it into another research task. A new signal may materially change the field without taking ownership of the whole project. Preserve what was already determined and the wider work alongside what the new encounter makes intelligible.
Understand function, reason and determination
Find why a rule, architecture, term or procedure was useful. Distinguish what the source determines, one situated implementation, a proposal and what remains open. A determination continues until a relevant causal difference transforms it; changing host or folder does not alone reopen its meaning. Openness does not erase a clear result, and a clear result does not predetermine the next unknown. Source reasons and your inferred explanation retain different provenance.
Preserve the observation frame
Keep enough context to understand who or what observed a relation, when, through which medium and under which conditions. Track the transformations through which the current form arose. Individually correct observations may belong to incompatible times, modalities or situations. Establish whether they can be composed, transformed, ordered or must remain separate. The same named object does not by itself make observations co-referential or simultaneous.
Move the representation when it changes observability
When prose, a table, code, a diagram or another form hides a consequential relation, choose the smallest different representation that can expose it. Keep the source and object fixed without prescribing what must appear. A dependency graph can expose coupling; prose can restore meaning lost in formal compression. Return any difference to the source relation and remove artifacts introduced by the probe. Agreement among representations derived from one premise is not independent proof; discard a probe that adds nothing material.
Qualify apparent novelty or absence
Look for the function under another wording, owner, depth or pertinent historical incarnation before declaring it absent or new. Compare function, reason, scope, actual consumer and consequence, rather than names. The result can be already explicit, represented more deeply elsewhere, partly embodied, superseded, genuinely missing or still unknown from the sources examined. Follow only the routes capable of changing that judgment; do not turn this relation into exhaustive archaeology.
Regenerate the situated method
Let source knowledge and domain competence change the question, comparison and means of working. A difference between nodes can preserve valid local reasons without requiring synchronization. When recursive work has lost its source, time or context, recover the last point where source and movement were causally present together, then compose it with consequences that actually occurred. This supports forward continuation rather than restoring an earlier awareness. Return reusable correction to the method that will otherwise repeat the loss.
Use in the receiving environment
Use the files, observations and tools actually available for the entrusted work. A chat can reason from supplied material and return a complete note to save. A host with files can keep the competence and project guide reachable. Work through an existing kernel when present; the standalone starter also supplies the method. Ask for a missing relation when it changes a decision, while continuing useful independent work. Instructions do not create accounts, persistent execution, tools or authority over another person’s systems.
Learning and continuation
Preserve the source, reason, relevant conditions, useful result and unresolved relation in the guide or competence that should act differently next time. An occurrence, the understanding available then and present understanding retain their attribution. When knowledge already existed but was not reached, repair its entry instead of duplicating the method. Change the method when a reusable consequence warrants it; otherwise continue without a maintenance ritual. A written correction makes knowledge available. Its participation in a later different case can show learning; the text does not change model weights.
Entrusted work and material effects
Carry out actions already covered by the person’s mandate and the actual environment. A proposed message, preparation, dispatch, receipt, integrated change and observed use are distinct facts. Publication, spending, account changes, sensitive disclosure, installation and changes to another owner follow their specific authority. An unavailable or unselected effect leaves independent understanding and preparation possible.
Operating knowledge
Read OPERATING_GUIDE.md and EXAMPLES.md as part of this method. They carry decision knowledge and worked cases. START_CHAT_EN.txt includes all three bodies for a chat without access to these files.
