[{"data":1,"prerenderedAt":348},["ShallowReactive",2],{"navigation_docs_en":3,"-en-overview-introduction":75,"-en-overview-introduction-surround":345},[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":10,"body":77,"description":338,"extension":339,"links":340,"meta":341,"navigation":342,"path":11,"seo":343,"stem":12,"__hash__":344},"docs_en\u002Fen\u002F1.overview\u002F1.introduction.md",{"type":78,"value":79,"toc":325},"minimark",[80,85,89,92,97,100,103,119,122,126,129,143,147,150,170,173,177,180,197,200,204,207,221,225,228,248,252,255,258,272,275,279,282,299,303],[81,82,84],"h1",{"id":83},"keero-bot","Keero Bot",[86,87,88],"p",{},"Keero Bot is a modular hardware platform for building interactive AI devices. The project combines an ESP32-S3 based mainboard with camera, audio, haptics, motion sensing, display support, and expansion interfaces for future modules.",[86,90,91],{},"The goal is not to present Keero Bot as a single-purpose board. It is positioned as a reusable system foundation for experiments where embedded intelligence needs to sense, respond, dock, move, and evolve through attached modules.",[93,94,96],"h2",{"id":95},"what-the-project-is-trying-to-become","What The Project Is Trying To Become",[86,98,99],{},"Keero Bot is being developed as a small but serious hardware platform that can grow into multiple physical product directions without starting over from scratch each time.",[86,101,102],{},"In practical terms, that means:",[104,105,106,110,113,116],"ul",{},[107,108,109],"li",{},"one compact reusable core board",[107,111,112],{},"one shared firmware direction",[107,114,115],{},"multiple physical extensions through modules",[107,117,118],{},"enough public documentation to communicate credibility and intent",[86,120,121],{},"This is why the project reads more like a platform dossier than a single board drop.",[93,123,125],{"id":124},"platform-direction","Platform Direction",[86,127,128],{},"Keero Bot is being shaped around four core ideas:",[104,130,131,134,137,140],{},[107,132,133],{},"one compact core board that concentrates the essential system functions",[107,135,136],{},"optional modules that adapt the platform to different physical use cases",[107,138,139],{},"open firmware and public architecture documentation",[107,141,142],{},"selective protection of production-ready hardware details",[93,144,146],{"id":145},"platform-capabilities","Platform Capabilities",[86,148,149],{},"At a visible public level, the current platform already points toward:",[104,151,152,155,158,161,164,167],{},[107,153,154],{},"visual sensing through a camera path",[107,156,157],{},"audio interaction with input and output hardware",[107,159,160],{},"local feedback through display and haptics",[107,162,163],{},"motion-aware interaction through sensors",[107,165,166],{},"battery-capable operation",[107,168,169],{},"dock and module expansion",[86,171,172],{},"Together, these capabilities give Keero Bot a stronger identity than a generic ESP32 carrier or development breakout.",[93,174,176],{"id":175},"what-this-documentation-covers","What This Documentation Covers",[86,178,179],{},"This public documentation is focused on:",[104,181,182,185,188,191,194],{},[107,183,184],{},"product overview and design intent",[107,186,187],{},"subsystem architecture",[107,189,190],{},"modular expansion strategy",[107,192,193],{},"prototyping readiness and partner positioning",[107,195,196],{},"firmware status and roadmap",[86,198,199],{},"It does not publish the full manufacturing package, editable board sources, or other production-critical implementation details.",[93,201,203],{"id":202},"intended-audience","Intended Audience",[86,205,206],{},"This site is written for:",[104,208,209,212,215,218],{},[107,210,211],{},"developers evaluating the platform direction",[107,213,214],{},"open-hardware followers who want architectural visibility",[107,216,217],{},"sponsors and manufacturing partners such as PCBWay",[107,219,220],{},"future collaborators working on firmware, modules, or productization",[93,222,224],{"id":223},"platform-summary","Platform Summary",[86,226,227],{},"At a high level, the current Keero Bot platform includes:",[104,229,230,233,236,239,242,245],{},[107,231,232],{},"ESP32-S3 compute core",[107,234,235],{},"managed battery and power subsystem",[107,237,238],{},"camera and display support",[107,240,241],{},"audio input and output",[107,243,244],{},"haptic and motion sensing capabilities",[107,246,247],{},"pogo-based modular expansion",[93,249,251],{"id":250},"why-the-public-version-is-selective","Why The Public Version Is Selective",[86,253,254],{},"The public release is designed to be informative without becoming a cloning package.",[86,256,257],{},"That balance matters because the project should:",[104,259,260,263,266,269],{},[107,261,262],{},"look serious to collaborators and sponsors",[107,264,265],{},"remain understandable to developers",[107,267,268],{},"keep firmware and architecture discussions open",[107,270,271],{},"avoid exposing the full production recipe of the official hardware",[86,273,274],{},"This is especially important for a project that may go through multiple prototype revisions and sponsor conversations.",[93,276,278],{"id":277},"what-a-sponsor-can-learn-quickly","What A Sponsor Can Learn Quickly",[86,280,281],{},"Someone evaluating Keero Bot for prototyping or sponsorship can already see:",[104,283,284,287,290,293,296],{},[107,285,286],{},"a coherent hardware identity",[107,288,289],{},"a documented modular roadmap",[107,291,292],{},"a practical interaction stack",[107,294,295],{},"a believable path from prototype to stronger product concept",[107,297,298],{},"evidence that documentation and firmware are evolving alongside the board",[93,300,302],{"id":301},"visual-reference","Visual Reference",[304,305,308,315,320],"div",{"className":306},[307],"keero-docs-gallery",[309,310],"img",{"alt":311,"className":312,"src":314},"Mainboard render",[313],"keero-docs-image","\u002Fkeero\u002Fimages\u002FPCB.png",[309,316],{"alt":317,"className":318,"src":319},"Top render",[313],"\u002Fkeero\u002Fimages\u002FPCB_TOP.png",[309,321],{"alt":322,"className":323,"src":324},"Bottom render",[313],"\u002Fkeero\u002Fimages\u002FPCB_BOTTOM.png",{"title":326,"searchDepth":327,"depth":327,"links":328},"",2,[329,330,331,332,333,334,335,336,337],{"id":95,"depth":327,"text":96},{"id":124,"depth":327,"text":125},{"id":145,"depth":327,"text":146},{"id":175,"depth":327,"text":176},{"id":202,"depth":327,"text":203},{"id":223,"depth":327,"text":224},{"id":250,"depth":327,"text":251},{"id":277,"depth":327,"text":278},{"id":301,"depth":327,"text":302},"High-level introduction to the Keero Bot modular AI hardware platform.","md",null,{},{"icon":13},{"title":10,"description":338},"XHd5o2_rwziLMztEal_7YIc5fID-ZI6DW9VvdJC-sTY",[340,346],{"title":15,"path":16,"stem":17,"description":347,"icon":18,"children":-1},"High-level functional architecture of the Keero Bot platform.",1775557595327]