Integration: bring an idea back

Integration is the point at which an exploratory result becomes a stable object for use or criticism. HLC treats it as part of the practice rather than an optional summary at the end. Without integration, an exchange can produce many associations while leaving no clear claim, question, or artifact that survives the session.

A compact integration record can contain five elements: a plain definition, a concrete example, a counterexample, a source or evidentiary basis, and the next use. These elements need not become a bureaucratic template. Their purpose is to expose what the concept means and how it could fail.

Suppose a boundary search produced “access as maintenance.” Define it as the ongoing work needed to keep an institution usable. Give an example such as updating instructions when a service changes. Give a counterexample where a recurring task has no meaningful effect on access. Then name the observation or document that could test the claim in a particular setting.

A result can also be a rejection. “This analogy does not preserve the meaning of consent” is a useful outcome if it prevents later confusion. Keeping the rejection makes the inquiry more honest than presenting every generated candidate as a discovery.

Integration provides an exit from recursive loops and a test for conceptual exoplanets. It also links exploration to work outside the model. A concept should either improve a subsequent question, inform an artifact, or remain explicitly provisional. It does not become an accomplishment merely because the conversation found it exciting.