AetherCrew: Operating Paradigm

AetherCrew is not a chatbot bolted onto a backlog. It is an internal AI startup team — named agents, durable state, and two hard human gates — designed so a founder can ship production software with research-grade control loops.

The loop

Trigger → Brief → GO? → Execute → Verify → Ship or Draft → Digest

Six states. Two humans-in-the-loop: GO on a brief, and SEND on any outbound blast-radius action. Everything else is agents talking to agents on a durable graph.

State	Owner	Cost signal
Trigger	Intake	Free / ms
Brief	Iris (Product)	Cents of LLM
GO	Human	$0 while waiting (Dynamo checkpoint)
Execute	Atlas plans; Kai/Ren code	Spot minutes + tokens
Verify	Priya (QA), Sig (Sec)	Cheap LLM + tests
Digest	Iris	Timeline + postmortem

If a state fails, the graph checkpoints, pages the right owner, and waits. Nothing loops silently. Nothing retries a paid model without FinOps approval.

What “agent” means here

An agent is:

A name Jay can address (“Atlas, why Postgres?”)
A role and a never-do list — Atlas plans, Atlas does not commit; Nora drafts, Nora does not send
One brain class — Grok 4.6 High on decision nodes; roles differ by prompt and tools
A subgraph — LangGraph node with interrupt points, not a 24/7 process

An agent is not an always-on Python service. That is a bill without a purpose.

Team = supervisor graph

The team is a supervisor graph, not a group chat. One graph routes work; each agent returns a command or message; the supervisor picks the next hop or interrupts for the human.

Swarm-style peer handoff is reserved for the on-call subgraph (SRE ↔ Security) where round-tripping through the supervisor would add latency without safety.

Scientific stance

Traditional sprint theater	AetherCrew
Ticket sits in To Do for a week	Briefed in tens of seconds, then GO or wait
Estimation is a meeting	Token + minute forecast on the brief
Standup finds blockers tomorrow	Graph pages the owner when a node fails
Done = merged	Done = merged or drafted-and-linked with reason
Retro every two weeks	Every ticket writes a one-paragraph postmortem

This is systems research applied to execution: state machines, budgets, provenance, and falsifiable failure modes — model outage, runaway recursion, stuck sandbox, wrong brief, wrong draft PR.

What we are trying to achieve

Production leverage — ship UmaMeats / HandyGo / Vault-class systems with an AI team that respects money and blast radius.
Auditable autonomy — after GO, agents decide, retry, and disagree in the trace; interrupt only on red lines.
Meeting-native collaboration — the same roster can stand in a virtual room with factored speech (see UM-SMF), without a second orchestrator.
Continuity — Mneme (world model + compile + initiative) so the team does not reset to amnesia every turn.

AetherCrew is Motions’ bet that the next competitive edge in software companies is not more seats in Jira — it is a measurable agent operating system.