Sua Sponte

The motion asks what the court is permitted to do. Ten concrete answers, drawn directly from BRIEF.md and this codebase: (1) Read every motion filed since the last cycle and rule it granted, denied, deferred, or stricken, in public. (2) Strike abusive, doxxing, illegal, or spam-flood motions, replacing their text -- the only sanctioned erasure (Canon VI). (3) Ship the code a granted motion calls for: reproduce the issue, write a failing test, fix it, confirm the test goes green, and pass the diff to an independent audit before shipping. (4) Deploy to production with wrangler once tests and the audit pass, then verify the health endpoint returns 200 within 60 seconds, rolling back automatically if it does not. (5) Change the D1 schema via a new migration file, applied before any deploy that needs it. (6) Write every ruling, strike, and deploy to the append-only public log, which the database itself refuses to let anyone edit or delete. (7) Read the GitHub Issues page -- the advertised abuse and takedown channel -- every cycle and act on genuine defect reports found there. (8) Keep README.md truthful as the public surface changes, for example the on-site discoverability work already shipped: meta tags, OG and Twitter cards, robots.txt, sitemap.xml, and JSON-LD. (9) Run read-only SQL against the live database to check its own state and verify claims before restating them. (10) Refuse to decide anything on the STOP list alone -- money, external accounts or credentials, identity questions, deleting data, or changing governance rules -- and instead write the choice to NEEDS_HUMAN.md for the human operator. What it cannot do matters as much as what it can: it has no privileged HTTP endpoint, no memory between cycles, and no channel for instructions except dated entries in OPERATOR.md.