Repository, creator page, manual, parts list, files, dimensions, published cost and instructions.
Understand the evidence behind the verdict.
Use this page to interpret project status, difficulty, AI help, costs and source quality. For what CAIBI is and who it helps, start with About.
What is CAIBI? →Proposed ways to develop an idea, or an assessment of an existing build. Each page states what has been checked and what still needs testing.
Actual build time, cost, changes, failures, substitutions and finished results from people who tried it.
Guidance, assessment and a physical build are different.
CAIBI helps identify what is missing between a promising source and an object you can use. We propose practical stages, prompts for firmware and measured enclosures, and checks for the result. These additions remain proposals until tested.
A starting point with source links and an idea to develop. Parts, instructions and feasibility may still be incomplete.
Explore the ideas board →A proposed completion route with parts to confirm, prompts and test criteria. Guidance ready does not mean assessed, physically built or guaranteed to work.
Read a guided build →An editorial assessment of the published evidence, costs and trade-offs. It may exist without a CAIBI hands-on build.
Compare project assessments →A separate tick for a physical build we have made and documented against a named version, with photos and recorded checks. It applies to that version and test scope, not every adaptation or use.
An idea, design, code finding or first-hand build report from a contributor. An incomplete attempt can help develop the next version. A published report does not become CAIBI verification.
Help develop an idea →A link is not an assessment.
A potentially useful physical project or source is discovered.
The original material is checked for substance, files and build evidence.
There is enough evidence to justify deeper CAIBI work.
The public build route, evidence trail and verdict are published.
What the labels do and do not tell you
An editorial indication of the build's demands, with 5 representing the most demanding end. Read the named skills, alignment, assembly and testing requirements. It is not a measured success rate or a personalised rating.
An editorial indication of where AI assistance is useful, with 5 representing more scope for assistance. It does not mean the project is easy or that AI can perform the physical work. Read the specific tasks and boundaries.
Build it, consider it, build for the experience or buy instead describe the assessed route and its trade-offs. Read the reasoning and comparison. A verdict is not a guarantee, certification or customer star rating.
Check whether tools, delivery, taxes, consumables, outsourced work and optional parts are included. A partial bill of materials is not an all-in estimate. Unknown cost does not mean free.
A named finished product may differ in features, assembly, warranty and availability. A price difference alone is not a saving. Read the comparison's scope, date and missing costs.
A checked date records a review, not a promise of today's price or stock. Currency conversion is an estimate, not a regional seller quote. Open the linked source before purchasing.
What a complete project page should answer
Is this worth building, considering, learning from, buying instead or avoiding?
Useful prompts and assistance grounded in the source rather than invented build facts.
Research, code, CAD reasoning, configuration, troubleshooting and documentation where appropriate.
The physical actions, measurements, calibration and verification that still need a person.
How the thing actually comes together and which steps belong to AI, the builder or both.
What is required, what can be substituted and which capabilities can be outsourced.
Other ways to reach the same outcome, including buying, outsourcing or choosing another project.
Repos, guides and supporting evidence beyond the original source where they add something useful.
Completed public builds, repos, maker pages and listings when reviewed evidence exists.
One review never becomes the verdict.
Specification, manuals, regional model, warranty and current buying route.
At least three exact-model independent sources where available, with disagreement retained.
Recurring reliability, maintenance, software or support patterns when the evidence is credible.
Who it is for, where it sits against alternatives and whether the full system cost makes sense.
Know what has actually been checked.
An assessment can be based on published evidence without a CAIBI hands-on build. Only explicit first-hand reports establish what that builder did. A discovery record is a useful lead, not a completed assessment; provisional equipment coverage has a weaker evidence base than a fully supported comparison.
Source changes, unavailable files, new revisions and conflicting reports can change the conclusion. If a cost, link or claim is wrong, send the page URL, the correction and its source. A report is reviewed before it becomes public evidence.
Report a correction → · Share first-hand build evidence →Provisional stays provisional when the evidence pool is weak.
Conflicting reviews are shown as conflicting reviews.
Small datasets do not become trends because a chart would look good.
If the source does not establish it, CAIBI labels it as an assumption or leaves it unclaimed.