Five lenses used to design DevPlane instrumentation. Each links to the canonical write-up on peopleanalyst.com. This site lists how product features map to those lenses; it does not replace the papers.
Clusters
Coordination
Stigmergic queues, handoffs, and collision mechanics in multi-agent + multi-tool work. Measures where information loss and false completion accumulate when nobody messages anyone directly.
Brief fidelity, repair after rupture, and whether the operational contract between operator and tooling holds across rewrites, rollbacks, and rework. Borrowed measurement language from psychotherapy process research; applied to dispatch and merge events.
Access, cost of legibility, refusal and halt semantics, and which failures the board renders visible vs. invisible. The interface arm asks what the joint system optimizes when automation improves.
Provenance, attribution, and continuity of voice across human and model-generated artifacts. Minimum metadata so longitudinal panels know which signals are operator-written vs. model-written.
Coordination cost in heterogeneous AI tool ecosystems — pre-registered designs, open methods where production data permits, and DevPlane as measurement apparatus.
Arm A — Agent ↔ agent. Stigmergic coordination through shared artifacts; drift and failure modes when agents do not message each other directly. peopleanalyst.com/research/coordination
Arm C — Interface (lead). The joint system; C1 risk compensation asks whether coordination improvements produce offsetting drops in operator vigilance (Ironies of Automation in software ops). Program framing and lead study: peopleanalyst.com/research/devplane