[{"data":1,"prerenderedAt":1877},["ShallowReactive",2],{"docs-nav":3,"docs-article-engineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fworkflow-visualizer":797},[4,17,27,44,55,67,75,82,94,106,114,122,129,135,144,153,161,169,177,189,202,211,218,229,240,248,260,268,276,286,296,305,314,323,331,337,343,350,356,364,371,378,383,393,401,410,415,422,432,439,444,451,458,462,467,475,487,499,509,516,525,533,539,545,551,557,563,567,579,593,603,614,621,626,633,640,646,653,658,665,673,678,686,692,699,704,710,721,730,740,747,753,761,767,776,782,791],{"path":5,"title":6,"description":7,"group":8,"section":6,"order":9,"tags":10,"lastUpdated":16},"\u002Fagents\u002Fagentic-crm","Agentic CRM","Research brief and build plan for an AgencyCore agentic CRM layer, rendered as an interactive page — the core operating loop, the target architecture, the typed-tool risk gateway, the proposed-actions review queue, and the four-slice MVP.","Agents",0,[11,12,13,14,15],"crm","agents","ai","architecture","research","2026-06-12",{"path":18,"title":19,"description":20,"group":8,"section":21,"order":22,"tags":23,"lastUpdated":26},"\u002Fagents\u002Fchat","Chat agent","High-level system design of the AgencyCore chat agent — core components, data flow, and the two abstractions that hold it together.","Reference",1,[12,14,24,25],"chat","system-design","2026-05-13",{"path":28,"title":29,"description":30,"group":8,"section":31,"order":32,"tags":33,"lastUpdated":43},"\u002Fagents\u002Fcompany-enrichment","Company Enrichment","The company enrichment workflow - a cache-first read in front of the company intelligence database that fills firmographic, contact and technographic facts via a fixed-order provider waterfall, and writes every resolved fact back with provenance so the first org pays once and every later search rides free.","Enrichment",2,[12,34,35,36,37,38,39,40,41,42],"workflow","enrichment","companies","waterfall","cache","intelligence-database","firmographics","provenance","sonar","2026-06-10",{"path":45,"title":46,"description":47,"group":8,"section":48,"order":9,"tags":49,"lastUpdated":54},"\u002Fagents\u002Fcompany-sonar","Company Signals","Signal-first company discovery for marketing agencies, on the Claude Agent SDK, with a global intelligence cache and deterministic composite scoring.","Company Sonar",[12,34,42,50,51,52,35,53,14],"company-search","signals","agent-sdk","scoring","2026-06-08",{"path":56,"title":57,"description":58,"group":8,"section":48,"order":22,"tags":59,"lastUpdated":66},"\u002Fagents\u002Fcompany-sonar\u002Fsignal-monitoring","Company Signals Monitoring","Realtime signal capture layer on top of the data graph. Detects hot events, scores them with a Claude managed agent against each agency's ICP, fans out alerts.",[14,51,60,61,62,63,64,65],"intel","icp","alerts","monitoring","sse","managed-agents","2026-06-09",{"path":68,"title":69,"description":70,"group":8,"section":71,"order":22,"tags":72,"lastUpdated":74},"\u002Fagents\u002Fconcepts\u002Fchat-agent-design-principles","Designing chat agents","The 2026 playbook for production chat agents that reach into internal systems via tools — context engineering, memory, tool design, when to add complexity.","Concepts",[12,14,24,73],"context-engineering","2026-05-14",{"path":76,"title":77,"description":78,"group":8,"section":71,"order":32,"tags":79,"lastUpdated":74},"\u002Fagents\u002Fconcepts\u002Fsystem-prompt-architecture","System prompt architecture","How to structure a production chat agent system prompt — eight sections, what each one does, and the rules vendors converge on.",[12,80,81],"prompt-engineering","system-prompt",{"path":83,"title":84,"description":85,"group":8,"section":84,"order":9,"tags":86,"lastUpdated":54},"\u002Fagents\u002Fenvoy","Envoy","High-level system design for the AI outreach engine — the sequence step state machine, the human-in-the-loop draft approval gate, multi-source context enrichment, and the inbox sentiment flow, rendered as an interactive page.",[12,87,88,89,90,91,92,93,14],"envoy","outreach","sales-engagement","sequences","state-machine","human-in-the-loop","nylas",{"path":95,"title":96,"description":97,"group":8,"section":98,"order":9,"tags":99,"lastUpdated":16},"\u002Fagents\u002Fheadhunter","Headhunter","The AI talent-search pipeline on one page - the production six-step design with its current-title relevance gate, and the 2.0 system design with internal-first waterfall sourcing, a pluggable source registry, automatic entity resolution, and a people intelligence graph that compounds every run.","General Search",[12,34,100,101,14,25,102,37,103,104,105],"headhunter","recruiting","multi-source","entity-resolution","people-intelligence","flywheel",{"path":107,"title":108,"description":109,"group":8,"section":21,"order":32,"tags":110,"lastUpdated":113},"\u002Fagents\u002Fpaperclip","Paperclip","Architecture deep dive into the Paperclip orchestration system.",[12,14,111,112],"orchestration","paperclip","2026-04-20",{"path":115,"title":116,"description":117,"group":8,"section":31,"order":22,"tags":118,"lastUpdated":16},"\u002Fagents\u002Fpeople-enrichment","People Enrichment","The people enrichment workflow - a cache-first read in front of the people intelligence database that fills profile, contact and employment facts via a fixed-order provider waterfall, keyed on the LinkedIn URL, and writes every resolved fact back with provenance so the first org pays once and every later search rides free. The fill step Headhunter and People Signals both call.",[12,34,35,119,37,38,39,120,41,100,121],"people","linkedin","people-sonar",{"path":123,"title":124,"description":125,"group":8,"section":126,"order":9,"tags":127,"lastUpdated":54},"\u002Fagents\u002Fpeople-sonar","People Signals","Signal-first people discovery for marketing agencies, built on the headhunter pipeline, with a composite score weighted by signal strength, source reputation, recency, and ICP fit.","People Sonar",[12,34,121,128,51,100,35,53,14],"people-search",{"path":130,"title":131,"description":132,"group":8,"section":126,"order":22,"tags":133,"lastUpdated":54},"\u002Fagents\u002Fpeople-sonar\u002Fpeople-signal-monitoring","People Signals Monitoring","Forward-looking design for the push layer that tracks known people - champions, past contacts, target-company decision-makers - and fires a warm lead the moment they change jobs, get promoted, or their company has an event.",[14,51,60,119,63,134],"warm-leads",{"path":136,"title":137,"description":138,"group":139,"section":140,"order":22,"tags":141,"lastUpdated":143},"\u002Fengineering\u002Fguides\u002Fagent-execution-stack","The Agent Execution Stack","Durable workflows over pluggable agent backends — how AgencyCore runs AI agents on Inngest over a webhook-driven Claude Managed Agents backend.","Engineering","Guides",[12,142,14,25],"inngest","2026-06-25",{"path":145,"title":146,"description":147,"group":139,"section":140,"order":9,"tags":148,"lastUpdated":143},"\u002Fengineering\u002Fguides\u002Fagent-runtime","Agent runtime","How AgencyCore runs AI agents on a provider-neutral runtime — the abstraction layer that lets us swap the agent backend, with Claude managed agents as the current provider.",[12,149,14,150,151,152,25],"runtime","anthropic","claude","providers",{"path":154,"title":155,"description":156,"group":139,"section":21,"order":157,"tags":158,"lastUpdated":160},"\u002Fengineering\u002Freference\u002Fagno-to-agent-sdk-migration","Agno → Claude Agent SDK migration","System-design spec for moving the ac-python-api workflow engine off Agno onto Anthropic's Claude Agent SDK \u002F Managed Agents, tiered by control-flow shape.",10,[12,14,159,52,65],"migration","2026-06-06",{"path":162,"title":163,"description":164,"group":139,"section":21,"order":22,"tags":165,"lastUpdated":54},"\u002Fengineering\u002Freference\u002Fcloudflare-agent-sandbox","Cloudflare agent sandbox","Cloudflare's Workers-based agent platform, evaluated as an alternative sandbox for our Agno workflows.",[12,166,167,168,159],"sandbox","cloudflare","workers",{"path":170,"title":171,"description":172,"group":139,"section":21,"order":32,"tags":173,"lastUpdated":176},"\u002Fengineering\u002Freference\u002Fvirtual-filesystem-rag","Virtual filesystem for AI assistants","How ChromaFs provides AI agents with structured file access.",[12,174,14,175],"rag","chromafs","2026-04-18",{"path":178,"title":179,"description":180,"group":139,"section":181,"order":182,"tags":183,"lastUpdated":188},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fcapabilities\u002Fstate-and-knowledge","State and knowledge","What a run may know. One deterministic context builder over application state, knowledge and memory, one owner for every fact, and memory that is written through a tool.","Agentic platform",11,[184,185,186,11,187],"context","memory","knowledge","pgvector","2026-08-31",{"path":190,"title":191,"description":192,"group":139,"section":181,"order":157,"tags":193,"lastUpdated":201},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fcapabilities\u002Ftools-and-integrations","Tools and integrations","A tool is the one way an agent reaches the world. AgencyCore owns the model facing contract, the invoke path, the credentials and the result boundary.",[194,195,196,197,198,199,200],"tools","integrations","mcp","agno","policy","security","idempotency","2026-09-04",{"path":203,"title":204,"description":205,"group":139,"section":181,"order":22,"tags":206,"lastUpdated":210},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fcontract","Platform contract","One platform behind chat, interactive channels, triggers, approvals and background runs, with one Agno runtime, one tool layer, one state layer, and three cross-cutting planes.",[12,14,197,142,194,207,149,208,198,209],"skills","channels","observability","2026-09-02",{"path":212,"title":181,"description":213,"group":139,"section":214,"order":22,"tags":215,"lastUpdated":201},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform","The whole agentic platform on one page - who starts a run, the one boundary every run passes, how the work executes, and what comes back.","System design",[12,14,216,197,142,217,198],"overview","runs",{"path":219,"title":220,"description":221,"group":139,"section":181,"order":222,"tags":223,"lastUpdated":228},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Finterfaces\u002Fagent-access","Agent access (CLI and MCP)","How an outside AI agent reaches AgencyCore. The ac CLI works today as a user seat. An MCP server is planned and not designed.",6,[224,196,12,151,225,226,227],"cli","access","auth","todo","2026-08-18",{"path":230,"title":231,"description":232,"group":139,"section":181,"order":233,"tags":234,"lastUpdated":239},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Finterfaces\u002Fchannel-gateway","Channel gateway","The only layer that knows both an interactive channel and the platform. One message shape converges inbound, one intent shape diverges outbound, and no model call happens here.",3,[208,235,236,237,238,199],"slack","web","identity","sessions","2026-08-30",{"path":241,"title":242,"description":243,"group":139,"section":181,"order":244,"tags":245,"lastUpdated":210},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Finterfaces\u002Ffront-door","Front door","The conversational control layer. It turns a request into one structured decision, then deterministic application code answers or hands work to RunManager.",4,[246,247,197,184,198,217],"front-door","routing",{"path":249,"title":250,"description":251,"group":139,"section":181,"order":32,"tags":252,"lastUpdated":259},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Finterfaces\u002Fsurfaces","Surfaces","Every product surface and its API contract. Web chat goes through the gateway; every schema-native surface calls the domain API.",[253,254,24,255,256,257,258,217,64],"surfaces","api","approvals","prospects","saved-searches","builder","2026-09-03",{"path":261,"title":262,"description":263,"group":139,"section":181,"order":264,"tags":265,"lastUpdated":188},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Finterfaces\u002Ftriggers","Triggers","A Run with no person. Every producer emits one Event, matching is deterministic, and dispatch reuses RunManager, Policy and Inngest.",5,[266,267,142,200],"triggers","events",{"path":269,"title":270,"description":271,"group":139,"section":181,"order":272,"tags":273,"lastUpdated":259},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fplanes\u002Fidempotency","Idempotency","One durable PostgreSQL key service prevents duplicate effects and freezes mutable input before selected Run starts. A Run start is guarded by a unique index on the Run row.",14,[200,217,194,274,275],"webhooks","reliability",{"path":277,"title":278,"description":279,"group":139,"section":181,"order":280,"tags":281,"lastUpdated":285},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fplanes\u002Fobservability-and-operations","Observability and operations","One run row, one span tree and one usage meter. Sentry reports system failure; AgencyCore spans explain what the agent did.",13,[209,217,282,283,64,284],"spans","usage","sentry","2026-08-26",{"path":287,"title":288,"description":289,"group":139,"section":181,"order":290,"tags":291,"lastUpdated":295},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fplanes\u002Fpolicy-and-governance","Policy and governance","One deterministic plane answers may this happen, at three checkpoints, with one grant model, one approval model and one decision log.",12,[198,292,255,293,294],"permissions","limits","governance","2026-08-25",{"path":297,"title":6,"description":298,"group":139,"section":299,"order":22,"tags":300,"lastUpdated":210},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fagentic-crm","The AgencyCore CRM loop for turning signals and discovery into qualified organization prospects, CRM relationships and outreach.","Agentic products",[11,301,51,302,256,35,303,304,87],"lead-generation","intelligence","signals-search","email-sequence",{"path":306,"title":307,"description":308,"group":139,"section":299,"order":264,"tags":309,"lastUpdated":188},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fbuilder-chat","Front door builder chat","Conversational authoring for organization-specific Agent and Workflow definitions, entered through the normal Front Door and backed by the existing DefinitionService.",[310,311,246,12,312,313,198],"authoring","definitions","workflows","templates",{"path":315,"title":316,"description":317,"group":139,"section":181,"order":318,"tags":319,"lastUpdated":201},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fcapability-contracts","Company, People and Signals contracts","The five Phase 7 product capabilities, their bounded inputs, stable references, permissions and results.",21,[320,321,119,51,322],"capabilities","company","contracts",{"path":324,"title":325,"description":326,"group":139,"section":181,"order":327,"tags":328,"lastUpdated":330},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fcapability-scenarios","Capability design scenarios","Normal, failure and recovery cases for the Phase 7 capability contracts, with implementation owners.",22,[320,329,321,119,51],"validation","2026-09-05",{"path":332,"title":333,"description":334,"group":139,"section":299,"order":233,"tags":335,"lastUpdated":210},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Femail-sequence","Email sequence workflow","Envoy durable outreach for one or many people, with fresh context, approvals, reply waits, follow-ups and Nylas transport.",[336,87,34,142,93,255],"email",{"path":338,"title":339,"description":340,"group":139,"section":299,"order":244,"tags":341,"lastUpdated":188},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fgeneral-chat","Front door general chat","The default conversational answer path for AgencyCore. It answers from supplied context, cites what it used, asks when context is insufficient, and delegates real work through the normal Front Door.",[24,246,186,184,247,342],"citations",{"path":344,"title":345,"description":346,"group":139,"section":299,"order":222,"tags":347,"lastUpdated":188},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fhuman-review","Human review inbox","One product page for every agentic action that is paused because a person must authorize an exact proposal. It is a view over the shared approval primitive, not a second review system.",[348,255,349,198,12],"human-review","inbox",{"path":351,"title":352,"description":353,"group":139,"section":299,"order":32,"tags":354,"lastUpdated":259},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fsignals-search","Signals Search","One bounded discovery workflow that finds companies, verifies signals, finds relevant people, and produces evidence-backed organization prospects without prematurely creating CRM records.",[303,355,36,119,51,302,256,11,35],"discovery",{"path":357,"title":358,"description":359,"group":139,"section":299,"order":360,"tags":361,"lastUpdated":188},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fworkflow-visualizer","Workflow visualizer","One constrained workflow graph, reused to author a draft, read a published definition, and watch a Run. Build mode edits the draft; run mode overlays Run and span state on the frozen snapshot.",7,[312,362,258,311,217,282,363,255],"visualizer","graph",{"path":365,"title":366,"description":367,"group":139,"section":181,"order":368,"tags":369,"lastUpdated":201},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fruntime\u002Fdefinitions","Runtime definitions","Editable drafts, one published configuration per definition, template forks, deterministic validation, and the Run snapshot that keeps in flight work stable.",8,[149,311,329,370],"publishing",{"path":372,"title":373,"description":374,"group":139,"section":181,"order":375,"tags":376,"lastUpdated":259},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fruntime\u002Fexecution","Runtime execution","The Run record, the Inngest step boundaries, agent segments, workflow nodes, approvals, cancellation, failure handling and live events.",9,[149,217,197,142,255,377,64],"cancellation",{"path":379,"title":380,"description":381,"group":139,"section":181,"order":360,"tags":382,"lastUpdated":285},"\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fruntime","Agentic runtime","One Run contract, one Agno agent runtime, one deterministic workflow model, and the component boundaries that keep the framework replaceable.",[149,217,197,312,207,142],{"path":384,"title":385,"description":386,"group":139,"section":387,"order":244,"tags":388,"lastUpdated":392},"\u002Fengineering\u002Fsystem-design\u002Fmission-control\u002Fcompany-context","Company context","L3. Company state, knowledge and memory are three different things. One deterministic builder turns them into one brief.","Mission Control",[389,390,186,185,184,391,11],"mission-control","company-state","retrieval","2026-08-12",{"path":394,"title":395,"description":396,"group":139,"section":387,"order":22,"tags":397,"lastUpdated":392},"\u002Fengineering\u002Fsystem-design\u002Fmission-control\u002Fexperience","Experience","L6. Where a person observes and controls the company, and the one rule that keeps the UI out of the business.",[389,398,399,255,400],"ui","control-plane","activity",{"path":402,"title":403,"description":404,"group":139,"section":387,"order":222,"tags":405,"lastUpdated":392},"\u002Fengineering\u002Fsystem-design\u002Fmission-control\u002Ffoundation","Foundation","L1. Generic infrastructure with no business logic in it. The test is that another product could run on it unchanged.",[389,406,407,408,267,409,226,209],"infrastructure","database","queue","storage",{"path":411,"title":387,"description":412,"group":139,"section":214,"order":233,"tags":413,"lastUpdated":392},"\u002Fengineering\u002Fsystem-design\u002Fmission-control","The internal Company OS. Six layers and one policy plane put a person in control of company state and of autonomous execution.",[389,414,14,12,312,198,399],"company-os",{"path":416,"title":417,"description":418,"group":139,"section":387,"order":32,"tags":419,"lastUpdated":392},"\u002Fengineering\u002Fsystem-design\u002Fmission-control\u002Fintelligence","Intelligence","L5. The agent is the primitive. A skill is how it works, a tool is how it reaches the world, and the two are never the same thing.",[389,12,207,420,421],"planning","reasoning",{"path":423,"title":424,"description":425,"group":139,"section":387,"order":368,"tags":426,"lastUpdated":392},"\u002Fengineering\u002Fsystem-design\u002Fmission-control\u002Fmetrics-and-connectors","Metrics and connectors","A worked example across every layer. Three vendors, one metric pipeline, three views, and the rule that decides what we store.",[389,427,195,428,429,284,430,431],"metrics","stripe","posthog","ingest","dashboards",{"path":433,"title":434,"description":435,"group":139,"section":387,"order":233,"tags":436,"lastUpdated":392},"\u002Fengineering\u002Fsystem-design\u002Fmission-control\u002Forchestration","Orchestration","L4. Workflow, run, step, trigger and event. Five nouns that turn a decision into durable execution.",[389,312,217,266,267,437,438],"durability","retry",{"path":440,"title":288,"description":441,"group":139,"section":387,"order":360,"tags":442,"lastUpdated":392},"\u002Fengineering\u002Fsystem-design\u002Fmission-control\u002Fpolicy-and-governance","A plane, not a layer. One place decides what an agent may do, under what conditions, and how much. Human approval is one of its three answers.",[389,198,294,255,292,293,443],"audit",{"path":445,"title":191,"description":446,"group":139,"section":387,"order":264,"tags":447,"lastUpdated":392},"\u002Fengineering\u002Fsystem-design\u002Fmission-control\u002Ftools-and-integrations","L2. One contract for every capability. The tool is the only route to the world, and it is where policy, audit and tenancy meet.",[389,194,195,448,449,450],"adapters","registry","credentials",{"path":452,"title":453,"description":454,"group":139,"section":455,"order":22,"tags":456,"lastUpdated":210},"\u002Fengineering\u002Fsystem-design\u002Fworkflows\u002Fcompany-search","Company search","Implementation notes for company.search. Search resolves and gates company identities; enrichment is a separate capability.","Workflows",[321,457,142,42],"search",{"path":459,"title":31,"description":460,"group":139,"section":455,"order":233,"tags":461,"lastUpdated":210},"\u002Fengineering\u002Fsystem-design\u002Fworkflows\u002Fenrichment","Reusable company and people enrichment workflows with canonical Intelligence write-back, existing tier freshness and bounded asynchronous email.",[35,321,119,142],{"path":463,"title":464,"description":465,"group":139,"section":455,"order":32,"tags":466,"lastUpdated":259},"\u002Fengineering\u002Fsystem-design\u002Fworkflows\u002Fpeople-search","People search","Implementation notes for people.search. Bounded company scope and persona gates return selectable person identities without enrichment.",[119,457,142,100],{"path":468,"title":469,"description":470,"group":139,"section":455,"order":244,"tags":471,"lastUpdated":474},"\u002Fengineering\u002Fsystem-design\u002Fworkflows\u002Fsignals-search","Signals search","Superseded. The earlier on-demand buying-signal search component, kept as a record of the design that the agentic platform Signals Search workflow replaces.",[51,12,142,472,473],"intelligence-databases","superseded","2026-08-28",{"path":476,"title":477,"description":478,"group":479,"section":480,"order":481,"tags":482,"lastUpdated":66},"\u002Flearnings\u002Fagentic-sdlc","The agentic SDLC","How AI agents move from autocomplete to owning the loop across the software lifecycle, and why that shifts the bottleneck from coding to verification.","Learnings",null,30,[12,483,484,485,486],"sdlc","engineering","verification","review",{"path":488,"title":489,"description":490,"group":479,"section":480,"order":491,"tags":492,"lastUpdated":498},"\u002Flearnings\u002Fagi-to-asi","From AGI to ASI","What lies beyond human-level AI. The four technological pathways from AGI to artificial superintelligence, the formal ceiling that bounds them, and the six bottlenecks that could stall the climb - distilled from the DeepMind report.",50,[493,494,495,496,497],"ai-futures","asi","agi","scaling","recursive-self-improvement","2026-06-19",{"path":500,"title":501,"description":502,"group":479,"section":480,"order":503,"tags":504,"lastUpdated":66},"\u002Flearnings\u002Fai-native-company-playbook","AI native company playbook","Why AI should be the operating system your company runs on, not a tool it uses, and the concrete practices that follow - closed loops, a queryable org, software factories, and token maxing.",40,[505,506,12,507,508],"ai-native","company-building","gtm","founders",{"path":510,"title":511,"description":512,"group":479,"section":480,"order":157,"tags":513,"lastUpdated":54},"\u002Flearnings\u002Fbuying-intent-signals","Buying intent signals","How buyers leak their intent before they ever fill in a form, and how to read those signals before the window closes.",[514,51,507,515],"intent","sales",{"path":517,"title":518,"description":519,"group":479,"section":480,"order":520,"tags":521,"lastUpdated":54},"\u002Flearnings\u002Fcold-outbound-system","Cold outbound system","A high-level study of an open-source 29-skill cold email system, organized into five sequential tracks from ICP to iteration.",20,[522,523,507,524],"outbound","cold-email","systems",{"path":526,"title":527,"description":528,"group":479,"section":480,"order":529,"tags":530,"lastUpdated":532},"\u002Flearnings\u002Fswan-gtm-skills-architecture","Swan GTM skills architecture","A research note on Swan AI's foundations and maps model for GTM agents, with ASCII diagrams and ideas AgencyCore can borrow.",60,[507,12,73,531,14],"swan","2026-07-01",{"path":534,"title":535,"description":536,"group":387,"section":480,"order":272,"tags":537,"lastUpdated":43},"\u002Fmission-control\u002Fciops-agent","CIOps agent","High-level system architecture and design notes for the Mission Control CIOps agent.",[389,12,538,14],"ciops",{"path":540,"title":541,"description":542,"group":387,"section":480,"order":182,"tags":543,"lastUpdated":43},"\u002Fmission-control\u002Fcostops-agent","CostOps agent","High-level system architecture and design notes for the Mission Control CostOps agent.",[389,12,544,14],"finops",{"path":546,"title":547,"description":548,"group":387,"section":480,"order":520,"tags":549,"lastUpdated":54},"\u002Fmission-control\u002Fdashboard","Dashboard","The Mission Control product UI - a dark cockpit with a fleet-nav rail, company-state grid, a working escalation queue, live ledger and a global kill switch.",[389,12,550,398],"dashboard",{"path":552,"title":553,"description":554,"group":387,"section":480,"order":280,"tags":555,"lastUpdated":43},"\u002Fmission-control\u002Fproduct-analytics-agent","ProductAnalytics agent","High-level system architecture and design notes for the Mission Control ProductAnalytics agent.",[389,12,556,14],"product-analytics",{"path":558,"title":559,"description":560,"group":387,"section":480,"order":290,"tags":561,"lastUpdated":43},"\u002Fmission-control\u002Frevenueops-agent","RevenueOps agent","High-level system architecture and design notes for the Mission Control RevenueOps agent.",[389,12,562,14],"revops",{"path":564,"title":214,"description":565,"group":387,"section":480,"order":157,"tags":566,"lastUpdated":54},"\u002Fmission-control\u002Fsystem-design","One screen for the whole company, watched by a guardrailed fleet of ops agents that explain, propose, act and learn overnight.",[389,12,544,14],{"path":568,"title":569,"description":570,"group":571,"section":480,"order":32,"tags":572,"lastUpdated":578},"\u002Fproduct-design\u002Fonboarding-flow","Onboarding flow","Product design for the signup wizard and how TAM building folds into it. Analyzes the flow today (account, profile, company), the gap (no ICP, empty dashboard), and the integration of a new \"who you sell to\" ICP step plus a build-and-reveal screen that lands the user on a populated, ranked list.","Product Design",[573,61,574,575,576,577],"onboarding","tam","activation","ux","user-journey","2026-06-11",{"path":580,"title":581,"description":582,"group":571,"section":480,"order":233,"tags":583,"lastUpdated":592},"\u002Fproduct-design\u002Fpricing-entitlements","Pricing tiers, entitlements and usage credits","Specification for subscription tiers with gated platform access: composable plan entitlements, a unified usage-credit currency, plan-sourced limits, per-module trials and a two-ticket delivery plan built on the Stripe billing foundation. Written for discussion; the Linear document is the canonical copy with ticket links.",[584,585,586,587,588,589,590,591],"pricing","entitlements","billing","credits","subscriptions","plans","seats","trials","2026-07-06",{"path":594,"title":595,"description":596,"group":571,"section":480,"order":233,"tags":597,"lastUpdated":578},"\u002Fproduct-design\u002Fsales-signals-ux","Designing Signals","Product design for the sales-signals experience in ac-frontend: the 14-type taxonomy and its color system, the anatomy of a signal card across four densities, the 0-10 lead score scale, the origin tag (sonar pull vs proactive push), the seven surfaces where signals render (launchpad, sonar app, company detail, timeline, activities, data layer, Envoy), and the interaction rules that keep them consistent.",[51,576,598,11,42,599,600,601,602],"design-system","lead-score","origin","pull","push",{"path":604,"title":605,"description":606,"group":607,"section":608,"order":244,"tags":609,"lastUpdated":43},"\u002Fproprietary-data\u002Fcrm\u002Factivities","Activities","Deep dive on crm_activities, the interaction + task log of the CRM — where it is served from, how a row is born and read, and its full schema, relationships and rules.","Proprietary data","CRM",[11,610,611,612,613],"activities","tasks","data-model","schema",{"path":615,"title":616,"description":617,"group":607,"section":608,"order":264,"tags":618,"lastUpdated":43},"\u002Fproprietary-data\u002Fcrm\u002Fcommunications","Communications","Deep dive on crm_communications and crm_communication_events, the unified email\u002Fcall\u002Fmessage log and its per-message engagement tracking — where it is served from, the outbound message lifecycle, and the full schema, relationships and rules.",[11,619,336,620,612],"communications","engagement",{"path":622,"title":623,"description":624,"group":607,"section":608,"order":22,"tags":625,"lastUpdated":43},"\u002Fproprietary-data\u002Fcrm\u002Fcompanies","Companies","Deep dive on crm_companies, the account record at the centre of the CRM — where it is served from, how a row is born and read, and its full schema, relationships and rules.",[11,36,612,613,14],{"path":627,"title":628,"description":629,"group":607,"section":608,"order":233,"tags":630,"lastUpdated":43},"\u002Fproprietary-data\u002Fcrm\u002Fdeals","Deals","Deep dive on the deal pipeline — crm_deals, crm_pipeline_stages and crm_pipeline_config. Where it is served from, the life of a deal, and its full schema, relationships and rules.",[11,631,632,612,613],"deals","pipeline",{"path":634,"title":635,"description":636,"group":607,"section":608,"order":222,"tags":637,"lastUpdated":43},"\u002Fproprietary-data\u002Fcrm\u002Flists","Lists","Deep dive on crm_lists and crm_list_members, the static or dynamic member collections of the CRM — where they are served from, how a list and its members come to be and are read, and their schema, relationships and rules.",[11,638,639,612,613],"lists","segments",{"path":641,"title":642,"description":643,"group":607,"section":608,"order":32,"tags":644,"lastUpdated":43},"\u002Fproprietary-data\u002Fcrm\u002Fpeople","People","Deep dive on crm_people, the contact record of the CRM — where it is served from, how a row is born and read, and its full schema, relationships and rules.",[11,119,645,612,613],"contacts",{"path":647,"title":648,"description":649,"group":607,"section":608,"order":368,"tags":650,"lastUpdated":43},"\u002Fproprietary-data\u002Fcrm\u002Fsaved-filters","Saved filters","Deep dive on crm_saved_filters, the named reusable filter snapshots over the company, person and signal list views — where it is served from, how a saved view is born and applied, and its full schema, relationships and rules.",[11,651,652,612,613],"saved-filters","views",{"path":654,"title":655,"description":656,"group":607,"section":608,"order":360,"tags":657,"lastUpdated":578},"\u002Fproprietary-data\u002Fcrm\u002Fsignals","Signals","Deep dive on the signals tables - signals, company_signals and person_signals, the CRM's sales-intelligence layer. Where signals are served from, how one is born and attached, and the full schema, relationships and rules.",[11,51,302,612,613],{"path":659,"title":660,"description":661,"group":607,"section":662,"order":22,"tags":663,"lastUpdated":43},"\u002Fproprietary-data\u002Fintelligence-databases\u002Fcompany-intelligence-database","Company Intelligence Database","Decided architecture for ENG-669, the cross-org company intelligence layer that acts as a read-through cache in front of enrichment providers, with public-facts-only privacy and provenance-tracked write-back.","Intelligence databases",[14,60,36,51,38,664],"eng-669",{"path":666,"title":667,"description":668,"group":607,"section":662,"order":244,"tags":669,"lastUpdated":578},"\u002Fproprietary-data\u002Fintelligence-databases\u002Forg-signal-feed","Org Signal Feed","The per-org activation layer on top of the shared signals store. One immutable intel_signals row fans out to many orgs through scoring (signal-type weight times ICP fit times recency decay) and materializes as ranked, tiered rows in intel_org_signal_feed - the only org-scoped, RLS-per-org table of the signal stack, the door the launchpad, inbox and digest all read through. Signals enter by two ingest classes - a user's sonar pull (ungated) or an automated push (gated by threshold plus an optional competitor-ICP check) - logged in intel_signal_ingests, and each feed row records its origin.",[14,60,51,670,53,671,672,575,430,601,602,600],"feed","decay","rls",{"path":674,"title":675,"description":676,"group":607,"section":662,"order":32,"tags":677,"lastUpdated":578},"\u002Fproprietary-data\u002Fintelligence-databases\u002Fpeople-intelligence-database","People Intelligence Database","Decided architecture for the cross-org people intelligence layer - a read-through cache in front of headhunter research and Hunter email lookups, with LinkedIn-URL identity, append-only employment edges, per-tier freshness stamps on the flat profile, shared intel_sources provenance, unified intel_signals, and a GDPR erasure path.",[14,60,119,51,38,100],{"path":679,"title":680,"description":681,"group":607,"section":662,"order":233,"tags":682,"lastUpdated":578},"\u002Fproprietary-data\u002Fintelligence-databases\u002Fsignals-intelligence-database","Signals Intelligence Database","Decided v1 architecture for the unified signal store - one polymorphic append-only intel_signals table that holds both company and person signals, with a shared taxonomy, source-ranked provenance, an intel_signal_ingests log that records which pipeline found each signal, decay at read time, and a person-to-company rollup so a champion job change surfaces on the company feed.",[14,60,51,683,671,684,670,685,41,601,602],"polymorphic","taxonomy","ingests",{"path":687,"title":688,"description":689,"group":607,"section":480,"order":9,"tags":690,"lastUpdated":16},"\u002Fproprietary-data\u002Foverview","Data Layer Overview","The AgencyCore data layer in one map - the org-scoped CRM plane in production today and the global intelligence plane designed to sit in front of it, with interactive diagrams of both, the end-to-end data flow, freshness and precedence rules, the privacy seam, and the rollout path.",[691,14,60,11,51,38,25,216],"data-layer",{"path":693,"title":694,"description":695,"group":696,"section":480,"order":9,"tags":697,"lastUpdated":54},"\u002Froadmap","Roadmap - June 2026","June 2026 product plan across four themes. The spine is moving our agents onto an isolated sandbox runtime and rebuilding the core agents and workflows on it, then standing up a read-through intelligence data store and shipping the Stripe billing system. Knowledge base, assistant, and credit tracking carry into the July roadmap.","Roadmap",[698,420],"roadmap",{"path":700,"title":701,"description":702,"group":696,"section":480,"order":22,"tags":703,"lastUpdated":54},"\u002Froadmap\u002Fjuly-2026","Roadmap - July 2026","July 2026 product plan across three themes, all carried over from June. Building on June's sandbox runtime, July grounds the agents in a knowledge base, launches the AI chat assistant, and meters every action with per-action credit tracking that reconciles into the Stripe billing system shipped in June.",[698,420],{"path":705,"title":706,"description":707,"group":696,"section":480,"order":32,"tags":708,"lastUpdated":532},"\u002Froadmap\u002Fjune-2026-slides","Roadmap slides - June 2026","Board-review slide deck for the June 2026 product roadmap, rendered directly from the original PPTX in the docs site.",[698,420,709],"slides",{"path":711,"title":712,"description":713,"group":714,"section":8,"order":520,"tags":715,"lastUpdated":16},"\u002Fsymphony\u002Fagents\u002Fdevops-agent","DevOps agent","Interactive design for a Slack-first Symphony DevOps agent that wraps production promotion, rollback, audit, and operational jobs behind policy gates, typed runbooks, and an auditable ledger.","Symphony",[716,235,717,718,719,720],"symphony","devops","production","runbooks","operations",{"path":722,"title":723,"description":724,"group":714,"section":8,"order":157,"tags":725,"lastUpdated":16},"\u002Fsymphony\u002Fagents\u002Foncall-agent","Oncall agent","Interactive design for a Symphony oncall agent that turns Sentry incidents into rich Linear tickets, investigates with Codex, opens fix PRs, and resolves Sentry after merge.",[716,284,726,727,728,729],"linear","oncall","incident-response","codex",{"path":731,"title":732,"description":733,"group":714,"section":734,"order":157,"tags":735,"lastUpdated":16},"\u002Fsymphony\u002Fhousekeeping\u002Fcodex-vacuum","Codex vacuum","Interactive design for the Symphony housekeeping timer that checkpoints and vacuums Codex sqlite stores on the VPS.","Housekeeping",[716,736,737,729,738,739],"timed-jobs","housekeeping","sqlite","vps",{"path":741,"title":742,"description":743,"group":714,"section":734,"order":481,"tags":744,"lastUpdated":16},"\u002Fsymphony\u002Fhousekeeping\u002Fhost-cleanup","Host cleanup","Interactive design for the Symphony housekeeping timer that removes stale \u002Ftmp debris, vacuums the journal, and optionally cleans the apt package cache.",[716,736,737,739,745,746],"disk","cleanup",{"path":748,"title":749,"description":750,"group":714,"section":734,"order":520,"tags":751,"lastUpdated":16},"\u002Fsymphony\u002Fhousekeeping\u002Fworkspace-cleanup","Workspace cleanup","Interactive design for the Symphony housekeeping timer that prunes idle per-issue workspaces after their TTL.",[716,736,737,752,746,739],"workspaces",{"path":754,"title":755,"description":756,"group":714,"section":480,"order":9,"tags":757,"lastUpdated":66},"\u002Fsymphony","Symphony orchestration","How AgencyCore runs OpenAI Symphony as a long-running daemon that turns Linear tickets into isolated, autonomous Codex runs, reviewed by Claude and merged by humans. High-level workflow, system architecture, and the engineer playbook.",[716,729,726,758,111,739,759,760],"claude-review","qa","automation",{"path":762,"title":763,"description":764,"group":714,"section":214,"order":22,"tags":765,"lastUpdated":392},"\u002Fsymphony\u002Fsystem-design\u002Fhigh-level-design","High-level design","The Symphony daemon end to end — the standing agent workforce and its label-routed workflows, then the runtime that polls, dispatches, runs and writes back.",[716,14,111,12,729,726,766],"systemd",{"path":768,"title":769,"description":770,"group":714,"section":771,"order":503,"tags":772,"lastUpdated":16},"\u002Fsymphony\u002Ftimed-jobs\u002Fdaily-security-agent","Daily security agent","Interactive design for a report-only Symphony timed job that reviews the last 24h of commits, scans the system for vulnerabilities, and opens focused follow-up tickets.","Timed jobs",[716,199,736,729,773,774,775],"semgrep","threat-model","ownership",{"path":777,"title":778,"description":779,"group":714,"section":771,"order":481,"tags":780,"lastUpdated":16},"\u002Fsymphony\u002Ftimed-jobs\u002Fdaily-sentry-triage","Daily Sentry triage","Interactive design for the Symphony timed job that performs read-only Sentry triage, deduplicates existing tracked clusters, and creates focused ENG bugs for new actionable errors.",[716,736,284,209,781,726],"triage",{"path":783,"title":784,"description":785,"group":714,"section":771,"order":157,"tags":786,"lastUpdated":16},"\u002Fsymphony\u002Ftimed-jobs\u002Fnightly-local-staging-e2e","Nightly local staging E2E","Interactive design for the Symphony timed job that seeds local Supabase, runs ac-frontend Playwright E2E against the local staging stack, uploads evidence, and cleans artifacts.",[716,736,787,788,789,790],"e2e","playwright","staging","frontend",{"path":792,"title":793,"description":794,"group":714,"section":771,"order":520,"tags":795,"lastUpdated":16},"\u002Fsymphony\u002Ftimed-jobs\u002Fnightly-staging-qa","Nightly staging QA","Interactive design for the Symphony timed job that seeds a staging QA Linear issue, runs an agent-browser crawl, validates feature-map coverage, and files focused follow-up work.",[716,736,789,759,796,726],"agent-browser",{"id":798,"title":358,"body":799,"customComponent":480,"description":359,"extension":1863,"group":139,"lastUpdated":188,"meta":1864,"navigation":1865,"order":360,"path":357,"related":1866,"section":299,"seo":1873,"stem":1874,"tags":1875,"__hash__":1876},"docs\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fworkflow-visualizer.md",{"type":800,"value":801,"toc":1834},"minimark",[802,806,823,831,836,841,844,854,861,865,872,878,889,893,899,1027,1044,1057,1061,1067,1125,1128,1132,1135,1141,1146,1149,1155,1169,1172,1175,1178,1209,1214,1218,1225,1231,1246,1249,1253,1256,1262,1265,1269,1272,1356,1359,1363,1366,1372,1375,1379,1386,1432,1435,1439,1445,1451,1454,1458,1464,1470,1473,1478,1484,1487,1491,1545,1549,1554,1557,1563,1566,1572,1582,1586,1592,1595,1599,1644,1648,1677,1681,1792,1796,1816,1820,1823,1831],[803,804,358],"h1",{"id":805},"workflow-visualizer",[807,808,809,810,814,815,818,819,822],"p",{},"A workflow must look the same when a person ",[811,812,813],"strong",{},"builds it",", ",[811,816,817],{},"reads it",", and ",[811,820,821],{},"watches it run",".",[807,824,825,826,830],{},"The visualizer is one graph component over the workflow definition. Build mode edits ",[827,828,829],"code",{},"draft_config",". Run mode overlays execution state on the snapshot the Run froze. There is no second visualization model for runtime.",[832,833],"doc-diagram",{"caption":834,"name":835},"One picture of a workflow, and the three places a person meets it. The middle band is authoring: only the boxes the runtime can execute may be placed, and a draft cannot run until it is published. The third band is a Run, which keeps its own frozen copy of the workflow, so an old Run always shows what really ran. The strip below it is the whole vocabulary a box can carry while the Run is on.","agentic-products-visualiser",[837,838,840],"h2",{"id":839},"product-goal","Product goal",[807,842,843],{},"One mental model for a workflow:",[845,846,852],"pre",{"className":847,"code":849,"language":850,"meta":851},[848],"language-text","Workflow definition\n        │\n        ▼\n   Workflow graph\n        │\n   ┌────┼───────────┐\n   ▼    ▼           ▼\n build  view        run\n draft  published   live \u002F historical\n","text","",[827,853,849],{"__ignoreMap":851},[807,855,856,857,860],{},"A node means the same thing in all three places. A ",[827,858,859],{},"Company Research Agent"," node is editable in the builder, read-only on the definition page, and status-bearing in a Run.",[837,862,864],{"id":863},"why-this-fits-the-platform","Why this fits the platform",[807,866,867,868,871],{},"The platform already holds every record the graph needs. A workflow is a definition, and a definition is data with a small deterministic vocabulary. A Run freezes an immutable snapshot of ",[827,869,870],{},"published_config"," at start. Execution produces child Runs and spans. The visualizer combines those records and adds none.",[845,873,876],{"className":874,"code":875,"language":850,"meta":851},[848],"build mode\ndraft_config ──> WorkflowGraph ──> DefinitionService ──> validate ──> publish\n\nrun mode\nRun snapshot + Run + child Runs + spans ──> WorkflowGraph\n",[827,877,875],{"__ignoreMap":851},[807,879,880,881,885,886,822],{},"No execution logic belongs in the visualizer. Inngest stays the durable orchestrator, the worker executes the workflow, and the UI renders product state only. See ",[882,883,884],"a",{"href":365},"runtime definitions"," and ",[882,887,888],{"href":372},"runtime execution",[837,890,892],{"id":891},"the-node-vocabulary-is-the-runtimes-unchanged","The node vocabulary is the runtime's, unchanged",[807,894,895,896,898],{},"The visual builder places the eight node types the runtime executes, and nothing else. Two of them are containers. The ",[882,897,149],{"href":379}," owns this table; the visualizer renders it.",[900,901,902,918],"table",{},[903,904,905],"thead",{},[906,907,908,912,915],"tr",{},[909,910,911],"th",{},"Node",[909,913,914],{},"Kind",[909,916,917],{},"What the graph draws",[919,920,921,935,947,960,972,984,1003,1015],"tbody",{},[906,922,923,929,932],{},[924,925,926],"td",{},[827,927,928],{},"sequence",[924,930,931],{},"container",[924,933,934],{},"The ordered relationship between children",[906,936,937,942,944],{},[924,938,939],{},[827,940,941],{},"parallel",[924,943,931],{},[924,945,946],{},"A fixed set of children that run at the same time",[906,948,949,954,957],{},[924,950,951],{},[827,952,953],{},"tool",[924,955,956],{},"step",[924,958,959],{},"One deterministic tool call",[906,961,962,967,969],{},[924,963,964],{},[827,965,966],{},"agent",[924,968,956],{},[924,970,971],{},"One agent as a child Run",[906,973,974,979,981],{},[924,975,976],{},[827,977,978],{},"subworkflow",[924,980,956],{},[924,982,983],{},"One published workflow as a child Run",[906,985,986,991,993],{},[924,987,988],{},[827,989,990],{},"branch",[924,992,956],{},[924,994,995,996,999,1000],{},"One child chosen by the shared ",[827,997,998],{},"ConditionEvaluator",", with a declared ",[827,1001,1002],{},"default",[906,1004,1005,1010,1012],{},[924,1006,1007],{},[827,1008,1009],{},"wait",[924,1011,956],{},[924,1013,1014],{},"A hold for an event or a delay",[906,1016,1017,1022,1024],{},[924,1018,1019],{},[827,1020,1021],{},"approval",[924,1023,956],{},[924,1025,1026],{},"A hold for a person",[807,1028,1029,885,1031,1033,1034,1036,1037,1039,1040,1043],{},[827,1030,1009],{},[827,1032,1021],{}," are two nodes, not one. A ",[827,1035,1009],{}," resumes on an event or a timer. An ",[827,1038,1021],{}," resolves an approval row, and the ",[882,1041,1042],{"href":344},"human review inbox"," is the global queue for it.",[807,1045,1046,1047,1050,1051,1053,1054,1056],{},"This is ",[811,1048,1049],{},"not"," an unrestricted DAG canvas. No code nodes, no loops, no dynamic graph rewriting at run time, no user-defined node types, and no dynamic fan-out node. Fan-out stays inside one ",[827,1052,953],{}," step or one ",[827,1055,966],{}," step, which reports one result, so the shape stays checkable at publish time.",[837,1058,1060],{"id":1059},"three-modes-one-component","Three modes, one component",[845,1062,1065],{"className":1063,"code":1064,"language":850,"meta":851},[848],"\u003CWorkflowGraph\n  definition={definition}\n  mode=\"edit | view | run\"\n  execution={optionalExecutionOverlay}\n\u002F>\n",[827,1066,1064],{"__ignoreMap":851},[900,1068,1069,1082],{},[903,1070,1071],{},[906,1072,1073,1076,1079],{},[909,1074,1075],{},"Surface",[909,1077,1078],{},"Mode",[909,1080,1081],{},"Behavior",[919,1083,1084,1097,1112],{},[906,1085,1086,1089,1094],{},[924,1087,1088],{},"Agent Builder",[924,1090,1091],{},[827,1092,1093],{},"edit",[924,1095,1096],{},"Add, connect, configure, remove and validate nodes on the draft",[906,1098,1099,1102,1107],{},[924,1100,1101],{},"Definition detail",[924,1103,1104],{},[827,1105,1106],{},"view",[924,1108,1109,1110],{},"Read-only picture of ",[827,1111,870],{},[906,1113,1114,1117,1122],{},[924,1115,1116],{},"Run Explorer",[924,1118,1119],{},[827,1120,1121],{},"run",[924,1123,1124],{},"Read-only Run snapshot, with live or historical execution overlaid",[807,1126,1127],{},"Layout and node identity stay stable between modes, so a person never relearns the workflow.",[837,1129,1131],{"id":1130},"build-mode","Build mode",[807,1133,1134],{},"Build mode is a visual editor for the draft. It is not a workflow engine.",[845,1136,1139],{"className":1137,"code":1138,"language":850,"meta":851},[848],"┌─────────────────┐\n│ Find Companies  │ agent\n└────────┬────────┘\n         │\n         ▼\n┌─────────────────┐\n│ Enrich Company  │ agent\n└────────┬────────┘\n         │\n         ▼\n    ┌──────────┐\n    │ Score ≥80│ branch\n    └────┬─────┘\n       \u002F   \\\n     yes    default\n      │      │\n      ▼      ▼\n┌──────────┐ Finish\n│ Review   │ approval\n└────┬─────┘\n     │\n     ▼\n┌─────────────────┐\n│ Email Sequence  │ subworkflow\n└─────────────────┘\n",[827,1140,1138],{"__ignoreMap":851},[1142,1143,1145],"h3",{"id":1144},"node-configuration","Node configuration",[807,1147,1148],{},"Selecting a node opens a side panel. Configuration never sits on the canvas.",[845,1150,1153],{"className":1151,"code":1152,"language":850,"meta":851},[848],"Enrich Company\n\nType      agent\nAgent     Company Research Agent\nInput     company = find_companies.company\nOutput    company_intelligence\n",[827,1154,1152],{"__ignoreMap":851},[807,1156,1157,1158,1160,1161,1164,1165,1168],{},"The editor writes ",[827,1159,829],{}," through ",[827,1162,1163],{},"PATCH \u002Fapi\u002Fv1\u002Fagentic\u002Fdefinitions\u002F{id}\u002Fdraft",", and sends ",[827,1166,1167],{},"expected_updated_at"," on every write. Two people editing one draft is normal, so a stale write is refused rather than merged. The editor never writes execution records and never bypasses validation.",[1142,1170,1171],{"id":329},"Validation",[807,1173,1174],{},"The builder may give immediate client-side guidance. Publishability is decided by the deterministic definition validator, and by nothing in the frontend.",[807,1176,1177],{},"The validator holds:",[1179,1180,1181,1185,1188,1191,1200,1203,1206],"ul",{},[1182,1183,1184],"li",{},"node ids are unique;",[1182,1186,1187],{},"every referenced agent, tool, skill and workflow exists and is visible to the organization;",[1182,1189,1190],{},"required inputs are connected, and every input and output reference resolves;",[1182,1192,1193,1194,1196,1197,1199],{},"a ",[827,1195,990],{}," declares a ",[827,1198,1002],{},";",[1182,1201,1202],{},"branch conditions use the supported deterministic operators;",[1182,1204,1205],{},"subworkflow nesting stays inside the platform cap;",[1182,1207,1208],{},"the scopes the referenced capabilities need are grantable.",[807,1210,1211,1212,822],{},"A workflow written in chat and a workflow drawn by hand run the same validator, because both are one ",[827,1213,829],{},[837,1215,1217],{"id":1216},"conversational-authoring-and-visual-editing-are-two-doors","Conversational authoring and visual editing are two doors",[807,1219,1220,1221,1224],{},"The visualizer does not replace the ",[882,1222,1223],{"href":306},"front door builder chat",". Both edit one draft.",[845,1226,1229],{"className":1227,"code":1228,"language":850,"meta":851},[848],"\"research prospects, wait for approval, then start outreach\"\n                    │\n              Front Door\n                    │\n        Definition Builder Agent\n                    │\n               draft_config\n                    │\n          Workflow visualizer\n                    │\n          person reviews \u002F edits\n                    │\n            validate ──> publish\n",[827,1230,1228],{"__ignoreMap":851},[1232,1233,1234,1240],"ol",{},[1182,1235,1236,1239],{},[811,1237,1238],{},"Conversation first"," — describe the workflow, and let the builder agent write the draft.",[1182,1241,1242,1245],{},[811,1243,1244],{},"Visual first"," — compose or change the same draft in the graph.",[807,1247,1248],{},"A change in either surface updates the same durable draft. Until a publish, nothing can run it.",[837,1250,1252],{"id":1251},"run-mode","Run mode",[807,1254,1255],{},"Run mode renders the immutable snapshot the Run froze at start. It does not render the current published definition.",[845,1257,1260],{"className":1258,"code":1259,"language":850,"meta":851},[848],"current published_config ────┐\n                             │ they differ after an edit\nRun snapshot ────────────────┘\n          │\n          ▼\n     run visualizer\n",[827,1261,1259],{"__ignoreMap":851},[807,1263,1264],{},"The page states plainly when the current definition differs from the snapshot, and links to the current definition. A historical Run must render correctly without reading the current definition at all.",[1142,1266,1268],{"id":1267},"runtime-overlays","Runtime overlays",[807,1270,1271],{},"Each node carries one small overlay.",[900,1273,1274,1284],{},[903,1275,1276],{},[906,1277,1278,1281],{},[909,1279,1280],{},"State",[909,1282,1283],{},"Example rendering",[919,1285,1286,1296,1306,1316,1326,1336,1346],{},[906,1287,1288,1291],{},[924,1289,1290],{},"Pending",[924,1292,1293],{},[827,1294,1295],{},"○ Find People",[906,1297,1298,1301],{},[924,1299,1300],{},"Running",[924,1302,1303],{},[827,1304,1305],{},"● Find People · 24\u002F40",[906,1307,1308,1311],{},[924,1309,1310],{},"Succeeded",[924,1312,1313],{},[827,1314,1315],{},"✓ Find People · 31s",[906,1317,1318,1321],{},[924,1319,1320],{},"Waiting",[924,1322,1323],{},[827,1324,1325],{},"⚠ Human Review · waiting",[906,1327,1328,1331],{},[924,1329,1330],{},"Failed",[924,1332,1333],{},[827,1334,1335],{},"✕ Enrichment · Exa timed out",[906,1337,1338,1341],{},[924,1339,1340],{},"Skipped",[924,1342,1343],{},[827,1344,1345],{},"– Email Sequence · branch not taken",[906,1347,1348,1351],{},[924,1349,1350],{},"Cancelled",[924,1352,1353],{},[827,1354,1355],{},"× Research · cancelled",[807,1357,1358],{},"Live state comes from the Run stream. Historical state is rebuilt from the Run row and its spans, with no event log. The UI never reads Inngest execution state.",[1142,1360,1362],{"id":1361},"node-details","Node details",[807,1364,1365],{},"Selecting a node opens its execution detail.",[845,1367,1370],{"className":1368,"code":1369,"language":850,"meta":851},[848],"Company Research Agent\n\nStatus       succeeded\nDuration     28.2s\nCost         $0.14\nChild Run    run_abc123\n\nInput        Acme Ltd\nOutput       Research completed\n\nExecution\n├─ LLM                    3.2s\n├─ web_search             8.1s\n├─ scrape_page            6.4s\n└─ LLM                    2.8s\n",[827,1371,1369],{"__ignoreMap":851},[807,1373,1374],{},"A node is therefore the friendly entry point into the Run and span tree. It does not replace it.",[1142,1376,1378],{"id":1377},"progress-is-a-whole-run-not-a-graph-feed","Progress is a whole Run, not a graph feed",[807,1380,1381,1382,1385],{},"The graph answers ",[811,1383,1384],{},"where the Run is, and how it got there",". It is not the only way to read output. The Run Explorer keeps its four product views.",[900,1387,1388,1398],{},[903,1389,1390],{},[906,1391,1392,1395],{},[909,1393,1394],{},"View",[909,1396,1397],{},"Question",[919,1399,1400,1408,1416,1424],{},[906,1401,1402,1405],{},[924,1403,1404],{},"Overview",[924,1406,1407],{},"What is happening?",[906,1409,1410,1413],{},[924,1411,1412],{},"Execution",[924,1414,1415],{},"What did the workflow and its agents do?",[906,1417,1418,1421],{},[924,1419,1420],{},"Results",[924,1422,1423],{},"What business output did it produce or change?",[906,1425,1426,1429],{},[924,1427,1428],{},"Definition",[924,1430,1431],{},"What exact configuration ran?",[807,1433,1434],{},"The graph is reused in Overview and Definition, and navigates into Execution. Result tables and created CRM records stay separate.",[837,1436,1438],{"id":1437},"approvals-in-place","Approvals in place",[807,1440,1441,1442,1444],{},"An ",[827,1443,1021],{}," node shows the decision where it interrupted the Run.",[845,1446,1449],{"className":1447,"code":1448,"language":850,"meta":851},[848],"✓ Qualify Prospects\n        │\n        ▼\n⚠ Human Review\n  waiting for approval\n        │\n        ▼\n○ Email Sequence\n",[827,1450,1448],{"__ignoreMap":851},[807,1452,1453],{},"Selecting it shows the proposed action, the rule that asked for a person, who requested it, the exact target or content, the expiry, and the action that resolves it. The approval inbox stays the global queue. The visualizer renders the same approval row, and never a second one.",[837,1455,1457],{"id":1456},"parallel-work-and-subworkflows","Parallel work and subworkflows",[807,1459,1460,1461,1463],{},"A ",[827,1462,941],{}," container stays readable without becoming a free-form canvas.",[845,1465,1468],{"className":1466,"code":1467,"language":850,"meta":851},[848],"          ┌─ Find People ───────┐\nEnrich ───┤                     ├── Merge\n          └─ Find Signals ──────┘\n",[827,1469,1467],{"__ignoreMap":851},[807,1471,1472],{},"Each branch updates on its own. The merge advances only when the runtime reports the container complete.",[807,1474,1460,1475,1477],{},[827,1476,978],{}," draws as one collapsed node.",[845,1479,1482],{"className":1480,"code":1481,"language":850,"meta":851},[848],"┌─────────────────────┐\n│ Email Sequence      │\n│ subworkflow     ›   │\n└─────────────────────┘\n",[827,1483,1481],{"__ignoreMap":851},[807,1485,1486],{},"A person drills into the child Run instead of expanding the nested graph inline. Nesting is capped at publish time, and the parent graph stays readable.",[837,1488,1490],{"id":1489},"ux-rules","UX rules",[1179,1492,1493,1499,1505,1511,1517,1523,1529,1535],{},[1182,1494,1495,1498],{},[811,1496,1497],{},"Definition first."," Node identity and labels come from the definition. Runtime only adds an overlay.",[1182,1500,1501,1504],{},[811,1502,1503],{},"Stable identity."," A node keeps one id across build, view and run.",[1182,1506,1507,1510],{},[811,1508,1509],{},"Configuration off-canvas."," The graph carries shape. The panel carries detail.",[1182,1512,1513,1516],{},[811,1514,1515],{},"Progressive disclosure."," Show business status first. Tool, LLM and span detail is one click deeper.",[1182,1518,1519,1522],{},[811,1520,1521],{},"No infrastructure vocabulary."," Never show an Inngest function id, an attempt count or a worker detail in the product UI.",[1182,1524,1525,1528],{},[811,1526,1527],{},"No silent definition drift."," A historical Run always renders its own snapshot.",[1182,1530,1531,1534],{},[811,1532,1533],{},"Mobile degrades vertically."," The same definition stays understandable without a wide canvas.",[1182,1536,1537,1540,1541,1544],{},[811,1538,1539],{},"The visualizer never changes a Run in flight."," Editing edits a draft for future Runs. Cancel stays a Run control, and ",[827,1542,1543],{},"disable"," stops a new Run tree only.",[837,1546,1548],{"id":1547},"contracts-it-consumes","Contracts it consumes",[807,1550,1551,1552,822],{},"The visualizer needs no new execution API. It reads the definition and Run contracts the platform already owns. See ",[882,1553,253],{"href":249},[1142,1555,1131],{"id":1556},"build-mode-1",[845,1558,1561],{"className":1559,"code":1560,"language":850,"meta":851},[848],"GET    \u002Fapi\u002Fv1\u002Fagentic\u002Fdefinitions\u002F{id}\nPATCH  \u002Fapi\u002Fv1\u002Fagentic\u002Fdefinitions\u002F{id}\u002Fdraft       expected_updated_at\nPOST   \u002Fapi\u002Fv1\u002Fagentic\u002Fdefinitions\u002F{id}\u002Fvalidate\nPOST   \u002Fapi\u002Fv1\u002Fagentic\u002Fdefinitions\u002F{id}\u002Fpublish     expected_updated_at\nPOST   \u002Fapi\u002Fv1\u002Fagentic\u002Fdefinitions\u002F{id}\u002Ffork\n",[827,1562,1560],{"__ignoreMap":851},[1142,1564,1252],{"id":1565},"run-mode-1",[845,1567,1570],{"className":1568,"code":1569,"language":850,"meta":851},[848],"GET    \u002Fapi\u002Fv1\u002Fagentic\u002Fruns\u002F{id}\nGET    \u002Fapi\u002Fv1\u002Fagentic\u002Fruns\u002F{id}\u002Fspans?cursor=\nGET    \u002Fapi\u002Fv1\u002Fagentic\u002Fruns?parent_run_id={id}&cursor=\nGET    \u002Fapi\u002Fv1\u002Fagentic\u002Fruns\u002F{id}\u002Fstream\n",[827,1571,1569],{"__ignoreMap":851},[807,1573,1574,1577,1578,1581],{},[811,1575,1576],{},"There is no run tree route, and the visualizer must not ask for one."," Run detail embeds no child list and carries ",[827,1579,1580],{},"child_count"," only, because a parallel node's widest case is five hundred children. The graph reads children through the paged list route, one node at a time, as it needs them.",[1142,1583,1585],{"id":1584},"the-minimum-the-graph-needs","The minimum the graph needs",[845,1587,1590],{"className":1588,"code":1589,"language":850,"meta":851},[848],"definition (or Run snapshot)\n  nodes[]\n    id\n    type\n    label\n    config\n    input bindings\n  the deterministic parent\u002Fchild relationships\n\nRunExecutionOverlay\n  run_id\n  node_id ->\n    status\n    started_at\n    ended_at\n    progress\n    child_run_id?\n    error_summary?\n    result_summary?\n",[827,1591,1589],{"__ignoreMap":851},[807,1593,1594],{},"The overlay is a projection of the Run and its spans. Do not persist a second graph for visualization, and do not add a durable event table beside the spans. Layout metadata may live with the definition if manual positioning earns its place later. Execution state stays in Runs and spans.",[837,1596,1598],{"id":1597},"v1-scope","V1 scope",[1232,1600,1601,1604,1612,1615,1618,1621,1626,1629,1632,1635],{},[1182,1602,1603],{},"A vertical, top-to-bottom graph.",[1182,1605,1606,1607,885,1609,1611],{},"All eight node types, with ",[827,1608,928],{},[827,1610,941],{}," drawn as containers.",[1182,1613,1614],{},"Click a node, open the side panel.",[1182,1616,1617],{},"Add, connect, configure and remove nodes in build mode.",[1182,1619,1620],{},"Deterministic validation and an explicit publish.",[1182,1622,1623,1624,822],{},"A read-only mode over ",[827,1625,870],{},[1182,1627,1628],{},"Live status overlays on a running Run.",[1182,1630,1631],{},"A completed Run rebuilt from the Run row and its spans.",[1182,1633,1634],{},"Approval state shown in place.",[1182,1636,1637,1638,1640,1641,1643],{},"A drill from an ",[827,1639,966],{}," or ",[827,1642,978],{}," node into the child Run.",[837,1645,1647],{"id":1646},"not-in-v1","Not in V1",[1179,1649,1650,1653,1656,1659,1662,1665,1668,1671,1674],{},[1182,1651,1652],{},"Free-form DAG authoring, code nodes, loops, or a dynamic fan-out node.",[1182,1654,1655],{},"Graph mutation at run time.",[1182,1657,1658],{},"A custom node or plugin SDK.",[1182,1660,1661],{},"Visual editing of a Run in flight.",[1182,1663,1664],{},"Inngest-level visualization.",[1182,1666,1667],{},"A second event store, or a second graph representation for runtime.",[1182,1669,1670],{},"Minimaps, canvas collaboration, comments and multiplayer editing.",[1182,1672,1673],{},"Automatic migration of a customized workflow when a platform template changes.",[1182,1675,1676],{},"Definition revision, history and rollback. The platform contract already excludes it.",[837,1678,1680],{"id":1679},"product-situations","Product situations",[900,1682,1683,1696],{},[903,1684,1685],{},[906,1686,1687,1690,1693],{},[909,1688,1689],{},"#",[909,1691,1692],{},"Situation",[909,1694,1695],{},"What happens",[919,1697,1698,1712,1723,1734,1752,1763,1778],{},[906,1699,1700,1703,1706],{},[924,1701,1702],{},"1",[924,1704,1705],{},"The builder agent writes the first draft",[924,1707,1708,1709,1711],{},"A person asks for a prospect qualification workflow in chat. The UI opens that same draft in the graph. The person swaps the qualification agent, adds an ",[827,1710,1021],{}," node, validates and publishes.",[906,1713,1714,1717,1720],{},[924,1715,1716],{},"2",[924,1718,1719],{},"A person builds it by hand",[924,1721,1722],{},"An admin starts from a blank workflow or forks a platform template, places nodes from the constrained set, connects inputs, validates and publishes. The result is the same definition shape a conversation produces.",[906,1724,1725,1728,1731],{},[924,1726,1727],{},"3",[924,1729,1730],{},"A person watches a live Run",[924,1732,1733],{},"The Run starts from chat or a trigger. The Run Explorer opens the graph from the snapshot. Nodes move pending -> running -> succeeded, and counters update on the stream.",[906,1735,1736,1739,1742],{},[924,1737,1738],{},"4",[924,1740,1741],{},"A Run waits for a person",[924,1743,1744,1745,1747,1748,1751],{},"The ",[827,1746,1021],{}," node reads ",[827,1749,1750],{},"waiting",", and later nodes stay pending. The person approves it in the node, and the same graph resumes when the runtime resumes the Run.",[906,1753,1754,1757,1760],{},[924,1755,1756],{},"5",[924,1758,1759],{},"The definition changed after the Run",[924,1761,1762],{},"A person republished the workflow. An older Run still renders its own snapshot. The page says the current definition differs, and links to it.",[906,1764,1765,1768,1771],{},[924,1766,1767],{},"6",[924,1769,1770],{},"The Run is older than the span window",[924,1772,1773,1774,1777],{},"Spans are kept 90 days and Runs 13 months, so a Run in between renders ",[811,1775,1776],{},"partly"," blank: an agent or subworkflow node still has a child Run and keeps its status, while a tool, wait, branch or approval node loses the span it read and has none. Say so on the graph. Left unlabelled it reads as a workflow whose steps never ran, which is the one thing it does not mean.",[906,1779,1780,1782,1785],{},[924,1781,1767],{},[924,1783,1784],{},"A failure is investigated",[924,1786,1787,1788,1791],{},"The enrichment node fails. The graph shows the failed node and a short error. Clicking it opens the execution detail, then the tool span that holds the failed ",[827,1789,1790],{},"web_search"," call.",[837,1793,1795],{"id":1794},"success-criteria","Success criteria",[1179,1797,1798,1801,1804,1807,1810,1813],{},[1182,1799,1800],{},"A non-technical person can say where a Run is without opening a log.",[1182,1802,1803],{},"A workflow authored in chat and one authored visually produce the same definition shape.",[1182,1805,1806],{},"The UI renders a historical Run without reading the current definition.",[1182,1808,1809],{},"No visualizer-specific runtime, event store or second graph is introduced.",[1182,1811,1812],{},"Every drawn node maps to definition data, and, while running, to Run and span data.",[1182,1814,1815],{},"One graph component serves the builder, the definition page and the Run Explorer.",[837,1817,1819],{"id":1818},"key-decision","Key decision",[807,1821,1822],{},"This replaces the V1 rule \"no visual DAG builder\" with a narrower one:",[1824,1825,1826],"blockquote",{},[807,1827,1828],{},[811,1829,1830],{},"Build a constrained visual editor and runtime visualizer over the same definition graph. Do not build a general-purpose DAG platform.",[807,1832,1833],{},"The exclusion that stays is arbitrary workflow code, loops and dynamic fan-out. The runtime vocabulary does not grow. What grows is how a person sees it.",{"title":851,"searchDepth":32,"depth":233,"links":1835},[1836,1837,1838,1839,1840,1844,1845,1850,1851,1852,1853,1858,1859,1860,1861,1862],{"id":839,"depth":32,"text":840},{"id":863,"depth":32,"text":864},{"id":891,"depth":32,"text":892},{"id":1059,"depth":32,"text":1060},{"id":1130,"depth":32,"text":1131,"children":1841},[1842,1843],{"id":1144,"depth":233,"text":1145},{"id":329,"depth":233,"text":1171},{"id":1216,"depth":32,"text":1217},{"id":1251,"depth":32,"text":1252,"children":1846},[1847,1848,1849],{"id":1267,"depth":233,"text":1268},{"id":1361,"depth":233,"text":1362},{"id":1377,"depth":233,"text":1378},{"id":1437,"depth":32,"text":1438},{"id":1456,"depth":32,"text":1457},{"id":1489,"depth":32,"text":1490},{"id":1547,"depth":32,"text":1548,"children":1854},[1855,1856,1857],{"id":1556,"depth":233,"text":1131},{"id":1565,"depth":233,"text":1252},{"id":1584,"depth":233,"text":1585},{"id":1597,"depth":32,"text":1598},{"id":1646,"depth":32,"text":1647},{"id":1679,"depth":32,"text":1680},{"id":1794,"depth":32,"text":1795},{"id":1818,"depth":32,"text":1819},"md",{},true,[1867,1868,1869,1870,1871,1872],"engineering\u002Fsystem-design\u002Fagentic-platform\u002Fruntime\u002Fdefinitions","engineering\u002Fsystem-design\u002Fagentic-platform\u002Fruntime\u002Fexecution","engineering\u002Fsystem-design\u002Fagentic-platform\u002Finterfaces\u002Fsurfaces","engineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fbuilder-chat","engineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fhuman-review","engineering\u002Fsystem-design\u002Fagentic-platform\u002Fplanes\u002Fobservability-and-operations",{"title":358,"description":359},"engineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fworkflow-visualizer",[312,362,258,311,217,282,363,255],"MmY9FofaBLXxI445XS9TlWs4L2TXCFizRklRvlAVi-o",1788650195974]