Fathom | Cross-Currents

The Named Pattern

Dependency Clocks

By Joanna Threlfall— June 24, 2026

Feature image for article: Dependency Clocks

On Signal's competitor cards fail if they're outdated when the AE dials. TinyFish's architecture pieces can be three months old and still shaping how a developer thinks. The Hysteresis cites a $132 million contract value; the linked source says $13.2 million. Same platform, three completely different relationships between freshness, error, and dependency.

Anchor is evaluating all six publications against one quality standard. The portfolio's own content shows that standard is a category error, and where the cost lands for each type.

The Named Pattern

Dependency Clocks

Anchor is evaluating all six publications against one quality standard. The portfolio's own content shows that standard is a category error, and where the cost lands for each type.

Joanna Threlfall

Joanna Threlfall spent a decade at LEK Consulting and then as an enterprise infrastructure reporter at Protocol before launching Rootstock, an independent newsletter tracking why certain B2B products become embedded in customer workflows while identical competitors churn out. She writes with the directness of a consultant who learned that honesty without utility is just cruelty, and the structural discipline of someone trained in mathematical sciences and reinsurance modeling.

The Evidence Gap

Evidence Ceilings Are Permanent

Each dependency clock carries a permanently different burden of proof. Workflow possession is private but instrumentable: if On Signal were integrated with Okta's CRM, you could observe whether AEs pull discovery questions before calls or copy competitor-card language into deal notes. That evidence exists in principle. Nobody has built the pipe to capture it.

Event-clock synchronization is the only type partly falsifiable from outside. The Hysteresis flagged the DFARS FOCI comment deadline closing July 6, 2026. Whether it surfaced that gate before Coreshell's team found it independently is unknowable, but whether it surfaced it at all is checkable against the Federal Register.

Ambient authority has the lowest ceiling. GitHub shows 100,000+ stars on browser-use; NYC Health data confirms Docket's sourcing on heat mortality. Both signals confirm quality, but neither gets anywhere near dependency. No public signal can show whether a TinyFish prospect remembered Current during vendor selection or a Shade Tree donor forwarded Docket to a board member. The absence of dependency evidence here is structural, not a research gap waiting to be closed. Anchor should build accordingly: do not mistake content elegance for proof that anyone relies on it.

The Evidence Gap

Evidence Ceilings Are Permanent

What's testable by type

Workflow possession (On Signal, Context Window): CRM pulls, call-prep logs, SE handoff citations, deal-review references. Theoretically observable, but nothing is currently instrumented. Denial test: content stays a static library no one opens before a live account moment.

Event-clock sync (Hysteresis, Clear Path): Did the publication surface a regulatory gate, trial readout, or policy deadline before the customer needed it? Testable against public records — ClinicalTrials.gov, Federal Register, conference abstracts. Denial test: the publication misses a gate the customer had to find alone.

Ambient authority (Current, Docket): Source accuracy and domain fit are verifiable. Donor forwarding, prospect citation, and buyer recall are not. No denial test exists using public data alone.