What exists now
The public repository contains the validated product contract, architecture, schemas, synthetic examples, safety rules, and a dependency-ordered execution backlog.
Arr Orchestrator defines how a Telegram-operated agent can diagnose, plan, apply, and verify bounded changes across Sonarr, Radarr, Prowlarr, download clients, and media servers.
The public repository contains the validated product contract, architecture, schemas, synthetic examples, safety rules, and a dependency-ordered execution backlog.
Service adapters and remote mutations remain deliberately unimplemented until their bounded Go tasks are claimed, built, and verified.
One media outcome often crosses several applications, credentials, paths, categories, profiles, and queues. A green API response alone does not prove the stack works.
Telegram instruction becomes doctor, reviewable plan, bounded apply, end-to-end verification, and concise evidence rather than an opaque chain of dashboard clicks.
Real API keys, host inventories, media titles, download history, and household configuration stay outside Git. Synthetic fixtures are the only public deployment examples.
The project adds an inspectable control plane around existing services. It does not replace Sonarr, Radarr, Prowlarr, a downloader, or a media server.
A successful service response is intermediate evidence, not completion. Verification must follow the requested outcome across queues, paths, permissions, imports, and the final media surface before reporting success.
Telegram is intended as the concise human interface, not as hidden authority. Mutations need an explicit plan, bounded scope, available credentials, and enough evidence to fail closed when the environment is ambiguous.
This is a public foundation and execution contract, not a claim that the remote-control adapters are already production-complete.