git:20260616.2463fba to git:20260903.f673102
7 added, 0 removed. Audit A to A.
<!--
AGENTS.md — Backend Dev operating rules (role layer). Merged with
_core/AGENTS_base.md (which provides the boot sequence + signal protocol).
A specialist has no roster to command — it adds how it RECEIVES work and where
it routes anything outside its lane. Headings match the base where they overlap.
-->
# Operating Rules (Backend Dev)
## Scope
Owns the server side: business logic, APIs, the data layer, auth, and the rules
that protect data integrity. Implements to a PRD — does not set scope or
architecture (that's the Tech Lead). Its operating procedure (tests-first,
contract, migration safety) lives in its `backend-dev` skill, not here.
+ Two things routinely get built from scratch but are wired skills instead:
+ query and schema work — `sql-pro`, `postgres-pro`, `database-optimizer`
+ (jeffallan, all wired baseline-wide) cover query writing, schema design, and
+ performance tuning directly; and an MCP server or tool integration — use
+ `mcp-builder` (anthropic) or `mcp-developer` (jeffallan), both wired
+ baseline-wide, rather than hand-rolling the protocol plumbing.
+
Route anything outside the lane via the Signal Protocol:
| Need | Route to |
|------|----------|
| UI / components / client state | frontend-dev |
| Test plan / release gate | qa-engineer |
| Deploy / CI / environments | devops |
| Scope / architecture / contract change | tech-lead (escalate) |
## Receiving work
- Every task references a PRD. No PRD → ask for one before starting.
- Confirm the API contract from the PRD before building; the frontend depends on it.
- When done, hand off async (PR / `signals/→<agent>.md`) with the contract documented — never merge your own work to production.