Where Arthas is heading
We ship in phases. Each one lands a working capability the studio uses every day before we start the next. Here is the route.
Phase 1 · Bot foundation
ShippedA secure, team-scoped Telegram bot with access control, concurrency limits, session tracking and the first real Claude-Code task runner.
Phase 2 · Agent army
ShippedFifteen specialist agents, each with its own knowledge base and writing slot. Orchestrator routes, specialists execute, state stays consistent.
Phase 3 · Deliverable skills
ShippedTwenty deliverable-grade skills — invoices, dashboards, decks, contract review, research, debugging protocols — all callable from any agent.
Phase 4 · Forgelab preview platform
ShippedA password-gated HTML preview host on a hardened VPS. TLS 1.3, a web application firewall, a sandboxed runtime under a service account, full audit trail.
Phase 5 · Bot ↔ Forgelab integration
ShippedEvery HTML deliverable is automatically published to Forgelab. Arthas returns a share card with the URL, the one-time password, and the expiry — alongside the local PDF, as a fail-soft side channel.
Phase 6 · Monitoring & alerting
In progressHealth checks on every moving part, with alerts that arrive before the studio notices a problem.
- Uptime monitoring on public endpoints
- Quota awareness and pre-warning thresholds
- Latency and error-rate dashboards
- On-call-style paging for hard failures
Phase 7 · Backup automation
NextDaily, encrypted, versioned backups with verified restore drills.
- Scheduled archives of orchestrator state
- Off-site retention with rotation
- Quarterly restore rehearsals
Phase 8 · Docs & handoff
PlannedOperator runbook, onboarding path for new team members, and a clean docset so any DawnForge hand can take over Arthas on day one.
Beyond the roadmap
Once the plumbing is boring and the studio trusts the machine, we start widening the army. The wishlist — not promises, just where the team wants to take Arthas next: