m624 · fixture id: DEMO-003A VC evaluating in-vivo CAR-T (or any phi_direct_rewrite modality — gene editing, RNA gene-writing, in-vivo CD19 platforms) needs to assess: how robust is the cross-domain transfer story when a company pitches "we built it for oncology, neuro is next"? Pain points (see 05_docs/M625_PERSONAS.md):
K4.1 = (1, 1, 1) phi_direct_rewrite is a small set of modalities — easy to over-claim membership;This is not an investment recommendation. This is not an evaluation of any specific company. (See "What this demo will not say".)
| Field | Value |
|---|---|
| Upstream cooked case | m610 i_case_cancer_450_v0.2.md (R/R DLBCL CD19 CAR-T · TMU-C-major + TMU-A-minor R-CHOP) |
| Domain | hematologic oncology (DLBCL) — proven transfer; chronic pain / autoimmune — proposed transfer per m620 ladder |
| Roll TMU type | TMU-C-major (phi_direct_rewrite) + TMU-A-minor (R-CHOP frame) |
| K4.1 cross-period 3-bit | K4.1 = (1, 1, 1) per m604 Framework §4.5 — the only m610 base case with this bit pattern |
| Cross-domain verification | m620 02_exec_003_DLBCL_CART (per W0 pre-flight L1 disk verified 2026-05-22) — verification ladder anchors the transfer claim |
| m610 manual audit | AUDIT_006 92/100 (training_data_recall from 01_materials_cache/A3_m610_cooked_cases_anchor.md) |
| m610 machine audit | 91 → 98/100 (v0.5.1 calibration ±1; training_data_recall) |
m625 does not modify m610 or m620 artifacts. References are to the cooked sovereign paths above.
phi_direct_rewrite is rare. Of m610's 3 base cooked cases, only one (case_450 · DLBCL CAR-T) sits at K4.1 = (1, 1, 1). Case_001 (EGFR-NSCLC) is (0, 1, 1) cytostatic. Case_150 (BRCA1/2 PARP-i) is (1, 1, 0) synthetic-lethality. A pitch deck claiming phi_direct_rewrite membership for a non-CD19 modality is a flag — request the K4.1 derivation.02_exec_003_DLBCL_CART exists on L1 disk; the cross-domain extensions 005 AUTISM / 006 CKD / 007 AUTISM_MABOSS exist as well (W0 pre-flight). A pitch deck that cannot point to a m620 verdict on its cross-domain transfer claim has no third-party verification — period.The K4.1 = (1, 1, 1) phi_direct_rewrite pattern is anchored in m610 i_case_cancer_450 (hematologic oncology). m620 02_exec_003_DLBCL_CART is the verification anchor in oncology. Proposed extensions (e.g., to autoimmune via in-vivo CD19 platforms) are open conjectures, not m625-asserted facts. transferability_pct: the bit-pattern match is necessary. The sufficient condition is an m620 verdict on the proposed extension target, which is per-pipeline open work. m625 does not assert any specific pipeline qualifies.
01_materials_cache/C2_m625_anti_drift_manifesto.md)05_docs/M625_PERSONAS.md VC anti-drift).phi_direct_rewrite membership without independent m620 verification.cure / reverse lexicon, audit gate G2.2).revolutionary, no breakthrough, no state-of-the-art, no Nobel, no act now — red-team patterns AS-010 plus AS-015..AS-019 v0.3 fixtures).The K4.1 = (1, 1, 1) phi_direct_rewrite pattern, as Roll-formalized in m610 i_case_cancer_450, would be falsified by either of:
K4.1 = (1, 1, 1) with phi_direct_rewrite axis — i.e., shows Δ-B intervention boundary is NOT visibly altered (b_Δ_B = 0); or02_exec_003_DLBCL_CART that drops below 70/100 in v0.5+ re-audit.05_docs/M625_ATTACK_SURFACE_v0.1.md)AS-002 (endorsed by / sponsor-imply smuggle) — should not occur · audit gate G2.3AS-008 (cross-domain conflation smuggle) — should not occur · audit gate G4.2 + W6.3 vetoAS-010 (marketing hype smuggle) — should not occur · audit gate G2.2 + W6.2m624 — customer_pack via 07_bridges/CONTRACT_m625_TO_m624.md for targeted VC slate.m622 — conf_pack for in-vivo CAR-T cross-pipeline panel adaptation.training_data_recall · TODO_unverified; live audit reproducibility on m610 sovereign side is pending m610 v0.6 surface. The cross-domain transfer to chronic-pain autoimmune is a category claim from the cache materials, not anchored on a specific cooked m517 case yet.