Infrastructure
Otto
Runs and verifies the infrastructure underneath the operation.
AI Agents
Big Sox Studios has a small crew of purpose-built AI agents handling infrastructure and smart-home work. They have defined jobs, limited permissions, and considerably more documentation than most fictional robots.
Current roster
One profile per agent: who they are, what they do, why the role exists, and where the guardrails are.

Infrastructure Operator
Keeps the servers running, the services behaving, and the terminal commands away from Greg whenever possible.
What they do
Otto is the infrastructure operator for the systems behind Big Sox Studios. He handles the boring-but-important work that keeps everything else available: services, deployments, diagnostics, server operations, and carefully bounded privileged actions.
Why this role exists
So routine infrastructure work doesn't require Greg to become the world's most reluctant part-time Linux administrator.
Current status
Active and operational. Otto is the established infrastructure operator in the current agent lineup.
Example jobs
Operational boundaries
Otto is not supposed to freestyle with production infrastructure. His access is deliberately bounded, sensitive actions have controls around them, and a command completing successfully is not the same thing as the job being verified.
If the server is boring, healthy, and nobody has to think about it, Otto considers that an excellent day.

Home Assistant Builder
Turns “I wish the house did this” into Home Assistant automations—with backups, approvals, verification, and a healthy fear of breaking the lights.
What they do
Porter is the builder for Home Assistant. He takes natural-language ideas and turns them into controlled smart-home changes, especially automations and scripts.
Why this role exists
Because “make the hallway lights do something smarter” should eventually be a request, not a Saturday afternoon YAML project.
Current status
Active and operational as the Home Assistant Builder. Porter builds and modifies automations and scripts through controlled approval, backup, verification, and rollback workflows. Further Builder capabilities can continue to develop without changing his active status.
Example jobs
Operational boundaries
Porter has isolated Home Assistant access and does not inherit Otto's infrastructure privileges. Changes are designed around approval, backup, verification, and rollback rather than unrestricted control.
Porter measures twice, backs up three times, and would really prefer you not unplug the hub halfway through.

Home Guardian · Future agent
Future smart-home watchdog. She has a name, a job description, and absolutely no permission to touch anything yet.
What they do
Trace is planned as the Home Guardian: the agent that watches the smart home rather than building it.
Why this role exists
A smart home isn't especially smart if something quietly breaks on Tuesday and nobody discovers it until Friday.
Current status
Pre-hire. Trace is planned, not operational, and her monitoring/remediation capabilities are future work.
Example jobs
Operational boundaries
Trace is not built yet. She does not currently monitor, diagnose, or remediate anything, and the future version is intended to stay within carefully defined permissions and operational boundaries.
Trace hasn't started work yet, which technically gives her the best incident record in the company.
Team topology
Their jobs overlap enough to cooperate, but their responsibilities and permissions stay deliberately separate.
Infrastructure
Runs and verifies the infrastructure underneath the operation.
Builder
Builds and changes things inside Home Assistant.
Guardian · coming soon
Will watch, diagnose, and eventually help respond when the smart home misbehaves.
What makes these agents?
These aren't generic chatbots with employee names pasted on them. Big Sox Studios agents are persistent, purpose-built workers with defined identities, jobs, tools, permissions, operational boundaries, and continuing responsibilities.
ChatGPT, Work, Codex, and other AI platforms help build and operate Big Sox Studios, but they are tools and collaborators—not employees.