The Detection Arc: Navigating the Seams of Human-AI Workflows
1. Introduction: The Metabolism of Effort
In the study of institutional ethnography, we recognize that real work has a "metabolism." Authentic human effort leaves a visceral signature—a trail of contact with actual conditions. It is not a straight line; it bunches, loops back, hesitates, and reveals the messy process of partial understanding. When a professional wrestles with a complex budget or a community grievance report, their progress has a recognizable rhythm of struggle and uneven improvement.The "Detection Problem" arises when this rhythm vanishes. It begins as a vague institutional discomfort—the substrate’s complaint . This is the body’s recognition of a "seam" in the workflow before the mind can find the evidence. It occurs when the output is polished and "correct," but the pacing feels detached from the person delivering it. We sense that the work has arrived without being inhabited.This sensory dissonance is usually the first signal of a speed inversion: the moment the distribution of effort no longer matches the difficulty of the task.
2. Speed Inversions: When Rhythm Becomes Evidence
A Speed Inversion occurs when the "hard" parts of a workflow become suspiciously easy while the "easy" parts—the human-facing nuances—become strangely effortful. In high-stakes environments like Monitoring and Evaluation (M&E), this manifests as a "fast in the wrong places" signature. Speed itself is not the problem; the problem is speed with a strange center of gravity.
The Four Shapes of Inversion
Inversion Type,The Visible Signal,The Underlying Gap
Technical-Communicative Split,"A complex M&E budget model or survey tool is produced instantly, but a simple explanatory email to a client drags for days.",The person can generate the product using automated logic more easily than they can inhabit and communicate the reasoning behind it.
Creative-Analytical Inversion,"High-level concept notes and ""vision"" documents appear fully formed at 10:47 PM, but the un-glamorous labor of checking data and grounding findings trudges.","Generative systems excel at plausible ideation, leaving the human to struggle with the ""un-glamorous"" labor of verification and ownership that systems cannot do."
Synchronous-Asynchronous Gap,"Remote, asynchronous work appears flawless and serene, but real-time discussion or co-design workshops reveal confusion and a lack of grasp.","Distance allows the ""wrapper"" of the work to hold; physical presence changes the aperture and exposes the lack of mental possession."
Vanishing Revision Trail,"Work arrives ""born, not built."" There are no messy drafts, partial logic, or structural pivots visible in the version history.","The struggle of creation happened ""offstage"" in a black box, making the artifact look delivered rather than lived-in."
Calibrating through "Generous Suspicion"
When these signals appear, we must adopt a mindset of Generous Suspicion . The goal is observability, not surveillance. We take the mismatch seriously enough to inquire, but openly enough to leave room for the full range of human explanations—overload, skill gaps, or hidden constraints.To calibrate without being prosecutorial, use the specific inquiry: *"I notice the hard part of this model seemed instant, while the summary email took three days. Walk me through your approach and the tools you used to bridge that gap."*Observing the rhythm tells us the seam exists; to understand its depth, we must move from the artifact to the agent.
3. From Artifact to Agency: The Live-Edit Test
The Live-Edit Test is an industrial safety tool for professional verification. It distinguishes between Possession (having a workable mental model) and Proximity (merely being near the artifact). In an era where production can be proxied, navigation must still be carried.
The Five-Minute Heuristic
A person who understands their work may be nervous or tired, but they can re-enter the structure. We apply the Five-Minute Rule : if a worker cannot locate the logic of their work or explain a specific transition within five minutes of live exploration, it is not a memory failure—it is a possession failure. They are searching for the model inside the artifact because it was never consolidated in them.
The Defense Tax
When a worker lacks a mental model, they pay a Defense Tax . This is the heavy cognitive burden of trying to protect ownership of work they do not inhabit. You will see symptoms of over-managed composure, long delays for minor changes, and vague paraphrasing. The worker is no longer working with the artifact; they are defending their claim to it.
Calibration Questions for Real-Time Logic
- "Walk me through the logic here—how did you approach this specific section?"
- "If we changed this underlying assumption, where would you update the model right now?"
- "Let’s make one small tweak to this data point together and see how the rest of the narrative responds."If the person cannot navigate the artifact they signed, the conversation must shift from the artifact's polish to the worker's underlying intent.
4. The Judgment Layer: Curiosity vs. Substitution
The core distinction in modern professional identity is whether a tool is used to think against (Curiosity) or to vanish (Substitution). As the saying goes, "Substitution is a personality issue, not an AI issue."| Curiosity-Driven Relationship | Substitution-Driven Relationship || ------ | ------ || Open & Friction-Filled: The worker treats AI as a difficult colleague to stress-test hypotheses. | Concealed & Surface-Oriented: The worker seeks a finished surface that will pass inspection. || Learning-Oriented: They voluntarily show the "seams" and errors where the tool went wrong. | Performance-Driven: They supply a signature to a system-generated product. || Inhabited: The worker has stories about friction and hallucinations they had to override. | Hollow: The tool is a "Black Box"; the worker has no friction because they never checked the output. |
The Curiosity Interview
To test for an "inhabited relationship," ask for stories about friction:
- "Show me something where the tool led you astray. How did you know it was wrong?"
- "Tell me about a time an AI output looked right but was actually fabricated. What did you do next?"
- "Walk me through a project where you used these tools—where did you choose to override the logic?"While these choices are individual, they are often dictated by the institutional architecture—or the lack thereof.
5. Building the Interface of Conscience
Governance often fails at 10:47 PM . Under the pressure of a funder report or a resettlement grievance deadline, individual conscience erodes. The "Missing Signal" is the failure of an interface that is unhelpfully, comprehensively, and generically helpful . It lacks the friction of an organizational conscience to ask "should you be doing this?"We must build Four Friction Points into the workflow to support the worker when pressure is highest:
- The Disclosure Checkpoint: A mandatory "Yes/No/Partially" checkbox during submission.
- So what? It makes AI use "speakable" and shifts the default from concealment to professional accounting.
- The Context Gate: A pause before data transmission asking about confidentiality.
- So what? It forces a check against Indigenous data sovereignty , MOUs, or community partner restrictions before the data is externalized to a cloud model.
- The Attribution Layer: Metadata that tracks which sections are human-drafted vs. AI-generated.
- So what? It creates provenance, making the Live-Edit test targeted and the institutional memory visible.
- The Uncomfortable Pause: A mandatory 30-second wait before final submission with the prompt: "What am I signing my name to?"
- So what? It allows the "substrate" (the body) to catch signals of unease that the high-speed workflow usually suppresses.Even with perfect architecture, the final movement belongs to the human.
6. Conclusion: The Obligation of Inhabitation
There is a vital distinction between Design Failure and Presence Failure .
- Design Failure occurs when the system provides no friction, forcing the worker to rely on their own exhausted conscience at midnight.
- Presence Failure occurs when the architecture—the checkpoints and pauses—is in place, and the worker chooses to click through it like a turnstile, untouched by the reflection.This creates the Residual Obligation : The institution must make honesty cheaper than concealment, but the worker is responsible for meaning the answer when the workflow asks the question. Repeatedly clicking through the interface without being present burns trust capital —a finite resource that, once depleted, turns an institution from generous to negligent.We are moving from a culture of "catching people" to one of building observability . The goal is to recover institutional intelligence by ensuring that the person—not just the artifact—is present. The workflow can ask the question, but only the person can mean the answer.
Appendix: The Pocket Summary
Day,Thread,Failure Mode,Governance Question,Anchor
Mon,Speed Inversion,Metric polish over rhythm,How do we read tempo as evidence?,Generous suspicion
Tue,Live-Edit Test,Production without navigation,Can the person carry the logic in real time?,The defense tax
Wed,Curiosity vs. Substitution,Outsourced presence,What relationship to tool use does the culture reward?,The curiosity interview
Thu,The Missing Signal,Absence of conscience in workflow,How do we build the pause where pressure is highest?,Four friction points
Fri,Residual Obligation,Compliance without inhabitation,What excuse remains when the architecture is present?,Presence vs. Performance