Architecture map
Done whenOne diagram of components and data flow, and one of the main path, each with its editable source.
You asked how we see this project getting done and which technologies are involved. Here is the full picture.
AgentSquad is a multi-agent platform running in a private beta. We are looking for an architect who reads the code, works out how it really behaves, and explains it clearly to two audiences: engineers, and people who will never read code.
So the technologies are already chosen. What we want from you is understanding, judgment and clear explanation.
Every request follows the same main path. Tracing this path through the code is the heart of the work. Switch the view to see the two ways we need it explained.
Someone asks for something, by chat or by voice.
Chat or voice input (Deepgram) reaches the Hono API. The request belongs to exactly one workspace.
The system plans the work as a set of steps and the order between them.
An orchestrator turns the request into a dependency graph of steps, a DAG, from a versioned template.
Each step is a known task, such as research, analysis, writing or video.
Each node runs a versioned operation from a catalog. Run state and an append-only event log live in Postgres; Inngest schedules the workers.
Some steps stop and wait for a person to approve before the work goes on.
Gate nodes pause the run until an authorized person decides. The wait is durable: it survives restarts and is recorded.
A finished piece of work comes back: a brief, a report, a video.
Outputs are stored per workspace. Row-level security in Postgres keeps each customer's data apart.
This is what you would be reading. It is one TypeScript monorepo.
You will not add, replace or configure any of these. Use whatever you like to read code and draw diagrams. We only ask that each diagram comes with an editable source file.
This is our starting point, not a rule. If you would run it differently, tell us how.
We sign the NDA, you get read-only access, and I walk you through the product and the repository layout.
You trace the main path end to end in the code and draft the architecture map: components, data flow, where state lives and where people step in.
We review the draft map together, to catch wrong assumptions before you start writing.
You write the two versions of the document and the honest assessment.
You present the architecture in a recorded call, and we close open questions.
Done whenOne diagram of components and data flow, and one of the main path, each with its editable source.
Done whenA new engineer can check every claim against the code, because each one points to the files behind it.
Done whenA client or investor understands what the platform does and why it can be trusted, without any jargon.
Done whenIt says plainly what is solid, what is risky and what you would simplify. Blunt is better than polite here.
Done whenA call of about an hour walks through the map, and we keep the recording.
If this fits what you do, reply with these three things and we will set up a first call: