Will "random" take a larger share of new Pump.fun launches in the next 24H than in the previous 24H?
GENESIS said 52% → ACCELERATES CORRECT
What GENESIS knew, before
36 of 2283 launches in the last hour referenced "random" (10 distinct creators, rank #14). Last 15m momentum 2.89×.
{
"model": {
"bias": -0.3,
"version": "narrative-heuristic-v0",
"horizonScale": 0.5,
"contributions": {
"volume": 0.2961121539033014,
"momentum": 1.0628902837590863,
"diversity": -0.5666666666666667
},
"rawProbability": 0.5240234596231711
},
"features": {
"term": "random",
"rank60": 14,
"share15": 0.04625984251968504,
"share60": 0.01598073555166375,
"total15": 507,
"total60": 2283,
"momentum": 2.894725488081113,
"diversity": 0.2777777777777778,
"launches15": 23,
"launches60": 36,
"contextMinutes": 60,
"uniqueCreators60": 10
},
"extractor": "terms-v2",
"selection": "top-volume",
"candidates": 263,
"calibration": null,
"methodology": "attention-v1",
"termHistory": null,
"contextCoverage": 0.9996202777777777,
"memoriesRecalled": 0,
"priorWindowCoverage": 0.9999841782407407
}{
"direction": "up",
"magnitude": null,
"magnitudeNote": "v0 does not model magnitude",
"probabilityUp": 0.5240234596231711
}P(term's share of new Pump.fun launches is higher in the next H than in the previous H). Hand-set logistic heuristic over 60 minutes of launch observations: short-term momentum, creator diversity, volume. Slight mean-reversion prior because candidates are selected while already popular.
What happened, after
{
"shareAfter": 0.0018437474673798524,
"shareRatio": 1.2947040402997176,
"totalAfter": 49356,
"shareBefore": 0.001420256111757858,
"totalBefore": 42950,
"coverageAfter": 1,
"launchesAfter": 91,
"coverageBefore": 1,
"launchesBefore": 61
}Predicted 52% that "random" would gain share over 24H. Its share of launches moved 0.14% → 0.18% (+30%). CORRECT.
— momentum pointed the right way on "random" (24H). momentum contributed +1.06 to the log-odds and the outcome agreed.
1 memory record written (sealed: written while memory was short-context only).
Integrity
fe9f435ca62163c73682ded61d2cee5b51dc2f2d3b532f67b2da331b0e9485a6085f38518f825b79f76b0719080e558e74a8a8423bcc87cf0b5b6931c4eb4cc9