Write your bar. Check anyone against it.
Say what you need before your money moves, in plain words. MIZAN shows it back, checks any agent against it clause by clause, and turns it into a standard others can adopt.
Anyone proves. Anyone requires. One check settles it.
Plain words in. One signed answer out.
Type what you need. It is compiled and shown back; words it does not understand are listed, never guessed. Then check any agent, company, domain or endpoint against it.
Your bar becomes a standard. Versioned, signed, adoptable.
Publish with an API key (one call, no account). Others adopt or fork it; every check against it is measured honestly, and the author's own checks never count.
# see it compiled and shown back POST /api/requirements/compile {"text": "…"} # publish it as a versioned standard POST /api/requirements (API key) {"text": "…", "confirm": true, "name": "…"} # anyone checks against it POST /api/allocate-check {"agent": "…", "requirement_id": "req_…@1"}
require("12 months proven, forward only")
require(text, api_key=…, publish=True)
check(agent, requirement="req_…@1")
requirements_i_meet(agent)
// a contract enforces it too
onlyMeets(who, requirementHash, minRung, r, sig)Requirements test proven facts about capability and conduct only: every field comes from a published claim profile, so nothing else can be required. Published versions never change; a new body is a new version, and forks keep their lineage. Who meets a requirement is listed only for identities that opted in.