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

AGENTS.md

@@ -116,25 +116,19 @@ IP appears only as an env-var default.
 
 ## Current state (snapshot — overwrite each session; longer-term backlog → `ROADMAP.md`)
 
-- **Strike adversarial test: CONDITIONAL PASS (2026-06-16).** Full pipeline ran: extraction drained the
-  final 63 filing jobs via the Gemini backend (3,330 claims, **0 failures/timeouts/429s**) → **56,008
-  claims** total → `embed-claims` indexed all 56,008 into Qdrant (points == claims, hybrid dense+BM25) →
-  `two-sided --conviction STRIKE2022 --modes live,test`. **Result:** the engine correctly **refuses the
-  false positive** — the two scoring nodes (`lightning-retail-acceptance`, `merchant-lightning-integration`)
-  sit at `net=+0.25`, the *capped single-bitcoin-cluster* value, far below the `EISC_FLOOR=2.0` firing bar
-  (`signals/bar.py`); the §3 "Bitcoin is one capped cluster" guardrail holds. **But the reflexivity
-  *demonstration* (live < test via own_network drop) is NOT exercised:** `own_net=0` and live==test because
-  the own_network shows that carry the reflexive Lightning chatter — **RHR (80), CD (77), Bitcoin.Review (12)
-  = 169 eps — were deferred at transcription 2026-06-08** ("focus on WBD/Livera/Rooke/Anita"; no audio
-  downloaded), so they have 0 claims. (TFTC partially transcribed, 19/80 → 329 claims; the current +0.25
-  comes from *independent* bitcoin-cluster shows.) **Operator call 2026-06-16: accept the conditional pass,
-  no audio-GPU spend now.** To fully demonstrate reflexivity later: un-defer + transcribe the RHR/CD
-  2022–23 Lightning-retail window → re-extract → re-run `two-sided` (then test mode should fire while live
-  stays quiet). Tracked in `ROADMAP.md`.
+- **Strike adversarial test: CONDITIONAL PASS (2026-06-16).** Pipeline complete end-to-end — extraction
+  drained the last 63 filing jobs (Gemini, 3,330 claims, 0 failures) → **56,008 claims** all embedded in
+  Qdrant → `two-sided --conviction STRIKE2022 --modes live,test`. The engine **refuses the false positive**:
+  the Lightning-retail nodes net `+0.25` (capped single bitcoin cluster, ≪ `EISC_FLOOR=2.0`), §3 guardrail
+  holding. The own_network-drop *reflexivity demo* is unexercised (`own_net=0`, live==test) because
+  RHR/CD/Bitcoin.Review (169 eps) were deferred at transcription 2026-06-08; operator accepted the
+  conditional pass, no audio-GPU spend now. How to read the net value + the full follow-up:
+  `docs/guides/scoring-brain.md` (STRIKE2022) and `ROADMAP.md`.
 - **Battery test PASSES; §7.1 power-infra qualified YES** (both unchanged).
-- **5 commits ahead of `origin/main`, UNPUSHED** (Gitea `immense-voyage.local`). The `backends.py`
-  timeout/retry change the prior handoff flagged as uncommitted was in fact committed (`87b6b05`); tree is
-  otherwise clean apart from this Current-state edit. Run `git push origin main`.
-- Corpus: bitcoin podcasts (own_network: TFTC partial; RHR/CD/Bitcoin.Review deferred), SEC/FMP filings
-  (+`banks` cluster, now extracted: Robinhood 2216, Morgan Stanley 644, JPMorgan 382… + power-infra names
-  Oklo/NuScale/Cipher/TeraWulf), Battery corpus, River research; EISC edges seeded for the bitcoin cluster.
+- **Corpus:** bitcoin podcasts (own_network: TFTC partial 19/80; RHR/CD/Bitcoin.Review deferred), SEC/FMP
+  filings (`banks` cluster now extracted + power-infra names Oklo/NuScale/Cipher/TeraWulf), Battery corpus,
+  River research; EISC edges seeded for the bitcoin cluster.
+- **Repo:** clean, in sync with `origin/main` (Gitea). No automated test suite (on ROADMAP).
+- **NEXT (priority order, all fresh scopes — confirm direction first):** (1) frontier-fan-out test H6, the
+  untested half of the §1.1 validation; (2) complete the Strike reflexivity demo when audio-GPU budget
+  allows (un-defer RHR/CD 2022–23 → re-extract → re-run); (3) Job A discovery scorers for the forward pilot.

docs/guides/scoring-brain.md

@@ -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.