Pressfront / Trace / Where did the Project Anchor gravity story start?
Traced story · Updated September 2026
A pseudo-scientific claim called the Anchor Paper spent most of a summer going almost nowhere, then went national in three days. We swept 415 tiles across ten sources to find the first public post, and this page is the result, including the parts the sweep could not reach.
The earliest public appearance we could verify is a thread by @Timeonaut on X, posted 17 June 2026, 11:32 UTC measured, opening the "ChronoGravity framework" with what it called the Anchor Paper. The post that made the story national came 56 days later derived: @Newsweek on X, 12 August 2026, 14:29 UTC, reach 3.41M measured.
Confidence in that origin is 71% derived, and the reason it is not higher is printed with it: only one platform saw the early window, so nothing corroborates the seed post. Coverage of the ten sources we tried was 6/10 measured.
The screen, as the tracer printed it
Project Anchor gravity, window 2026-06-15..2026-08-31https://x.com/Timeonaut/status/2067208740533637393Verbatim from the tracer: “earliest we could VERIFY, not proven origin. deletions & screenshot-laundering are invisible to us.”
The private-account rule. We never log in, follow anyone, request access to a locked account, or use scraped private data. A private account is invisible to us and stays that way. So what you see below is the earliest public appearance we could verify, never a proven origin. If a story started in a group chat, a DM or a locked profile, the first public post is the node we can see, and we say so rather than dressing it up as the source.
Run one yourself: Trace a story. How the sweep and the confidence number are built: the methodology card.
The seed post had almost no engagement. It sat there through the back half of June, all of July, and the first week of August. Then in four days it became a story with a 3.41M-reach amplifier attached to it.
That shape is the thing worth knowing about, and it is the argument for watching rather than reacting. Anyone checking this story on 11 August would have found a quiet claim in a corner of X. Anyone checking it on 13 August was already late. The gap between those two days is where a comms person would have wanted to know, and it is exactly the window a trace makes visible after the fact, and a monitor makes visible while it is happening.
We are describing what happened, not forecasting what will. Nothing here says the seed post was destined to break out, and no honest tool can tell you that in advance.
The first deep sweep of this story got it wrong. It reported a Bluesky post from 6 August as the earliest public appearance: 50 days late, on the wrong platform. The correct answer had actually been retrieved by a boundary probe and then thrown away, because only tile sweeps fed the mention list and the seed post had three total engagements, so it never ranked in an engagement-ordered pull.
Seven separate causes were found and fixed, and the re-run produced the result on this page for $0.1065. We publish that because a tool that reports confidence should be able to say when it was wrong, and because the failure mode is instructive: the loudest cluster is never the origin. Cluster selection now prefers the cluster holding the earliest relevant mention and absorbs the louder ones into it, which is why the screen above shows 70 mentions rather than the 13 the failed run found.
Reddit returned nothing on this story. That is worth separating from a collection failure, because the two look identical on a dashboard and mean opposite things.
The archive layer was hand-probed across r/conspiracy, r/space, r/nasa, r/UFOs, r/HighStrangeness, r/singularity, r/collapse and r/skeptic over the full window, and found no on-topic posts. So the zero on this trace reads as genuine absence. On a different story the same zero could mean our subreddit discovery missed the room the conversation was in, and the coverage report would say so. Naming which kind of zero you are looking at is most of the honesty in this product.
The earliest public appearance we could verify is a thread by @Timeonaut on X, posted 17 June 2026, 11:32 UTC, introducing what it called the Anchor Paper and the ChronoGravity framework. That is the earliest public post we found across a ten-source sweep of 415 tiles, not a proven origin. Only one platform saw the early window, so nothing corroborates it, and our confidence in it is 71%.
56 days. The seed post is dated 17 June 2026 and the biggest amplifier we measured, reach 3.41M, posted on 12 August 2026. Burst detection over the free-sensor daily curve independently placed the acceleration between 2026-08-10 and 2026-08-13, peaking 2026-08-12. Both numbers come from the same sweep and agree with each other.
Because only one platform saw the early window. Confidence is six numbers multiplied: coverage, timestamp reliability, a boundary penalty, an origin penalty, match strength, and a relevance-health term. The origin penalty fires when nothing corroborates the earliest node. On this trace coverage was 0.91 (6/10 sources returned results, and an empty answer counted at that source's expected recall (4 at the census estimate, which is modeled)), the origin penalty was 0.8 for the single early platform, relevance health was 0.97 (the share of in-window posts that were on topic), and the other three were 1.0. The formula is versioned (v2.1-2026-09-18) and printed on every result, so a score from one version is never compared with a score from another. A single-source origin with a native timestamp is good evidence and weak corroboration at the same time, and 71% is what that combination honestly looks like.
Yes, and we say so on every result. We never log in, follow, or access private accounts, so a claim that circulated first in a group chat, a DM or a locked profile is invisible to us. What we report is the earliest public appearance. On this trace the path includes a screenshot claim node, which is exactly the shape a leak from somewhere private takes when it reaches the open web, and it is stored as unverified rather than counted as a source.
Free trace, no account for the first one. You get the same screen you just read.
Honest fine print. Trace reports the earliest public appearance we could verify inside the window we searched, which is not the same thing as a proven origin. We only read public posts and public metrics, so deleted posts, screenshots laundered out of private accounts, and anything that started in a DM or a locked group are invisible to us, and every result names the sources that came back empty. Confidence is a number we publish together with the gaps behind it, never on its own. Trace describes what has already happened and how fast it is moving right now; it does not predict what will go viral, and no honest tool does.