[{"data":1,"prerenderedAt":250},["ShallowReactive",2],{"navigation_docs_en":3,"-en-hardware-modules-and-mechanics":75,"-en-hardware-modules-and-mechanics-surround":245},[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":41,"body":77,"description":238,"extension":239,"links":240,"meta":241,"navigation":242,"path":42,"seo":243,"stem":43,"__hash__":244},"docs_en\u002Fen\u002F2.hardware\u002F3.modules-and-mechanics.md",{"type":78,"value":79,"toc":227},"minimark",[80,84,88,93,96,109,112,115,119,122,125,136,139,143,146,149,152,156,159,163,166,180,184,187,201,205],[81,82,41],"h1",{"id":83},"modules-and-mechanics",[85,86,87],"p",{},"Keero Bot is intentionally structured as a modular system. The mainboard carries the core intelligence and interaction stack, while external modules adapt the platform to different physical roles.",[89,90,92],"h2",{"id":91},"modular-design","Modular Design",[85,94,95],{},"The public modular story is built around three ideas:",[97,98,99,103,106],"ul",{},[100,101,102],"li",{},"one reusable core board",[100,104,105],{},"compact module interfaces for fast iteration",[100,107,108],{},"accessory-specific mechanics without redesigning the entire system",[85,110,111],{},"This makes the project more attractive both to developers and to fabrication partners, because the platform can evolve in stages.",[85,113,114],{},"It also gives the hardware story more long-term value. A prototype run is more interesting when it supports a platform family rather than a single static board.",[89,116,118],{"id":117},"dock-concept","Dock Concept",[85,120,121],{},"The dock concept positions Keero Bot as more than a loose prototype board.",[85,123,124],{},"It suggests a workflow where the system can:",[97,126,127,130,133],{},[100,128,129],{},"rest in a charging base",[100,131,132],{},"expose development access more cleanly",[100,134,135],{},"support future desk or showcase experiences",[85,137,138],{},"The dock is strategically useful because it creates a more polished user journey for demos, charging, testing, and sponsor presentation.",[89,140,142],{"id":141},"tracks-concept","Tracks Concept",[85,144,145],{},"The tracks concept pushes the platform toward embodied AI and mobility experiments.",[85,147,148],{},"This is important strategically because it demonstrates that Keero Bot is not only about electronics integration. It is also about how the system behaves in physical space.",[85,150,151],{},"For PCBWay or any prototyping partner, that means the project has room for continued iteration beyond the first board revision.",[89,153,155],{"id":154},"mechanical-readiness","Mechanical Readiness",[85,157,158],{},"The current repository already shows that enclosure and module fit were considered early. That helps communicate maturity to sponsors even when detailed production mechanics are not publicly released.",[89,160,162],{"id":161},"public-module-story","Public Module Story",[85,164,165],{},"At a public documentation level, the modular story already communicates:",[97,167,168,171,174,177],{},[100,169,170],{},"a core board that can remain stable across revisions",[100,172,173],{},"a dock direction for stationary use",[100,175,176],{},"a tracks direction for motion and embodied experiments",[100,178,179],{},"space for future accessories without reinventing the entire platform",[89,181,183],{"id":182},"why-modularity-matters","Why Modularity Matters",[85,185,186],{},"For Keero Bot, modularity is not only a convenience feature. It is a product strategy:",[97,188,189,192,195,198],{},[100,190,191],{},"developers can prototype faster",[100,193,194],{},"the hardware narrative becomes easier to understand",[100,196,197],{},"the same core platform can support multiple demos and sponsor conversations",[100,199,200],{},"firmware work can scale across more than one physical configuration",[89,202,204],{"id":203},"preview-images","Preview Images",[206,207,210,217,222],"div",{"className":208},[209],"keero-docs-gallery",[211,212],"img",{"alt":213,"className":214,"src":216},"Keero hero image",[215],"keero-docs-image","\u002Fkeero\u002Fimages\u002Fhero.png",[211,218],{"alt":219,"className":220,"src":221},"PCB top view",[215],"\u002Fkeero\u002Fimages\u002FPCB_TOP.png",[211,223],{"alt":224,"className":225,"src":226},"PCB bottom view",[215],"\u002Fkeero\u002Fimages\u002FPCB_BOTTOM.png",{"title":228,"searchDepth":229,"depth":229,"links":230},"",2,[231,232,233,234,235,236,237],{"id":91,"depth":229,"text":92},{"id":117,"depth":229,"text":118},{"id":141,"depth":229,"text":142},{"id":154,"depth":229,"text":155},{"id":161,"depth":229,"text":162},{"id":182,"depth":229,"text":183},{"id":203,"depth":229,"text":204},"High-level description of the Keero Bot modular hardware strategy and current physical concepts.","md",null,{},{"icon":44},{"title":41,"description":238},"C_DRhIlxlN77CKNsmnf8CxXJl1QclynLQasJooiJcmk",[246,248],{"title":36,"path":37,"stem":38,"description":247,"icon":39,"children":-1},"High-level view of how Keero Bot approaches power, docking, and subsystem communication.",{"title":46,"path":47,"stem":48,"description":249,"icon":49,"children":-1},"Public-facing manufacturing posture, prototyping readiness, and partner positioning for the Keero Bot platform.",1775557595696]