1"use strict";(self.webpackChunkfactverse_docs=self.webpackChunkfactverse_docs||[]).push([[20864],{12367:(e,t,n)=>{n.r(t),n.d(t,{assets:()=>o,contentTitle:()=>c,default:()=>h,frontMatter:()=>a,metadata:()=>r,toc:()=>d});const r=JSON.parse('{"id":"factverse-ai-agent/architecture","title":"FactVerse AI Agent Architecture","description":"Architecture overview for FactVerse AI Agent across FactVerse Platform, DFS, Designer, Inspector, MCP, knowledge, simulation, and governed actions.","source":"@site/.generated/en/docs/factverse-ai-agent/architecture.md","sourceDirName":"factverse-ai-agent","slug":"/factverse-ai-agent/architecture","permalink":"/factverse-docs/factverse-ai-agent/architecture","draft":false,"unlisted":false,"tags":[],"version":"current","sidebarPosition":46,"frontMatter":{"slug":"/factverse-ai-agent/architecture","title":"FactVerse AI Agent Architecture","description":"Architecture overview for FactVerse AI Agent across FactVerse Platform, DFS, Designer, Inspector, MCP, knowledge, simulation, and governed actions.","sidebar_label":"Architecture","sidebar_position":46},"sidebar":"docs","previous":{"title":"Core Concepts","permalink":"/factverse-docs/factverse-ai-agent/core-concepts"},"next":{"title":"Capability Map","permalink":"/factverse-docs/factverse-ai-agent/capability-map"}}');var s=n(74848),i=n(28453);const a={slug:"/factverse-ai-agent/architecture",title:"FactVerse AI Agent Architecture",description:"Architecture overview for FactVerse AI Agent across FactVerse Platform, DFS, Designer, Inspector, MCP, knowledge, simulation, and governed actions.",sidebar_label:"Architecture",sidebar_position:"46"},c="FactVerse AI Agent Architecture",o={},d=[{value:"Architecture flow",id:"architecture-flow",level:2},{value:"Architecture layers",id:"architecture-layers",level:2},{value:"Runtime flow",id:"runtime-flow",level:2},{value:"Product responsibilities",id:"product-responsibilities",level:2},{value:"Deployment models",id:"deployment-models",level:2},{value:"Deployment planning checks",id:"deployment-planning-checks",level:2},{value:"Design principles",id:"design-principles",level:2}];function l(e){const t={h1:"h1",h2:"h2",header:"header",li:"li",mermaid:"mermaid",ol:"ol",p:"p",table:"table",tbody:"tbody",td:"td",th:"th",thead:"thead",tr:"tr",ul:"ul",...(0,i.R)(),...e.components};return(0,s.jsxs)(s.Fragment,{children:[(0,s.jsx)(t.header,{children:(0,s.jsx)(t.h1,{id:"factverse-ai-agent-architecture",children:"FactVerse AI Agent Architecture"})}),"\n",(0,s.jsx)(t.p,{children:"FactVerse AI Agent sits between enterprise AI clients and the FactVerse industrial runtime. It gives agents a governed way to use digital twins, operational data, knowledge, simulation services, and approved action paths while keeping product API access scoped and auditable."}),"\n",(0,s.jsx)(t.h2,{id:"architecture-flow",children:"Architecture flow"}),"\n",(0,s.jsx)(t.mermaid,{value:"flowchart TD\n A[Enterprise AI client] --\x3e B[MCP endpoint]\n B --\x3e C[Tenant, key, and scope checks]\n C --\x3e D[FactVerse tool access]\n D --\x3e E[Platform, DFS, Designer, Inspector, knowledge, simulation]\n E --\x3e F[Evidence-backed answer, compute result, or draft action]\n F --\x3e G[Human review and run record]\n G --\x3e H[Feedback to data, knowledge, and operating workflows]"}),"\n",(0,s.jsx)(t.h2,{id:"architecture-layers",children:"Architecture layers"}),"\n",(0,s.jsxs)(t.table,{children:[(0,s.jsx)(t.thead,{children:(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.th,{children:"Layer"}),(0,s.jsx)(t.th,{children:"Role"}),(0,s.jsx)(t.th,{children:"Main FactVerse connection"})]})}),(0,s.jsxs)(t.tbody,{children:[(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"AI clients and channels"}),(0,s.jsx)(t.td,{children:"Enterprise copilots, agent runners, workflow tools, and customer applications that need industrial
1context"}),(0,s.jsx)(t.td,{children:"MCP endpoints and scoped API keys"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Governance and tool access"}),(0,s.jsx)(t.td,{children:"Tenant boundary, scope checks, audit records, human approval, and write-action control"}),(0,s.jsx)(t.td,{children:"FactVerse Platform identity, permission, and tenant context"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Data and knowledge"}),(0,s.jsx)(t.td,{children:"Operational signals, asset records, documents, SOPs, maintenance history, and quality checks"}),(0,s.jsx)(t.td,{children:"DFS, knowledge stores, and tool references"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Digital twin and simulation"}),(0,s.jsx)(t.td,{children:"Scene context, equipment layout, SimReady assets, and planning models for analysis or Physical AI workflows"}),(0,s.jsx)(t.td,{children:"FactVerse Designer and simulation services"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Operational execution"}),(0,s.jsx)(t.td,{children:"Runtime visualization, alerts, work orders, inspection records, and field feedback"}),(0,s.jsx)(t.td,{children:"DataMesh Inspector and customer operation systems"})]})]})]}),"\n",(0,s.jsx)(t.h2,{id:"runtime-flow",children:"Runtime flow"}),"\n",(0,s.jsxs)(t.ol,{children:["\n",(0,s.jsx)(t.li,{children:"The client connects through an MCP endpoint with a scoped credential."}),"\n",(0,s.jsx)(t.li,{children:"FactVerse resolves tenant, asset, permission, and product context before tool execution."}),"\n",(0,s.jsx)(t.li,{children:"The agent retrieves data, digital twin context, knowledge, or simulation-ready assets through governed tools."}),"\n",(0,s.jsx)(t.li,{children:"The agent produces analysis, recommendations, task drafts, or simulation requests based on the available context."}),"\n",(0,s.jsx)(t.li,{children:"Write actions such as work-order updates or operational changes stay behind approval and audit controls."}),"\n",(0,s.jsx)(t.li,{children:"Inspector and connected operation systems record the execution result so future agent work can learn from completed activity."}),"\n"]}),"\n",(0,s.jsx)(t.h2,{id:"product-responsibilities",children:"Product responsibilities"}),"\n",(0,s.jsxs)(t.table,{children:[(0,s.jsx)(t.thead,{children:(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.th,{children:"Product or service"}),(0,s.jsx)(t.th,{children:"Responsibility in Agent workflows"})]})}),(0,s.jsxs)(t.tbody,{children:[(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"FactVerse Platform"}),(0,s.jsx)(t.td,{children:"Tenant, identity, asset, permission, subscription, and shared product context"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"DFS"}),(0,s.jsx)(t.td,{children:"Data ingestion, transformation, quality checks, operational signals, and integration pipelines"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"FactVerse Designer"}),(0,s.jsx)(t.td,{children:"Digital twin scene creation, layout planning, SimReady asset preparation, and simulation-oriented authoring"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"DataMesh Inspector"}),(0,s.jsx)(t.td,{children:"Runtime visualization, alerts, inspection workflows, work orders, and field execution records"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"MCP"}),(0,s.jsx)(t.td,{children:"Governed tool discovery and access for external AI clients and enterprise agents"})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Knowledge and references"}),(0,s.jsx)(t.td,{children:"Manuals, SOPs, asset records, tool catalogs, and domain documents available to approved workflows"})]})]})]}),"\n",(0,s.jsx)(t.h2,{id:"deployment-models",children:"Deployment models"}),"\n",(0,s.jsx)(t.p,{children:"FactVerse AI Agent can support cloud, on-premises, and hybrid deployment discussions depending on customer security and integration requirements. The architecture model separates integration boundaries, governance surfaces, and product responsibilities so deployment planning can stay clear across environments."}),"\n",(0,s.jsx)(t.h2,{id:"deployment-planning-checks",children:"Deployment planning checks"}),"\n",(0,s.jsxs)(t.table,{children:[(0,s.jsx)(t.thead,{children:(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.th,{children:"Check"}),(0,s.jsx)(t.th,{children:"Decision to record"})]})}),(0,s.jsxs)(t.tbody,{children:[(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Client location"}),(0,s.jsx)(t.td,{children:"Cloud AI client, customer network client, on-prem runner, or hybrid workflow."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Endpoint exposure"}),(0,s.jsx)(t.td,{children:"Which MCP endpoints are reachable and which network controls apply."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Data residency"}),(0,s.jsx)(t.td,{children:"Which source data, documents, scene assets, and logs can leave the customer environment."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Credential owner"}),(0,s.jsx)(t.td,{children:"Who issues, rotates, and revokes API keys."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Audit retention"}),(0,s.jsx)(t.td,{children:"Where workflow run records, tool calls, and reviewer decisions are stored."})]}),(0,s.jsxs)(t.tr,{children:[(0,s.jsx)(t.td,{children:"Operations handover"}),(0,s.jsx)(t.td,{children:"Who handles failures in client config, source data, model output, and action approval."})]})]})]}),"\n",(0,s.jsx)(t.h2,{id:"design-principles",children:"Design principles"}),"\n",(0,s.jsxs)(t.ul,{children:["\n",(0,s.jsx)(t.li,{children:"Expose capabilities through scoped tools with governed product API boundaries."}),"\n",(0,s.jsx)(t.li,{children:"Keep tenant, asset, and permission context attached to every workflow."}),"\n",(0,s.jsx)(t.li,{children:"Treat digital twins as operational context with visual, data, and workflow meaning."}),"\n",(0,s.jsx)(t.li,{children:"Use simulation and planning assets where they improve reasoning quality or scenario validation."}),"\n",(0,s.jsx)(t.li,{children:"Keep human approval and audit records around actions that affect real operations."}),"\n"]})]})}function h(e={}){const{wrapper:t}={...(0,i.R)(),...e.components};return t?(0,s.jsx)(t,{...e,children:(0,s.jsx)(l,{...e})}):l(e)}},28453:(e,t,n)=>{n.d(t,{R:()=>a,x:()=>c});var r=n(96540);const s={},i=r.createContext(s);function a(e){const t=r.useContext(i);return r.useMemo(function(){return"function"==typeof e?e(t):{...t,...e}},[t,e])}function c(e){let t;return t=e.disableParentContext?"function"==typeof e.components?e.components(s):e.components||s:a(e.components),r.createElement(i.Provider,{value:t},e.children)}}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.