Provision and revoke a developer

Steps

Use bin/developer locally as the authorized operator. Select the environment explicitly. Passwords are piped from a secure source, not arguments, copied examples, or web registration.

secure password-manager output → APP_ENV=DEV php bin/developer add your.username
APP_ENV=DEV php bin/developer revoke your.username
APP_ENV=DEV php bin/developer allow-ai your.username
APP_ENV=DEV php bin/developer deny-ai your.username

The first line describes a pipeline; replace its left side with your password manager's secure output command. No default username/password is included. AI permission alone does not activate a provider.

Verify

Account records contain native password hashes, not plaintext. Revocation and AI permission changes are rechecked on subsequent requests. Recovery/password reset and enterprise SSO/MFA are separate identity projects, not silently implemented features.

Editorial provenance

Source: resources/guides/developer-account.md. Source SHA-256: ab5df9a63b2e00c60d4600a372cc7590af8d80545bb19964655157cd2479867f.

Knowledge-base application source; editorial checkpoint 2026-10-20. See candidate status and adoption boundary.