How the readout works.
Helio Commons separates physical feasibility, evidence quality, time pressure, and coordination. A forecast is a prompt for investigation—not a prophecy.
Sources earn weight.
Each source contributes depth, verified items, and kind diversity. The UI shows the exact count used by the engine so a new claim cannot hide behind a polished number.
Dates create pressure.
A near-term prototype gets more momentum than a 2040 scenario, but distance also lowers confidence. This keeps “soon” and “important” from being confused.
Watch, prototype, deploy.
Stage is a leverage multiplier, not a maturity certificate. It tells the reader which kind of evidence would change the decision next.
Every mutation leaves a trace.
Each event uses SHA-384(previousSeal ‖ canonicalJson(event)). The audit endpoint replays the chain, and exports carry the current seal.
Pick a lane.
The routes are deliberately different so the tool is useful in the browser, a terminal, or an agent session.