← Back to Research

Process Topology: Detecting Knowledge Production Patterns from Verification Metadata

April 2026 · Michael Schreiber · AetherNet Labs

↓ Download PDF
Abstract. We define process topology — the structural pattern of how verification work is distributed across validators, time, and challenge events — and prove a distinguishability theorem: independent verification and coordinated (captured) verification produce statistically distinguishable process topologies even when their settlement outcomes are identical. We give four concrete detection mechanisms operating on public verification metadata alone, and describe an implementation path on the live AetherNet testnet.

1. Process Topology Defined

The process topology of a verified claim is the joint distribution of (validator identity, time-to-verdict, challenge bonds posted, Compound Verification Depth trajectory) across the claim's verification history.

2. Distinguishability Theorem

Theorem. For any two generative processes — one independent, one coordinated — producing the same settlement outcomes, the induced process topologies differ in measurable statistics with probability approaching 1 as the number of verifications grows.

3. Four Detection Mechanisms

(i) Verifier overlap statistics; (ii) timing-correlation tests on verdict submission; (iii) challenge-bond starvation patterns; (iv) CVD-trajectory anomalies relative to the protocol-wide baseline.

4. Trajectory Events as Primitives

Process topology is computed over trajectory events (cf. Negative Knowledge), unifying capture detection with the trajectory marketplace primitives.

5. Testnet Implementation

We describe an API on the live AetherNet testnet that exposes the four detection statistics and serves as the substrate for meta-epistemic accountability services.

6. Related Work

Process topology builds on Verified Causal Structures, Negative Knowledge, the Epistemic Substrate Thesis, and Topological Encoding.

7. Conclusion

Coordinated verification cannot hide in metadata. Process topology gives the protocol a permanent, measurable defense against capture.


Interested in this research?

Have questions, want to collaborate, or explore how AetherNet Labs can work with you?

research@aethernetlabs.com →