[{"data":1,"prerenderedAt":1559},["ShallowReactive",2],{"docs-nav":3,"docs-article-engineering\u002Fsystem-design\u002Fagentic-platform":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":181,"body":799,"customComponent":480,"description":213,"extension":1546,"group":139,"lastUpdated":201,"meta":1547,"navigation":1548,"order":22,"path":212,"related":1549,"section":214,"seo":1555,"stem":1556,"tags":1557,"__hash__":1558},"docs\u002Fengineering\u002Fsystem-design\u002Fagentic-platform\u002Findex.md",{"type":800,"value":801,"toc":1533},"minimark",[802,806,810,813,826,830,835,894,897,915,918,922,995,998,1019,1023,1026,1046,1069,1080,1084,1087,1090,1093,1097,1100,1103,1118,1125,1131,1135,1178,1182,1185,1222,1225,1229,1267,1278,1282,1285,1317,1320,1324,1527],[803,804,181],"h1",{"id":805},"agentic-platform",[807,808,809],"p",{},"This page is the map. It shows every core component and the whole path from a request to a result. It hides the classes, the tables and the contracts. Each layer page below carries those.",[807,811,812],{},"Read this page first. Then read the layer page for the part you must change.",[807,814,815,816,820,821,825],{},"One box carries a ",[817,818,819],"strong",{},"TODO",". The MCP server is planned and not built, and ",[822,823,824],"a",{"href":219},"agent access"," records what works today.",[827,828],"doc-diagram",{"caption":829,"name":216},"A person, a machine, or an AI agent working for a person. All of them meet at one run boundary, and one runtime executes the work. Products sit on top as definitions plus product data, and nothing reaches the world except through a tool. The MCP server is marked TODO because it is planned and not built.",[831,832,834],"h2",{"id":833},"code-and-naming","Code and naming",[836,837,838,854],"table",{},[839,840,841],"thead",{},[842,843,844,848,851],"tr",{},[845,846,847],"th",{},"Term",[845,849,850],{},"Meaning",[845,852,853],{},"Example",[855,856,857,872,883],"tbody",{},[842,858,859,863,866],{},[860,861,862],"td",{},"Capability",[860,864,865],{},"An action the user can request",[860,867,868],{},[869,870,871],"code",{},"company.search",[842,873,874,877,880],{},[860,875,876],{},"Workflow",[860,878,879],{},"The steps that perform an action",[860,881,882],{},"Resolve identities, remove duplicates, apply filters",[842,884,885,888,891],{},[860,886,887],{},"Tool",[860,889,890],{},"One operation that a step can call",[860,892,893],{},"Read company data",[807,895,896],{},"A product is a user-facing area, such as Companies. Its actions are capabilities.\nThe Front Door selects work. The runtime executes it and checks permissions.",[807,898,899,900,903,904,907,908,914],{},"In the API, ",[869,901,902],{},"src\u002Fagentic\u002Fcapabilities\u002F"," holds business actions and their workflows.\n",[869,905,906],{},"src\u002Fagentic\u002Fservices\u002F"," holds shared tools, context, memory and data access.\nThe ",[822,909,913],{"href":910,"rel":911},"https:\u002F\u002Fgithub.com\u002FAlterityNetwork\u002Fac-python-api\u002Fblob\u002Fagentic-platform\u002Fsrc\u002Fagentic\u002FREADME.md",[912],"nofollow","API onboarding guide"," shows the request flow and where to change code.",[807,916,917],{},"The Front Door selects the five stable product IDs.\nIt keeps the published Agent and Workflow UUID path for custom definitions.",[831,919,921],{"id":920},"the-four-stages","The four stages",[836,923,924,937],{},[839,925,926],{},[842,927,928,931,934],{},[845,929,930],{},"Stage",[845,932,933],{},"What happens",[845,935,936],{},"The rule it obeys",[855,938,939,956,969,982],{},[842,940,941,946,953],{},[860,942,943],{},[817,944,945],{},"1 · Who starts the work",[860,947,948,949,952],{},"A person speaks to a conversational surface, or works in the product UI. A machine reports an event, and a trigger matches it to one rule. An AI agent works for a person, and drives the ",[869,950,951],{},"ac"," CLI on that person's seat.",[860,954,955],{},"Whoever calls, the call ends at the same boundary.",[842,957,958,963,966],{},[860,959,960],{},[817,961,962],{},"2 · One door into execution",[860,964,965],{},"Every caller reaches the same run start. The run manager freezes the published definition, the skills, the tool contracts, the context policy and the principal. Policy answers: allow, deny, or require approval. Inngest then owns retry, wait and time out.",[860,967,968],{},"Every run starts here, or nowhere.",[842,970,971,976,979],{},[860,972,973],{},[817,974,975],{},"3 · The work",[860,977,978],{},"The runtime rebuilds fresh, scoped context, then claims the run and dispatches it by kind. An agent runs a model loop; a workflow follows the steps we wrote. Either one reaches the world only through a tool.",[860,980,981],{},"One agentic hop. One runtime.",[842,983,984,989,992],{},[860,985,986],{},[817,987,988],{},"4 · What comes back",[860,990,991],{},"The run row, its spans and its cost are the durable record. Discovery work also lands in product state: global intelligence, then organization prospect, then CRM. Anything needing a person collects in the approval inbox.",[860,993,994],{},"One record, one answer, one bill.",[807,996,997],{},"Three planes run across all four stages, so they need no arrows of their own:",[999,1000,1001,1008,1014],"ul",{},[1002,1003,1004,1007],"li",{},[817,1005,1006],{},"Policy"," decides at admission, at every tool call, and as cost accrues.",[1002,1009,1010,1013],{},[817,1011,1012],{},"Observability"," writes one run row, one span for each unit of work, and one cost meter. The durable span is written before the live event.",[1002,1015,1016,1018],{},[817,1017,270],{}," makes the same message, webhook or tool call take effect only once.",[831,1020,1022],{"id":1021},"what-a-long-workflow-needs","What a long workflow needs",[807,1024,1025],{},"Inngest is not just a queue. Three of its guarantees are what make a multi-day workflow possible at all:",[999,1027,1028,1034,1040],{},[1002,1029,1030,1033],{},[817,1031,1032],{},"Retry."," A step that failed runs again from where it stopped, not from the top of the run.",[1002,1035,1036,1039],{},[817,1037,1038],{},"Wait."," A run can park on a reply, an event, an approval, or a date, and hold no worker while it waits.",[1002,1041,1042,1045],{},[817,1043,1044],{},"Time out."," A wait that never resolves ends the run, instead of leaking it.",[807,1047,1048,1049,1052,1053,1056,1057,1060,1061,1064,1065,1068],{},"The email sequence is the clearest case, and the diagram opens it up: an ",[817,1050,1051],{},"agent step"," drafts the email and follows a skill, a ",[817,1054,1055],{},"tool step"," calls ",[869,1058,1059],{},"email.send"," where the tool invoker asks policy first, an ",[817,1062,1063],{},"approval step"," parks the run until a person decides, and a ",[817,1066,1067],{},"wait"," holds for a reply or three days. That is one run, not a chain of cron jobs.",[807,1070,1071,1072,1075,1076,1079],{},"A workflow has eight node types. Two are containers, ",[869,1073,1074],{},"sequence"," and ",[869,1077,1078],{},"parallel",". Six are steps: agent, tool, approval, wait, branch, subworkflow. There are no loops and no expression engine. The node set is fixed at publish time, so bounded fan out over runtime data lives inside one step.",[831,1081,1083],{"id":1082},"what-an-organization-can-add","What an organization can add",[807,1085,1086],{},"Platform templates are read-only, and an organization extends the platform by adding its own definitions:",[807,1088,1089],{},"| To add | How |\n|---|---|---|\n| An agent or a workflow | Fork a platform template, then edit and publish the fork |\n| A skill | Write one. A skill teaches an agent how to use the tools it already has |\n| A tool | Use a platform tool or approved vendor integration. MCP servers are deferred |",[807,1091,1092],{},"Writing new executable tool code is deliberately deferred. Use platform tools, vendor integrations, and organization-authored skills first. MCP expands the tool source later, after the web-first interface slice is working. Whatever the source, publishing stays the safety boundary: a draft cannot run.",[831,1094,1096],{"id":1095},"one-page-for-every-decision-a-run-waits-on","One page for every decision a run waits on",[807,1098,1099],{},"A run that stops for a person always stops for the same reason: it proposes an exact action, and somebody must authorize it. Every one of those collects in the approval inbox, whatever created it.",[807,1101,1102],{},"Three things create one:",[999,1104,1105,1108,1111],{},[1002,1106,1107],{},"policy at admission, before a run executes anything;",[1002,1109,1110],{},"policy at a tool call, such as an email waiting to send;",[1002,1112,1113,1114,1117],{},"an ",[869,1115,1116],{},"approval"," node, because the workflow author asked for a gate there.",[807,1119,1120,1121,1124],{},"The approval inbox is the guaranteed floor for all three. A channel may render buttons, but every presentation resolves the same approval row, and silence is never consent. The ",[822,1122,1123],{"href":344},"human review inbox"," is the product page for it.",[807,1126,1127,1130],{},[817,1128,1129],{},"Curation is not authorization."," A new prospect waiting to be watched, dismissed or promoted is business judgement, not permission to act, and it stays in Signals Search. Folding it into the approval inbox would mix a queue a person may ignore with a queue that blocks a run.",[831,1132,1134],{"id":1133},"why-it-has-this-shape","Why it has this shape",[1136,1137,1138,1144,1154,1160,1166,1172],"ol",{},[1002,1139,1140,1143],{},[817,1141,1142],{},"One product execution substrate."," One run model, one status model, one event surface.",[1002,1145,1146,1149,1150,1153],{},[817,1147,1148],{},"One agent framework."," Agno runs the reasoning loop, behind ",[869,1151,1152],{},"AgentRuntime",". There is no backend selector and no runtime registry.",[1002,1155,1156,1159],{},[817,1157,1158],{},"One agentic hop."," The front door picks one agent or one workflow. Coordinating a workflow is not a second reasoning hop.",[1002,1161,1162,1165],{},[817,1163,1164],{},"The runtime is one layer, and Agno sits behind it."," The run executor dispatches by kind. The agent loop lives behind a framework-neutral interface, and no Agno type reaches policy, tools, definitions or surfaces. That is what keeps the framework replaceable.",[1002,1167,1168,1171],{},[817,1169,1170],{},"An agent reaches the world only through a tool."," No credentials, no raw SQL, and no arbitrary API access in model context.",[1002,1173,1174,1177],{},[817,1175,1176],{},"Publishing is a safety boundary."," A draft cannot run. A run freezes the published configuration, and reads policy and tool state live at each checkpoint.",[831,1179,1181],{"id":1180},"one-request-end-to-end","One request, end to end",[807,1183,1184],{},"A user writes in web chat: \"find UK fintech companies with recent funding signals and marketing decision makers.\"",[1136,1186,1187,1190,1193,1200,1207,1210,1213,1216,1219],{},[1002,1188,1189],{},"The web adapter authenticates the user and normalizes the message.",[1002,1191,1192],{},"The Front Door builds scoped context and an eligible capability shortlist.",[1002,1194,1195,1196,1199],{},"The model selects ",[869,1197,1198],{},"signals.search"," with its version and validated input.",[1002,1201,1202,1203,1206],{},"The capability service resolves the tenant executor and calls ",[869,1204,1205],{},"RunManager.start()"," with the message's stable key.",[1002,1208,1209],{},"RunManager freezes the definition tree and capability metadata. Policy admits, denies or requests approval.",[1002,1211,1212],{},"The workflow performs bounded research and calls its published Company\u002FPeople child workflows.",[1002,1214,1215],{},"Tool calls pass action policy. Enrichment writes canonical Intelligence; Signals writes organization prospects.",[1002,1217,1218],{},"The Run and conversation streams report progress. The user reviews the resulting prospects.",[1002,1220,1221],{},"CRM promotion remains an explicit action. Email sequence execution belongs to a separate Phase 8 action.",[807,1223,1224],{},"A compound request with no single matching published capability produces a clarification.\nThe Front Door does not start an implicit search\u002Fenrich\u002Foutreach plan.",[831,1226,1228],{"id":1227},"delivery-phases","Delivery phases",[836,1230,1231,1241],{},[839,1232,1233],{},[842,1234,1235,1238],{},[845,1236,1237],{},"Phase",[845,1239,1240],{},"Scope",[855,1242,1243,1251,1259],{},[842,1244,1245,1248],{},[860,1246,1247],{},"7",[860,1249,1250],{},"Company, People and Signals capability products",[842,1252,1253,1256],{},[860,1254,1255],{},"8",[860,1257,1258],{},"Email sequence execution",[842,1260,1261,1264],{},[860,1262,1263],{},"9",[860,1265,1266],{},"Remaining legacy cutover and removal",[807,1268,1269,1270,1273,1274,1277],{},"The ",[822,1271,1272],{"href":315},"capability contracts"," define the Phase 7 boundary.\nThe ",[822,1275,1276],{"href":324},"design scenarios"," define its normal, failure and recovery cases.",[831,1279,1281],{"id":1280},"how-these-pages-are-organized","How these pages are organized",[807,1283,1284],{},"The four stages above tell the story of one request. The pages cover five areas. Existing article URLs remain stable and do not define Python package names.",[999,1286,1287,1293,1299,1305,1311],{},[1002,1288,1289,1292],{},[817,1290,1291],{},"Interfaces"," - who starts a run, and how the request reaches us.",[1002,1294,1295,1298],{},[817,1296,1297],{},"Runtime"," - how the work executes.",[1002,1300,1301,1304],{},[817,1302,1303],{},"Services"," - shared tools, context, memory and data access.",[1002,1306,1307,1310],{},[817,1308,1309],{},"Planes"," - what crosses every stage.",[1002,1312,1313,1316],{},[817,1314,1315],{},"Products"," - the platform applied to one product.",[807,1318,1319],{},"Policy and observability belong to a tier and to a stage at the same time. That is what a plane means. It crosses every stage, so it takes no place in the sequence.",[831,1321,1323],{"id":1322},"where-to-read-more","Where to read more",[836,1325,1326,1339],{},[839,1327,1328],{},[842,1329,1330,1333,1336],{},[845,1331,1332],{},"Tier",[845,1334,1335],{},"Box in the diagram",[845,1337,1338],{},"Page",[855,1340,1341,1352,1362,1372,1382,1397,1408,1419,1430,1441,1452,1462,1473,1483,1494,1505,1516],{},[842,1342,1343,1345,1348],{},[860,1344,1291],{},[860,1346,1347],{},"Web chat · Approval inbox · Agent builder · Run explorer",[860,1349,1350],{},[822,1351,250],{"href":249},[842,1353,1354,1356,1358],{},[860,1355,1291],{},[860,1357,231],{},[860,1359,1360],{},[822,1361,231],{"href":230},[842,1363,1364,1366,1368],{},[860,1365,1291],{},[860,1367,242],{},[860,1369,1370],{},[822,1371,242],{"href":241},[842,1373,1374,1376,1378],{},[860,1375,1291],{},[860,1377,262],{},[860,1379,1380],{},[822,1381,262],{"href":261},[842,1383,1384,1386,1392],{},[860,1385,1291],{},[860,1387,1388,1389,1391],{},"Claude Code · MCP clients · the ",[869,1390,951],{}," CLI · MCP server",[860,1393,1394,1396],{},[822,1395,220],{"href":219}," - a stub, not a design",[842,1398,1399,1401,1404],{},[860,1400,1297],{},[860,1402,1403],{},"Agentic runtime · Agent · Workflow",[860,1405,1406],{},[822,1407,380],{"href":379},[842,1409,1410,1412,1415],{},[860,1411,1297],{},[860,1413,1414],{},"Authoring · Definitions",[860,1416,1417],{},[822,1418,366],{"href":365},[842,1420,1421,1423,1426],{},[860,1422,1297],{},[860,1424,1425],{},"Run manager · Inngest · Approvals",[860,1427,1428],{},[822,1429,373],{"href":372},[842,1431,1432,1434,1437],{},[860,1433,1303],{},[860,1435,1436],{},"Tools · where a tool lands",[860,1438,1439],{},[822,1440,191],{"href":190},[842,1442,1443,1445,1448],{},[860,1444,1303],{},[860,1446,1447],{},"What the run may read · Context builder",[860,1449,1450],{},[822,1451,179],{"href":178},[842,1453,1454,1456,1458],{},[860,1455,1309],{},[860,1457,1006],{},[860,1459,1460],{},[822,1461,288],{"href":287},[842,1463,1464,1466,1469],{},[860,1465,1309],{},[860,1467,1468],{},"Run row · Spans · Cost meter",[860,1470,1471],{},[822,1472,278],{"href":277},[842,1474,1475,1477,1479],{},[860,1476,1309],{},[860,1478,270],{},[860,1480,1481],{},[822,1482,270],{"href":269},[842,1484,1485,1487,1490],{},[860,1486,1315],{},[860,1488,1489],{},"Global intelligence · Organization prospect · CRM",[860,1491,1492],{},[822,1493,6],{"href":297},[842,1495,1496,1498,1501],{},[860,1497,1315],{},[860,1499,1500],{},"Default chat answers from context",[860,1502,1503],{},[822,1504,339],{"href":338},[842,1506,1507,1509,1512],{},[860,1508,1315],{},[860,1510,1511],{},"Approval inbox, as a product page",[860,1513,1514],{},[822,1515,345],{"href":344},[842,1517,1518,1520,1523],{},[860,1519,1315],{},[860,1521,1522],{},"Workflow graph, in the builder and in a Run",[860,1524,1525],{},[822,1526,358],{"href":357},[807,1528,1269,1529,1532],{},[822,1530,1531],{"href":203},"platform contract"," holds the layer ownership table, the shared contracts, the data model, and the list of what we are not building.",{"title":1534,"searchDepth":32,"depth":233,"links":1535},"",[1536,1537,1538,1539,1540,1541,1542,1543,1544,1545],{"id":833,"depth":32,"text":834},{"id":920,"depth":32,"text":921},{"id":1021,"depth":32,"text":1022},{"id":1082,"depth":32,"text":1083},{"id":1095,"depth":32,"text":1096},{"id":1133,"depth":32,"text":1134},{"id":1180,"depth":32,"text":1181},{"id":1227,"depth":32,"text":1228},{"id":1280,"depth":32,"text":1281},{"id":1322,"depth":32,"text":1323},"md",{},true,[1550,1551,1552,1553,1554],"engineering\u002Fsystem-design\u002Fagentic-platform\u002Fcontract","engineering\u002Fsystem-design\u002Fagentic-platform\u002Finterfaces\u002Fagent-access","engineering\u002Fsystem-design\u002Fagentic-platform\u002Finterfaces\u002Ffront-door","engineering\u002Fsystem-design\u002Fagentic-platform\u002Fruntime","engineering\u002Fsystem-design\u002Fagentic-platform\u002Fproducts\u002Fagentic-crm",{"title":181,"description":213},"engineering\u002Fsystem-design\u002Fagentic-platform\u002Findex",[12,14,216,197,142,217,198],"ltkjWtbA4Gvz9KpFljLb5d4j-AEiQxicaDUJHxKjxGs",1788650174419]