[{"data":1,"prerenderedAt":342},["ShallowReactive",2],{"navigation_docs_en":3,"-en-overview-system-architecture":75,"-en-overview-system-architecture-surround":337},[4,25,65],{"title":5,"path":6,"stem":7,"children":8,"page":24},"Overview","\u002Fen\u002Foverview","en\u002F1.overview",[9,14,19],{"title":10,"path":11,"stem":12,"icon":13},"Introduction","\u002Fen\u002Foverview\u002Fintroduction","en\u002F1.overview\u002F1.introduction","i-lucide-home",{"title":15,"path":16,"stem":17,"icon":18},"System Architecture","\u002Fen\u002Foverview\u002Fsystem-architecture","en\u002F1.overview\u002F2.system-architecture","i-lucide-workflow",{"title":20,"path":21,"stem":22,"icon":23},"Partnership and Prototyping","\u002Fen\u002Foverview\u002Fpartnership-and-prototyping","en\u002F1.overview\u002F3.partnership-and-prototyping","i-lucide-handshake",false,{"title":26,"path":27,"stem":28,"children":29,"page":24},"Hardware","\u002Fen\u002Fhardware","en\u002F2.hardware",[30,35,40,45,50,55,60],{"title":31,"path":32,"stem":33,"icon":34},"Mainboard","\u002Fen\u002Fhardware\u002Fmainboard","en\u002F2.hardware\u002F1.mainboard","i-lucide-circuit-board",{"title":36,"path":37,"stem":38,"icon":39},"Power and Interconnect","\u002Fen\u002Fhardware\u002Fpower-and-signals","en\u002F2.hardware\u002F2.power-and-signals","i-lucide-battery",{"title":41,"path":42,"stem":43,"icon":44},"Modules and Mechanics","\u002Fen\u002Fhardware\u002Fmodules-and-mechanics","en\u002F2.hardware\u002F3.modules-and-mechanics","i-lucide-box",{"title":46,"path":47,"stem":48,"icon":49},"Manufacturing and Prototyping","\u002Fen\u002Fhardware\u002Fmanufacturing-files","en\u002F2.hardware\u002F4.manufacturing-files","i-lucide-file-stack",{"title":51,"path":52,"stem":53,"icon":54},"Module Interfaces","\u002Fen\u002Fhardware\u002Fconnector-map","en\u002F2.hardware\u002F5.connector-map","i-lucide-plug",{"title":56,"path":57,"stem":58,"icon":59},"Use Cases","\u002Fen\u002Fhardware\u002Forder-and-build","en\u002F2.hardware\u002F6.order-and-build","i-lucide-package-check",{"title":61,"path":62,"stem":63,"icon":64},"Board Viewer","\u002Fen\u002Fhardware\u002Finteractive-bom","en\u002F2.hardware\u002F7.interactive-bom","i-lucide-box-select",{"title":66,"path":67,"stem":68,"children":69,"page":24},"Firmware","\u002Fen\u002Ffirmware","en\u002F3.firmware",[70],{"title":71,"path":72,"stem":73,"icon":74},"Status and Roadmap","\u002Fen\u002Ffirmware\u002Fstatus-and-roadmap","en\u002F3.firmware\u002F1.status-and-roadmap","i-lucide-code-xml",{"id":76,"title":15,"body":77,"description":330,"extension":331,"links":332,"meta":333,"navigation":334,"path":16,"seo":335,"stem":17,"__hash__":336},"docs_en\u002Fen\u002F1.overview\u002F2.system-architecture.md",{"type":78,"value":79,"toc":318},"minimark",[80,84,88,93,106,109,113,116,119,135,138,142,145,148,165,168,171,175,178,192,195,198,202,205,208,219,222,225,229,232,235,249,252,255,259,262,280,283,287,290,293,304,307],[81,82,15],"h1",{"id":83},"system-architecture",[85,86,87],"p",{},"Keero Bot is organized as a small set of clear functional blocks rather than a single monolithic board story. This makes the platform easier to understand, easier to extend, and easier to position for prototyping partners.",[89,90,92],"h2",{"id":91},"block-level-view","Block-Level View",[94,95,98],"div",{"className":96},[97],"keero-docs-embed",[99,100],"img",{"alt":101,"className":102,"src":105},"Keero block architecture",[103,104],"keero-docs-image","keero-docs-image--wide","\u002Fkeero\u002Fimages\u002Fblock_architecture.png",[85,107,108],{},"This is the simplest public way to understand the system: one mainboard core, one firmware layer coordinating it, one interaction stack, one power story, and one modular expansion path.",[89,110,112],{"id":111},"_1-mainboard-core","1. Mainboard Core",[85,114,115],{},"The mainboard is the central hardware layer of the platform. It brings together compute, power management, sensing, wired interfaces, and module connectivity in one reusable core.",[85,117,118],{},"From a system perspective, the mainboard is responsible for:",[120,121,122,126,129,132],"ul",{},[123,124,125],"li",{},"hosting the ESP32-S3 compute core",[123,127,128],{},"coordinating local peripherals",[123,130,131],{},"managing power across the device",[123,133,134],{},"exposing interfaces to external modules",[85,136,137],{},"This is important for Keero Bot because the project needs one stable hardware center that can survive across multiple enclosure, dock, and mobility concepts.",[89,139,141],{"id":140},"_2-interaction-layer","2. Interaction Layer",[85,143,144],{},"Keero Bot is designed around real-world interaction rather than pure compute.",[85,146,147],{},"The public hardware story includes support for:",[120,149,150,153,156,159,162],{},[123,151,152],{},"camera-based perception",[123,154,155],{},"microphone and speaker paths",[123,157,158],{},"haptic feedback",[123,160,161],{},"user input and motion sensing",[123,163,164],{},"display output for local feedback",[85,166,167],{},"Together, these pieces position the platform as an embodied AI device rather than a conventional development board.",[85,169,170],{},"From a product-story perspective, this interaction layer is what makes the project immediately understandable to both developers and sponsors.",[89,172,174],{"id":173},"_3-power-and-mobility-layer","3. Power and Mobility Layer",[85,176,177],{},"The system is intended for portable and dockable use cases. Publicly, that means the architecture includes:",[120,179,180,183,186,189],{},[123,181,182],{},"battery-powered operation",[123,184,185],{},"managed charging behavior",[123,187,188],{},"dock-oriented connectivity",[123,190,191],{},"support for mobility-oriented modules such as tracks",[85,193,194],{},"The detailed rail implementation stays private, but the public system design clearly communicates that power was treated as a first-class part of the platform.",[85,196,197],{},"That matters because serious portable hardware has to be designed around real operational modes, not only a lab-bench power story.",[89,199,201],{"id":200},"_4-modular-expansion-layer","4. Modular Expansion Layer",[85,203,204],{},"Modularity is one of the defining parts of Keero Bot.",[85,206,207],{},"The platform is designed so that:",[120,209,210,213,216],{},[123,211,212],{},"the mainboard remains the reusable brain",[123,214,215],{},"external modules add form factor or capability changes",[123,217,218],{},"pogo contacts and board-level expansion interfaces support iteration without redesigning the full system",[85,220,221],{},"This is especially important for future docking, mobility, and accessory experiments.",[85,223,224],{},"Modularity is also a strong sponsor-facing signal because it suggests repeated prototype value instead of a one-off fabrication run.",[89,226,228],{"id":227},"_5-firmware-layer","5. Firmware Layer",[85,230,231],{},"Firmware is the orchestration layer that turns the board into a coherent product platform.",[85,233,234],{},"Its long-term role is to:",[120,236,237,240,243,246],{},[123,238,239],{},"initialize and coordinate hardware subsystems",[123,241,242],{},"manage interaction behavior",[123,244,245],{},"support module-specific functionality",[123,247,248],{},"provide the bridge to AI logic and connected services",[85,250,251],{},"Public docs keep firmware more open than hardware production data, which supports community understanding without exposing the full manufacturing recipe.",[85,253,254],{},"This asymmetric openness is intentional. Firmware benefits from openness, while production-ready hardware assets benefit from more control.",[89,256,258],{"id":257},"architecture-at-a-glance","Architecture At A Glance",[85,260,261],{},"If Keero Bot is read as a layered system, the stack is:",[263,264,265,268,271,274,277],"ol",{},[123,266,267],{},"mainboard hardware core",[123,269,270],{},"interaction peripherals",[123,272,273],{},"portable and docked power behavior",[123,275,276],{},"modular accessories and attachments",[123,278,279],{},"firmware orchestration",[85,281,282],{},"That structure is simple enough to communicate clearly and rich enough to support future demos, iterations, and partner discussions.",[89,284,286],{"id":285},"public-disclosure-boundary","Public Disclosure Boundary",[85,288,289],{},"This architecture page is intentionally high level.",[85,291,292],{},"It explains:",[120,294,295,298,301],{},[123,296,297],{},"what the system does",[123,299,300],{},"how the major blocks relate",[123,302,303],{},"why the design is credible",[85,305,306],{},"It intentionally avoids:",[120,308,309,312,315],{},[123,310,311],{},"exact PCB implementation details",[123,313,314],{},"low-level signal maps for replication",[123,316,317],{},"full manufacturing or sourcing instructions",{"title":319,"searchDepth":320,"depth":320,"links":321},"",2,[322,323,324,325,326,327,328,329],{"id":91,"depth":320,"text":92},{"id":111,"depth":320,"text":112},{"id":140,"depth":320,"text":141},{"id":173,"depth":320,"text":174},{"id":200,"depth":320,"text":201},{"id":227,"depth":320,"text":228},{"id":257,"depth":320,"text":258},{"id":285,"depth":320,"text":286},"High-level functional architecture of the Keero Bot platform.","md",null,{},{"icon":18},{"title":15,"description":330},"QwkI6hz9WEbH9g8Fo4uRy6EC3-wP6WiEi5eCd9_PIy4",[338,340],{"title":10,"path":11,"stem":12,"description":339,"icon":13,"children":-1},"High-level introduction to the Keero Bot modular AI hardware platform.",{"title":20,"path":21,"stem":22,"description":341,"icon":23,"children":-1},"Why Keero Bot is a strong fit for prototyping partners and hardware sponsors.",1775557595672]