A Mech snippet embedded in a FedWiki page is not just a job description that produces results. It is an *utterance* placed into a communicative situation. What it “does” cannot be fully determined at execution time; it becomes intelligible only through how later pages take it up. Survey probes act as **deputies for EXTRACT**. They do not replace extraction, nor merely consume its output. Instead, they re-enter the extraction results into the wiki as addenda: pages that select, summarize, and re-describe what EXTRACT has made available. This re-description is already a communicative move. As probes interact with the Mech process, a **movement in the lineup** emerges. New pages appear on the right that reference back to the original snippet on the left, while simultaneously reshaping what that snippet is now taken to mean. The meaning of “it” is not fixed upstream; it stabilizes only through these reference-backs. This differs fundamentally from pipeline thinking. A pipeline assumes meaning is defined in advance and merely transported through stages. Here, meaning is produced **retroactively**: later pages determine what earlier operations are understood to have been. Explanation is not external documentation but happens in the same medium as execution — the wiki itself. To *make uptake inspectable* means to design EXTRACT, probes, and Mech snippets so that these reference-backs are explicit: which distinctions were selected, which folds or relations were taken up, and which were ignored or deferred. Inspectability lives in the lineage of pages, not in a final report.
See Discourse Graphs