- Postgres queue, the default: background jobs need no broker.
?queue=postgreson/my/object-createand/my/object-update(orapp_state.func_producer(queue="postgres", client_postgres=...)) adds a row to the new tablequeue_joband returns its id;venv/bin/python -m script.consumer_postgres <channel>runs it. Jobs are taken withFOR UPDATE SKIP LOCKEDinside a transaction held until the job is finished, so several consumers can share a channel and a killed one leaves nothing stuck;LISTEN/NOTIFYwakes consumers at once; retries wait inrun_at; a job failed afterconfig_queue_retry_maxretries stays withstatus2 and its error. Redis, RabbitMQ, Kafka and Celery are unchanged (docs/queue.md). - Rules are checked by code:
script.checkhas arulesstep that fails a project on: a secret in code or docs, Postgres through anything but asyncpg,.envmissing from.gitignore, a pool or SDK client opened infunction_extend/orrouter_extend/(scripts may open their own), a role or permission check inrouter_extend/(config_apidoes it). Each break is named with its file and line. The report-only score is nowstandard Defaults x/y(no Rules part). - Front end is Defaults only:
AGENTS.mdanddocs/frontend.mdsay plainly that every front-end point is a suggestion a page may follow or not; the two former front-end Rules (standalone page storage and escaping, keeping the login alive) are Defaults. Only how Atom serves pages and the route paths they call stay enforced.