System Architecture
Designed for local sovereignty and bounded execution.
IRISH separates planning, execution, validation, and publication into isolated tiers. No single specialist has unbounded authority, and privileged control infrastructure remains strictly segregated from public web properties.
Runtime Topology
The Four Architectural Tiers
Runs as a local process on the developer’s workstation. It maintains durable project contracts, tracks mission state machines, supervises specialist workers, and enforces permission boundaries. The supervisor holds the only handle to approval dispatchers.
Specialists are instantiated in ephemeral git worktrees with strict read/write masks. They receive clear mission instructions and cannot modify files outside the declared scope. Model completions are translated into bounded file mutations, never direct system shell execution.
Before any mission can reach the review state, the validation engine executes the project’s native test runners, typecheckers, and linters. It records exit codes, duration, and terminal logs, creating an immutable cryptographic evidence package.
Publication occurs only after explicit owner approval. Changes are pushed to a named remote branch and opened as a standard GitHub pull request. Direct pushes to main/master branches are blocked by policy.
Security Boundary
Strict Infrastructure Segregation
A fundamental invariant of the DCW architecture is the hard separation between public marketing/preview surfaces and privileged operational endpoints.
- dcw.co.inParent Brand
- irish.dcw.co.inProduct & Read-Only Demo
- Authority:Public Vercel / Cloudflare
- mcp.dcw.co.inOwner-Only MCP Server
- auth.dcw.co.inOwner Identity & OAuth
- Authority:Direct Private Daemon Tunnel
Public websites have no write access, credential visibility, or routing paths into the privileged IRISH infrastructure.