← Back · Home / Prediction Diary
Published before the outcome
KP Prediction Diary
Every entry here is published before its outcome is known: an anonymised horary question, the horary number, and the engine’s own judgment and timing window. Nothing is edited after publication — each entry’s content hash proves it. Outcomes are recorded honestly, including when the window misses.
Loading…
How to read an entry
Each entry shows the engine judgment (Promised / Denied / Promised-with-delay) and its timing window at the moment it was published — before the real-world answer was known. Once the window has passed, we record whether it happened inside the window, outside it, or not at all, and that outcome is the only thing ever edited afterward. The content hash is a fingerprint of the original judgment text; recomputing it should always match what’s shown.
Why unresolved entries are never hidden: excluding them from view would let only convenient outcomes accumulate. The count above is taken only from resolved entries, but the unresolved count is always shown alongside it.
FAQ
Why are the questions anonymised?
A horary question can be personal. Every entry here is stripped of any identifying detail before publication — only the astrological content (question category, horary number, judgment) is shown.
What does “content hash” mean?
A SHA-256 fingerprint computed from the question, horary number, judgment and window at the moment of publication. If that text were ever quietly edited afterward, the hash would change and no longer match what’s recorded — it’s how this page proves it isn’t rewriting history.
How is the resolved-in-window count worked out?
Resolved entries only: “happened inside the window” counts toward it; “happened outside the window” and “did not happen” do not. Unresolved entries are left out of the count but their number is always shown separately, never hidden.