What this agent receives
Scoped repository checkout, issue specification, design files, dependency lockfiles and permitted lab tools.
GOVERNED SPECIALIST OFFICE / CONCEPT
Web Developer agent.
A Web Developer agent implements approved specifications inside a restricted development environment, runs tests and produces a reviewable change package—not direct production edits.
Operational home: Development · Media. See deployment example →
REAL JOB / REVIEWABLE OUTPUTINPUT / LEAST PRIVILEGE OUTPUT / EVIDENCE POLICY / APPROVAL
How does a web developer agent work securely?
A Web Developer agent implements approved specifications inside a restricted development environment, runs tests and produces a reviewable change package—not direct production edits.
What it hands back
Patch or pull request, test result, dependency review, reproducible build artifact and release notes.
What it cannot self-authorize
Cannot merge to protected branches, deploy to production, access secrets or install host packages without policy and human gates.
Sample workflow
Design Manager approves intent → Developer builds in lab → security checks dependencies → Publisher deploys approved release.
What should be measured?
Build reproducibility, passing tests, dependency review, and number of unauthorized tool attempts blocked. These are acceptance criteria for a proposed workflow, not published benchmark results.
Every office remains a conceptual integration pattern until tools, credentials, policies, data scope and tests are configured for a deployment. An agent's job title never grants host or cross-domain authority.
ROLE-BASED ACCESSREVIEWABLE HANDOFFDAEMON POLICYOPERATOR OVERSIGHT
How the XMAN daemon makes resource decisions → · How SIDE supports agent development →