Doop is treated as a design workspace and MCP-connected tool. It does not grant execution authority, financial authority, credential authority, publication authority, or security-offensive authority.
generate UI concepts and implementation-ready HTML/CSS artifacts;
review accessibility, layout, responsive behavior, design-system consistency and visual QA;
stream bounded design work through an authenticated MCP connection;
preserve attribution/evidence for agent-produced design changes.
Denied by default
autonomous publication to production;
handling secrets in canvas content;
browser-side credentials;
financial operations;
privilege escalation;
unrestricted external network access;
autonomous offensive security activity;
treating MCP connection as execution approval.
Preferred integration mode
Self-host Doop in a dedicated long-running Node runtime with persistent PostgreSQL and WebSocket support, or use the vendor-hosted service only after explicit account authorization.
Connect agents through Doop's MCP OAuth flow or an equivalent authenticated MCP boundary.
Keep model/API credentials server-side.
Disable unsupported ChatGPT-subscription proxying for production use; prefer direct MCP clients or supported provider/API paths.
Route consequential actions through HANTER governance and Approval Gateway.
Fleet usage
Creative/UI agents: primary users.
Other NCA: may request/review artifacts when mission scope requires it.
ORION: advisory coordination only.
HANTER: command center and policy authority boundary; no provider runtime becomes a competing command authority.