MC Verifier Registry

Actors in this list are permitted to mark H-priority tasks as done even when they are not the task owner.

MC #107143 (CEO directive 2026-08-14): alem is REMOVED from this registry as a routed/default verifier. "ready_for_review je bullshit — ko to treba da odradi review (ja)? Ne. ... Nikad ja i nikad ready na review da mene čeka." alem retains full owner-prerogative override — via mc.js done --force --reason "<text>" and the CEO-attestation force-approve/force-deny flow (A13/B7, HMAC-verified) — but that is an explicit, authenticated CEO ACTION each time, never a default assignment or an unconditional bypass.

Allowed Verifiers

john
proveo
validator
flowforge
codecraft
securion
codex-reviewer — automated cross-vendor reviewer (OpenAI/Codex via pi CLI OAuth, MC #107143 D3)
gemini-reviewer — automated cross-vendor reviewer (Google/Gemini API, MC #107143 D3)

How to Add a Verifier

Add a line in the "Allowed Verifiers" section: - \actor-name``
Commit the file (~/system/rules/mc-verifiers.md) and sync to BookStack.
No code change needed — mc.js reads this file at runtime.

Gate Logic

When mc.js done <id> --actor <X> is called on an H-priority task:

If <X> is in the Allowed Verifiers list — actor check passes.
If <X> is the task owner AND not in the list — gate blocks.
--force --reason "<text>" overrides the actor check + logs FORCED_COMPLETION (this remains available to any actor, including alem, as an explicit, audited owner-prerogative override — never a silent/default bypass).

Evidence Requirements (ZAKON PI2 Check 5)

For H-priority tasks with category in [frontend, backend, devops, deploy, infra], at least one of the following must exist before done is accepted:

docs/evidence/<task-id>/verification.json
docs/evidence/<task-id>/ directory with at least 1 file
task.dod_evidence set in DB (via mc.js ready <id> "notes")
Absolute path to existing file referenced in the outcome message

Override: --force --reason "<text>" logs FORCED_COMPLETION and bypasses the evidence gate.