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.
Challenge m625
m625's value, if any, equals the value of its attack surface. If the attack surface is fake — handpicked easy fixtures, no false-positive penalty, no public BLOCKED log — the framework is fake.
So here is the open intake.
Nine attack families
Vocabulary freeze · find a marketing word that should be forbidden but is not. (See 09_walls/forbidden_vocabulary.yml.)
NCNU-5 · find a phrasing of clinical-decision / individual-prediction / moral-attribution the audit misses.
W7-N (cross-domain expert) · find an expert-collaboration imply the audit misses (especially domains where the expert list is currently empty).
m610 hard-veto · find a cross-period claim where K4.1 is dropped or mis-declared.
W6.3 conflation · find a cross-domain claim where transferability is missing but the demo passes audit.
Honest verdict (W6.5) · find a Tier-1 demo where any of 已做 / 待办 / 漏洞 / 反驳预案 is missing or evasive.
Attack-surface coverage · find a customer-failure mode NOT covered by any AS-NNN fixture.
Audit pipeline · find a bug in 02_audit/audit.py — gate that fails to fire on a violation OR fires on a false positive.
Cross-binding drift · find a case where spec ↔ code ↔ test do not match — see 05_docs/SELF_AUDIT_BENCHMARK_v0.1.md.
How to file
v1.0 intake form posts directly to the m625 backend (FastAPI /api/challenge · sqlite-backed store at _ops/challenge_store.sqlite · md trail at _ops/CHALLENGE_INTAKE.md). Three viable channels remain open:
Pull request against this repository · m625 reviews and either accepts (records in _ops/BLOCKED_LOG.md) or rejects (records reason in _ops/ITER_FINDINGS.md).
Email the owner contact in 01_materials_cache/C0_m625_project_identity_card.md.
Form below (live · posts to /api/challenge · returns submission ID).
Recent challenges (live · sqlite-backed)
loading …
What happens next
m625 reproduces locally.
Result recorded in _ops/BLOCKED_LOG.md (timestamped, append-only, version-controlled).
Either the rule or the artifact is revised within the next wave.
Either way the finding is credited in _ops/ITER_FINDINGS.md · rejection comes with a written reason.