[{"data":1,"prerenderedAt":269},["ShallowReactive",2],{"navigation_docs_en":3,"-en-overview-partnership-and-prototyping":75,"-en-overview-partnership-and-prototyping-surround":264},[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":20,"body":77,"description":257,"extension":258,"links":259,"meta":260,"navigation":261,"path":21,"seo":262,"stem":22,"__hash__":263},"docs_en\u002Fen\u002F1.overview\u002F3.partnership-and-prototyping.md",{"type":78,"value":79,"toc":247},"minimark",[80,84,88,93,96,115,118,122,125,139,142,146,149,163,166,170,173,190,193,197,200,217,220,224,227,244],[81,82,20],"h1",{"id":83},"partnership-and-prototyping",[85,86,87],"p",{},"Keero Bot is documented as a real hardware platform rather than a loose concept. That makes it easier for sponsors, fabrication partners, and technical collaborators to evaluate where the project stands and how it can grow.",[89,90,92],"h2",{"id":91},"why-the-project-is-a-good-fit","Why The Project Is A Good Fit",[85,94,95],{},"From a partner perspective, the platform already shows several positive signals:",[97,98,99,103,106,109,112],"ul",{},[100,101,102],"li",{},"a defined mainboard rather than only loose module ideas",[100,104,105],{},"clear system architecture and interaction direction",[100,107,108],{},"reusable modular expansion strategy",[100,110,111],{},"firmware work already in motion",[100,113,114],{},"public documentation that explains the platform in a structured way",[85,116,117],{},"This combination helps communicate that Keero Bot is not only visually interesting. It has technical direction, prototyping intent, and room for iterative manufacturing support.",[89,119,121],{"id":120},"why-pcbway-is-relevant","Why PCBWay Is Relevant",[85,123,124],{},"PCBWay is a natural fit for a project like Keero Bot because the platform benefits from:",[97,126,127,130,133,136],{},[100,128,129],{},"repeatable prototype PCB manufacturing",[100,131,132],{},"early assembly feedback",[100,134,135],{},"support for iterative revisions",[100,137,138],{},"credible presentation for future demos and product exploration",[85,140,141],{},"For a modular embedded system, reliable prototyping matters just as much as the design concept itself.",[89,143,145],{"id":144},"what-a-hardware-sponsor-can-validate","What A Hardware Sponsor Can Validate",[85,147,148],{},"Even without full production files, a sponsor can still evaluate several useful things here:",[97,150,151,154,157,160],{},[100,152,153],{},"whether the platform has a coherent subsystem breakdown",[100,155,156],{},"whether the product direction is clear enough to justify prototype support",[100,158,159],{},"whether the project is structured for iteration instead of one single board run",[100,161,162],{},"whether the documentation quality matches a serious hardware effort",[85,164,165],{},"That kind of visibility is often enough for an initial sponsorship discussion.",[89,167,169],{"id":168},"what-public-docs-show","What Public Docs Show",[85,171,172],{},"The public documentation is designed to provide enough visibility for evaluation:",[97,174,175,178,181,184,187],{},[100,176,177],{},"overall platform purpose",[100,179,180],{},"subsystem-level architecture",[100,182,183],{},"module strategy",[100,185,186],{},"prototyping posture",[100,188,189],{},"roadmap and current status",[85,191,192],{},"This allows meaningful sponsor review without turning the website into a replication package.",[89,194,196],{"id":195},"what-stays-private","What Stays Private",[85,198,199],{},"To protect the project and keep the release balanced, some material is not published openly:",[97,201,202,205,208,211,214],{},[100,203,204],{},"fabrication packages",[100,206,207],{},"full assembly outputs",[100,209,210],{},"editable hardware source exports",[100,212,213],{},"unrestricted production BOM data",[100,215,216],{},"exact production-ready implementation details",[85,218,219],{},"That boundary is intentional. It keeps the hardware understandable, but not trivially clonable.",[89,221,223],{"id":222},"collaboration-direction","Collaboration Direction",[85,225,226],{},"If Keero Bot moves into deeper sponsor or manufacturing collaboration, the most relevant conversations would be around:",[97,228,229,232,235,238,241],{},[100,230,231],{},"prototype quality",[100,233,234],{},"iteration speed",[100,236,237],{},"assembly readiness",[100,239,240],{},"bring-up support",[100,242,243],{},"future module expansion",[85,245,246],{},"This is the level at which the project is best positioned for partner discussion today.",{"title":248,"searchDepth":249,"depth":249,"links":250},"",2,[251,252,253,254,255,256],{"id":91,"depth":249,"text":92},{"id":120,"depth":249,"text":121},{"id":144,"depth":249,"text":145},{"id":168,"depth":249,"text":169},{"id":195,"depth":249,"text":196},{"id":222,"depth":249,"text":223},"Why Keero Bot is a strong fit for prototyping partners and hardware sponsors.","md",null,{},{"icon":23},{"title":20,"description":257},"-VQgroip6wTIlnzdVE0VdeSO2kVIKMbECsIb5bAbvyA",[265,267],{"title":15,"path":16,"stem":17,"description":266,"icon":18,"children":-1},"High-level functional architecture of the Keero Bot platform.",{"title":31,"path":32,"stem":33,"description":268,"icon":34,"children":-1},"High-level overview of the Keero Bot mainboard and its role in the overall platform.",1775557595327]