researchclaw-dedicated-container-oracle-network-topology

AutoResearchClaw is deployed as a dedicated researchclaw Docker container on oracle-network, alongside oracle-hermes, oracle-mirofish, and oracle-graphiti-mcp. This follows the established oracle-* topology pattern and is required for experiment sandboxing isolation — AutoResearchClaw executes generated experiment code which must run in isolation. The container uses the host’s Docker socket for its own experiment sandbox containers. Coupling it inside oracle-hermes would risk dependency conflicts and compromise security isolation.

Related

• autoresearchclaw-must-run-in-dedicated-container-for-sandbox
• autoresearchclaw-requires-dedicated-container-for-sandbox
• researchclaw-must-run-in-dedicated-container-for-sandboxing
• researchclaw-must-run-in-dedicated-container-for-experiment
• autoresearchclaw-dedicated-container-not-inside-hermes
• researchclaw-dedicated-container-not-inside-hermes
• oracle-network-container-topology-pattern
• researchclaw-requires-docker-isolation-not-host-install
• docker-iptables-bypasses-ufw-docker-user-chain-required
• docker-iptables-bypasses-ufw-requires-docker-user-chain