One name, two real things behind it.
"Engineering coworker" refers to two genuinely different real artifacts in this operator's ecosystem, and this site keeps them explicitly separate rather than blending them into one description: (1) the abstract engineering-coworker Cowork skill -- a TypeScript+Rust implementation peer in a 7-coworker system, living in the sister knowledge-engineering repo's cowork/ chassis -- and (2) the concrete crates/engineering-coworker Rust MCP server in this repo, which actually executes cargo/wrangler/git/D1 operations on the developer's real Mac.
4 rows grounded in the live anthropic-skills:engineering-coworker SKILL.md content -- its queue/mailbox pattern, hard invariants, and AgentOutcome contract.
1 row plus 6 tool rows grounded in this repo's own CLAUDE.md, describing crates/engineering-coworker -- a real, compiled Rust MCP server, not prose.
2 rows for the two real surfaces that run this role: macos__desktop_cowork__engineering_coworker and cloud__docker_mcp__engineering_coworker.
The taxonomy, live
All 14 rows are live in this Worker's own D1 database (engineering_role_facts). Browse the board → or hit the JSON API.
What is real vs. what is not
Real: all 14 seed rows, each citing an exact source -- either the live SKILL.md content read via the Skill tool this session, or this repo's own CLAUDE.md, both actually read before writing these rows. Not yet built: no write-gated POST endpoint (read-only catalog for now -- see README.md); no dogfood contract on subagentcontracts.com yet. See the concept page for the full distinction.