grant/ten31-signal-engine
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Tighten Current state; document two-sided net-value interpretation

Browse Source
This commit is contained in:
Keysat
2026-06-16 12:53:14 -05:00
parent 0cba2626d3
commit 29bca8b387
2 changed files with 20 additions and 21 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/guides/scoring-brain.md
+5
View File
@@ -70,6 +70,11 @@ Pre-registered failed convictions used to test the engine against its target fai
stays quiet in `live` (own_network dropped) while it would fire in `test`** — the engine refusing the
intra-cluster echo. Run `two-sided --conviction STRIKE2022 --modes live,test`. The REALIZED-ONLY rule
is load-bearing here (speculative "Lightning will revolutionize payments" is `predictive`, not signal).
**Reading the output:** a single capped bitcoin cluster nets `eisc≈0.25` — already sub-bar vs
`EISC_FLOOR=2.0`, so a `+0.25` "quiet in live" can be the *cluster cap* refusing the false positive,
NOT the own_network drop. Check `own_net`: if it's 0, live==test and the reflexivity mechanism is
unexercised (the affirmers are independent), so a quiet `live` does not by itself prove the echo-drop —
you need own_network affirms present (`own_net>0`) for `test` to fire above `live`.
**Standing rule S1:** derivatives resolve on OUTCOME (scaled substance), never milestones or enablers.
An announced program / a regulatory unblock / a single bank's toe-in is CONTEXT, not corroboration.