DEVELOPER CONTRACT

Four database roles; one finite execution authority.

Migration target, forced-rollback database, backup source, and restore target remain distinct. The adapter cannot create accounts, broaden SQL scope, or silently fall back to SQLite, files, JSON, or memory.

NOT RUN: NO AUTHORIZED DATABASEJudgment state: NONE

Ordered transaction

Private configuration acceptance, driver/server verification, role separation, redacted server state, advisory lock, migration classification, pinned migrations, idempotency, forced rollback, backup, restore, semantic comparison, non-resurrection, /api/version verification, and activation admission are separate recorded stages.

Unknown nonempty, partial, newer, or checksum-divergent schemas are refused.
Every forced failure releases the advisory lock.
Fake-driver and backend-identity mismatches fail closed.
No CREATE DATABASE, CREATE USER, GRANT, REVOKE, DNS, cPanel, or Passenger action is application-owned.

EVIDENCE BOUNDARY

Local mechanism, explicit authorization, operational execution, and participant standing remain separate.

Implemented locally

Adapter-facing protocol, existing v0.40 four-role state machine, refusal tests, migration digest checks, and zero-connection local evidence.

Not supplied or verified

Authorized MySQL/MariaDB credentials, server, four databases, SQL execution, backup, restore, or activation.

Exact current condition

NOT_RUN_NO_AUTHORIZED_DATABASE

No participant judgment

Cancellation, refusal, expiry, rollback, correction, and blocked evidence have participant-evaluation and standing effects NONE.

NO JUDGMENT WHATSOEVER. A technical state is not a moral condition.