← 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: regulator · domain: rare · tier: 1
ferry target: m560 · fixture id: DEMO-008
self-audit grade: A

i_demo_008 · regulator × rare · audit framework cross-mapping

Why a regulator (or regulator-adjacent reviewer) would come to evidence.x1000.ai

A FDA / EMA / NMPA-adjacent reviewer evaluating new modalities (in-vivo CD19 platforms, n=1 rare-disease n-of-1, RNA gene-writing) reads about Roll-formalized evidence patterns and asks: how does this map to existing review frameworks? Pain points (see 05_docs/M625_PERSONAS.md):

m625 does not advise on any specific submission. **m625 shows that millennium audit V1.1's 4-layer structure has a structural analog with FDA's 4-layer review process (informational, not prescriptive)**, and that NCNU-5 + W7-N can serve as a sponsor self-audit pattern.

This is not regulatory advice. This is not a regulatory submission template. (See "What this demo will not say".)


The Roll-formalized object (anchored on m604 千年审计 V1.1)

FieldValue
Upstream standardm604 千年审计 V1.1 (m604 sovereign · /data/projects/m604_RollDeep/01_standards/ and 04_audit_reports/)
Domainrare / cross-domain (informational mapping)
Audit structure4-layer (Roll Kernel Consistency / Vocabulary Freeze / Evidence Protocol / Structural Integrity) — see 01_materials_cache/A2_m604_millennium_audit_v11.md
Hard constraintsNCNU-5 (m604) + W7-N (m517) + m610 hard-veto (5 families + 5 extensions) — 17 hard constraints total
Industrial gates8 (per 01_materials_cache/C5_m625_industrial_audit_gate_v01.md)
Forbidden vocab freezeper 09_walls/forbidden_vocabulary.yml · m604 NCNU lexicon authoritative

How a regulator reviewer should read this evidence (≤ 5 minutes)

- Layer 1 (Roll Kernel Consistency) ↔ regulator-side "primary endpoint and trial design integrity" - Layer 2 (Vocabulary Freeze) ↔ regulator-side "labeling and claim language review" - Layer 3 (Evidence Protocol) ↔ regulator-side "evidence quality + corroboration" - Layer 4 (Structural Integrity) ↔ regulator-side "cross-program consistency review" The analogy is *structural*, not *operational*. A regulator does NOT outsource review to a Roll engine. (NCNU P_1)

Cross-domain transferability declaration (per W6.3)

The 4-layer audit structure is m604-sovereign and was designed for cross-domain Roll evidence (cancer / neuro / longevity / autism / neurodegen / CKD / rare). Cross-mapping to FDA / EMA / NMPA review processes is structural-analog only. transferability_pct: not quantified; the analogy is offered as informational reference, not as a substitutable framework.


What this demo will not say (anti-drift)


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

The structural-analog claim would be falsified by either of:

Both paths are open. Regulators and sponsors are invited to challenge.

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


Ferry target (per W6.6)

Frontmatter `ferry_target: m560`.

Honest verdict (per W6.5)

- *"You're claiming Roll equals FDA review."* — No. Structural-analog is read above with explicit informational framing. The point is not equivalence; the point is sponsor self-audit pattern transfer. - *"NCNU-5 is too narrow."* — Open finding. v0.3 expansion target. - *"This is a regulatory affairs pitch."* — No. m625 does not pitch regulatory adoption. The demo exists to help reviewers and sponsors *think* about the analogy, not to advocate it.