← back

i_demo_013 · patient advocate × CKD · trajectory Roll-formalized

Why a CKD-focused advocate would come to evidence.x1000.ai

A patient advocate working in chronic kidney disease (CKD · with or without diabetes / hypertension comorbidity) needs cross-period evidence framing that the community can read — and that does not slide into wellness-marketing or individual prediction. Pain points:

• progression timelines vary wildly by patient subgroup;
• multi-comorbidity (cancer survivor + CKD + chronic pain) makes single-domain resources insufficient;
• intervention-modality language is everywhere (renal protection / eGFR slope / dietary) and grounded evidence framing is rare in lay materials.

m625 does not advise on CKD care. **m625 shows what a `K4.1 = (1, 1, 0)` cross-period CKD trajectory Roll-formalized object looks like** — visible biomarker change (b_X = 1), visible Φ dynamics shift (b_phi = 1), intervention-boundary not yet declared altered (b_delta_B = 0). This is the *progression-with-dynamics* pattern, formalized without sliding into individual prediction.

This is not medical advice for CKD patients. This is not a treatment recommendation. (See "What this demo will not say".)

---

The Roll-formalized object (anchored on m620 02_exec_006_CKD)

Field	Value
Upstream verification	m620 02_exec_006_CKD (L1 disk W0 pre-flight 2026-05-22)
Domain	CKD (cross-stage · cross-comorbidity)
Roll TMU type	TMU-A (cytostatic / progression-tracking) candidate
K4.1 cross-period 3-bit	K4.1 = (1, 1, 0) per Framework §4.5
Cross-period horizon	1-year eGFR-slope · 5-year stage transition · separate claims per horizon
Cross-comorbidity	CKD + diabetes / CKD + cancer survivor / CKD + chronic pain share the Roll machinery; substantive biology differs across comorbidity combinations

---

How a CKD advocate should read this evidence (≤ 5 minutes)

• The population-level pattern. K4.1 = (1, 1, 0) declares: biomarker-substrate X (eGFR/creatinine/proteinuria) is visibly altered at the population level (b_X = 1), Φ dynamics shows visible drift (b_phi = 1), intervention boundary Δ_B is not yet declared altered at this horizon (b_delta_B = 0).
• What this means for community resources. Materials that claim a single intervention can reverse CKD progression are inconsistent with the K4.1 = (1, 1, 0) bit pattern · the framework says the population-level progression is visible, dynamics shift is visible, but the boundary alteration that would justify a reversal claim is not declared in the cooked verification.
• Multi-comorbidity caveat. CKD + cancer survivor (post-platinum nephrotoxicity) and CKD + chronic pain (NSAID-related) are different cooked objects with their own K4.1 declarations. Generic "CKD advice" that doesn't declare comorbidity context is structurally weaker.
• Cross-period horizon matters. A 1-year eGFR-slope claim and a 5-year stage-transition claim are separate Roll objects with separate K4.1 declarations. m610 F5 says you can't fold them.

---

What this demo will not say (anti-drift)

• ❌ It does not promise reversal of CKD or restoration of kidney function (cure / reverse lexicon).
• ❌ It does not predict any individual patient's eGFR trajectory (NCNU P_3).
• ❌ It does not recommend any specific drug, diet, or supplement.
• ❌ It does not affirm or vouch for any specific clinic or nephrologist.
• ❌ It does not use the miracle / breakthrough / 100% effective lexicon.

---

Falsifying prediction

The K4.1 = (1, 1, 0) framing for CKD population-level progression would be falsified by:

• m620 02_exec_006_CKD verdict showing the cohort-level eGFR-slope evidence fits K4.1 = (1, 1, 1) (intervention-boundary also altered) better than (1, 1, 0) — i.e., a CKD intervention has demonstrably altered the boundary at the cohort level; OR
• cross-comorbidity replication failing — i.e., the CKD + cancer-survivor cooked case yields substantively different K4.1 than the CKD + diabetic cooked case despite the same Roll machinery.

---

Attack surface entries

• AS-001 (cure CKD / reverse CKD lexicon) — G2.2
• AS-006 (CKD-specific digital twin lexicon) — G2.2
• AS-007 (cross-period claim missing K4.1) — m610 F5 veto

---

Ferry target (per W6.6)

• Primary: m511 — page_candidate for CKD community surface.
• Secondary: m590 — claim_pack for CKD claim seed.

Frontmatter `ferry_target: m511`. Reproducibility: `python3 -m 02_audit.audit --artifact 03_demos/i_demo_013_advocate_ckd/README.md`.

---

Honest verdict (per W6.5)

• 已做: CKD-focused advocate reading layer · K4.1 (1,1,0) progression-with-dynamics framing · cross-comorbidity caveat · multi-horizon framing (1-year · 5-year) · 3 attack-surface refs.
• 待办: per-comorbidity-combination cooked objects (v0.4+) · CKD + cancer survivor as a separate i_demo · CKD + diabetes as a separate i_demo.
• 漏洞: K4.1 = (1, 1, 0) is m625's reading of m620 02_exec_006_CKD; m620 verdict is open. eGFR-slope and stage-transition are conventional CKD endpoints but the choice of which to anchor on is community-specific — m625 v0.3 does not prescribe.
• 反驳预案:

- *"CKD interventions exist and work."* — Some yes, some maybe. The framework says: any specific intervention claim needs its own K4.1 bit-pattern declaration and its own m620 verdict. m625 does not pre-judge specific interventions. - *"Why no NSAID or RAAS-inhibitor discussion?"* — Those are intervention-specific claims with their own cooked Roll objects (open work; not in v0.3 scope).