← All work
AI · agentsConcept · design stage

multi-agent-web-build

A designed, not-yet-built LangGraph team of specialist agents meant to turn a Next.js + Payload + GSAP template into a finished, production-grade site.

Role
System design
Status
Concept · design stage
Stack
Python · LangGraph · hybrid RAG · Omniroute gateway · Next.js · Payload CMS · GSAP
Links
AdamMostofi/multi-agent-web-build ↗
Architect: Plan → UI/UX: Brief → Coder: Edits → Reviewer: Gate → Editor: Applyblocking issues → reviseHybrid RAG tool · dense + BM25 → RRF → rerank · books + official docs (GSAP, Payload, Tailwind, SEO)01 · ArchitectPlanbuild plan · GA402 · UI/UXBrieftokens · motion03 · CoderEditsJSON write/replace04 · ReviewerGateapprove or block05 · EditorApplypath-guarded writes

A linear LangGraph StateGraph. Every agent can query the hybrid RAG corpus before it writes.

Status, up front

This is a concept. The architecture, agent roles and repository layout are designed, and the plumbing is sketched out, but it isn’t fully implemented. It’s here because the design shows how I think about orchestration.

The idea

Building a site for a small business repeats the same steps every time: plan, design brief, code, review, apply. The idea is to hand those steps to a team of specialist agents running in a controlled pipeline, all grounded in real documentation rather than model memory.

Design decisions

  • The graph is the router. A linear LangGraph StateGraph (architect → ui/ux → coder → reviewer → editor). Each node is a plain (state) -> dict function.
  • Models by tier, not by name. Every agent calls one OpenAI-compatible gateway (Omniroute) with a tier (orchestrator, coder or cheap). Swapping models is a one-line .env change.
  • Hybrid RAG as a tool. Dense embeddings plus BM25, fused with RRF and reranked by a cross-encoder. The strategy comes from compliance-rag. Chunks carry a breadcrumb, so retrieved context knows where it came from.
  • Edits are data. The coder emits a JSON list of write / replace / delete edits. The editor applies them with a path-traversal guard and reports per-edit results.
  • The template is real. It builds on the Safar site’s stack: Next.js App Router, Payload CMS and GSAP.