← back

m625 is not a clinical decision tool · not a publisher · not an expert authority · not a simulator. It is a cross-domain Roll-formalized evidence atlas with public audit + attack surface.
persona: patient advocate · domain: neuro · tier: 1
ferry target: m511 · fixture id: DEMO-002
self-audit grade: A

i_demo_002 · patient advocate × neuro · chronic-pain attractor pattern

Why a patient advocate would come to evidence.x1000.ai

A patient advocate working in chronic-pain support (post-injury, fibromyalgia, post-surgical, or mixed mind-body) reads about brain-network attractor dynamics in lay press and on forums. Pain points (see 05_docs/M625_PERSONAS.md):

m625 does not advise this advocate or this advocate's community. **m625 shows what a Roll-formalized evidence pattern looks like, and how to tell it apart from marketing**. The advocate is invited to take the formalization back to the community, audit it independently, and tell m625 where the reading layer is misleading.

This is not patient-facing medical advice. This is not a community-treatment plan. (See "What this demo will not say" below.)


The Roll-formalized object (anchored on m517 CARD01)

FieldValue
Upstream cooked cardm517 02_cards_cooked/CARD01_DEEP_v0.2.md (Tu 2020 attractor · TMU-A)
Domainchronic pain (cross-condition: post-injury, fibromyalgia, post-surgical)
Roll TMU typeTMU-A
K4.1 cross-period 3-bitK4.1 = (1, 1, 0) per m604 Framework §4.4
Patternbrain-network attractor dynamics (X = network state · Φ = attractor dynamics)
Source layerTu et al. 2020 (training_data_recall · TODO_unverified; m517 marks the underlying anchor as drafted-not-signed)
m517 statusv0.3.0 Wave 2 closed · BIRTH snapshot 2026-05-21T19:55Z registered to m556

m625 does not modify m517's card file. The reference path is /data/projects/m517_NeuroDynamics_Circle/workspace/02_cards_cooked/CARD01_DEEP_v0.2.md (m517 sovereign). What m625 adds here is a patient-advocate-facing reading layer.


How to read this evidence (advocate orientation, ≤ 5 minutes)


What this demo will not say (anti-drift · per 01_materials_cache/C2_m625_anti_drift_manifesto.md)

If an advocate reads any of the above into this demo, that is a failure of this demo and should be filed under `_ops/BLOCKED_LOG.md` for next-round revision.

Cross-domain transferability declaration (per W6.3)

The TMU-A pattern with K4.1 = (1, 1, 0) in m517 CARD01 (chronic pain) looks similar at the K4.1-bit level to m610 i_case_cancer_150 (BRCA1/2 breast cancer, TMU-A synthetic-lethality, also K4.1 (1,1,0)). This does not mean the two conditions share underlying biology. transferability_pct: a same K4.1 bit pattern is necessary, not sufficient, for cross-domain Roll transfer; the underlying X-structures (brain network vs. tumor-cell genome) are categorically distinct. m620 verification ladder (m620 exec dirs) is the path to a quantitative transferability score; no such score is asserted by m625 v0.1.


Falsifying prediction (per W6.5 + Roll EPP-3)

The current evidence pattern, as Roll-formalized in m517 CARD01, would be falsified by either of:

Both paths are open. Advocates and skeptics are invited to attempt either.

Attack surface entries (per 05_docs/M625_ATTACK_SURFACE_v0.1.md)

The audit run on this demo is recorded in `_ops/SELF_AUDIT_LATEST.json` after each `python3 -m 02_audit.audit --self-audit` invocation.

Ferry target (per W6.6)

Frontmatter `ferry_target: m511`. Actual payload generation is deferred to v0.2 (per `05_docs/M625_FERRY_TARGETS.md`).

Honest verdict (per W6.5)

- Patient-advocate reading layer cooked over m517 CARD01 Tu 2020 attractor. - K4.1 (1,1,0) declaration referenced by spec section. - 3 attack-surface entries (AS-001, AS-006, AS-010) linked. - Cross-domain bit-pattern observation flagged as necessary-but-not-sufficient (per W6.3). - Falsifying prediction stated with two re-audit paths. - Plain-language community version of this reading layer (lower reading level · v0.2). - Cross-condition synthesis across CARD01 (Tu 2020) + CARD06 (VGAIT) + CARD08 (Wu 2025) for the advocate (deferred to v0.2 after CARD08 cooking · see Demo 006). - Live advocate walkthrough (deferred to v0.2 owner-led session per m517 "请教 NOT 展示" doctrine). - The Tu 2020 source is classified as `training_data_recall · TODO_unverified` because m517 itself labels the underlying anchor as drafted-not-signed (m517 self-reported readiness from `01_materials_cache/A5_m517_neuro_anchor.md` is mid-band, not yet signed). Live PubMed verify is open work for m517 v0.4+, not for m625. - The K4.1 (1,1,0) bit-pattern coincidence with m610 i_case_cancer_150 (BRCA1/2 breast) is observational, not derivational; m620 verification is the path to a substantive cross-domain claim. - No quantitative effect-size claim is made for chronic-pain intervention; this is by design (m517 W7-N + m625 W6 anti-marketing) and may frustrate advocates expecting numbers. - *"Where is the trial number?"* — m625 does not host trial data. m517's outbound `06_m590_neuro_claim_seeds/SEED_PACK_v0.3.md` contains many seeds with NCT/PMID anchors at training_data_recall tier; live verify is m517 v0.4+. - *"Why no plain English?"* — v0.1 reading layer is researcher-readable; v0.2 will produce a plain-language variant. Filed under "待办". - *"How is this different from a wellness blog?"* — a wellness blog claims a `cure`. This demo declares `K4.1 = (1,1,0)`, states the falsifying prediction in machine-checkable terms, and exposes the attack surface. A wellness blog does none of these. - *"Why CARD01 and not the others?"* — CARD01 is the deepest cooked card in m517 v0.3.0 with a clean TMU-A classification. CARD06 (VGAIT) and CARD08 (Wu 2025 cross-condition) are anchored in adjacent demos (Demo 006 covers Wu 2025).