Current snapshot
As of September 19, 2026, O1 remains a product in development. Local expressive reactions are described as working, compact local AI is described as a working prototype, and supported vision and tool workflows are connected betas. Final production specifications, current price, general availability, and several policy details remain TBD.
The public record is strongest when it describes a narrow behavior and weakest when it tries to imply a finished commercial device. That is why the specs and feature-status ledger separates working, prototype, connected-beta, planned, browser-preview, and TBD states. The status travels with the claim; removing the label would change its meaning.
The current design identifies two esp32-s3 processors, an OLED expression display, and owner-triggered vision input. Those are design facts, not a locked retail bill of materials. No current evidence record establishes production dimensions, weight, battery specification, certifications, accessories in the box, or a manufacturer of record.
How a claim enters the public record
A statement belongs on these pages only when a current source supports the exact scope of the wording. A product-page statement can establish what Growit claims. It cannot, by itself, establish independent validation. A render can document an intended form. It cannot establish battery life, durability, production materials, scale accuracy, or shipment readiness.
- Name the claim precisely. “The face reacts locally” is different from “the whole device works offline.”
- Locate the current source. Current product, fact-sheet, legal, and policy pages take precedence over undated marketing fragments.
- Carry the qualification. Prototype, beta, planned, and TBD labels stay next to the fact.
- Check for conflicts. If two repository sources disagree, the page reports the conflict instead of choosing the more attractive claim.
- Avoid inferred precision. A component name does not prove performance; a scheduled window does not prove fulfillment.
- Date the review. Fast-changing purchase and product details need a visible review date.
What this method does not do: it is not an independent lab test, certification review, teardown, security audit, or customer review. Those forms of evidence should be published and attributed separately when they exist.
Documentation record
The dates below are verified editorial checkpoints in the repository. They should not be read as engineering completion dates or production milestones.
- September 6, 2026 — guide evidence inventory.
The buyer-guide evidence file mapped capability, purchase, privacy, return, warranty, and drop statements to first-party sources. It explicitly distinguished a hardware render from a product photograph and recorded that final production specifications were pending.
- September 19, 2026 — media fact sheet updated.
The public media summary restated the current design, local reactions, connected beta requirements, Eye World combinations, planned ownership model, and scheduled entry windows. It also kept final price, quantities, fulfillment, and production specifications subject to later announcement.
- September 19, 2026 — evidence architecture consolidated.
The public specs ledger, build log, buying guide, press room, migration record, and comparison page were moved onto one typed fact set. Unknown values are stored as null and displayed as TBD so a page cannot quietly invent them.
Future entries should describe a verifiable change: a dated specification release, a published test method and result, a policy becoming final, an independently reviewable unit, or a corrected claim. Routine copy edits should not be presented as product progress.
Media provenance is still being reconciled
The September 19 media kit labels files beginning with real- as photographs of a real O1 prototype. An earlier evidence review recorded that it had not independently verified a production photograph in the owned source set. Those two statements answer different questions—the kit gives an editorial label, while the review asks whether provenance was independently established—but the difference matters.
These pages do not use supplied media as proof of a production unit, shipment, manufacturing readiness, or final hardware. Campaign art and renders remain labeled as such. A future provenance update should identify the original file, capture context, date, device revision, and the person who can attest to it; none of those details are supplied here today.
Reporters and reviewers can use the press room for current labels and may request original-format assets or clarification at growit@growit.lol. Publication should not turn a campaign render into a documentary image or describe a prototype as a shipped production device.
Open questions that remain TBD
These are not hidden footnotes. They are the product decisions a careful buyer, reviewer, or integration partner would need before treating O1 as a final commercial device.
Hardware
Final production specification
Dimensions, weight, battery, charging, radio details, sensors, materials, certifications, accessories, and revision identifiers remain TBD.
Commercial
Price and availability
Current price, taxable total, shipping destinations and charges, order capacity, and general retail availability remain TBD.
Data
Feature-specific processing maps
Each connected beta still needs a clear description of input, processing location, retention, permissions, credential handling, and deletion controls.
Evidence
Independent verification
No independent review, benchmark, teardown, customer rating, or side-by-side device test is claimed by this record.
Sources and corrections
If a source below conflicts with a page, the page should be corrected with a dated note. If a new source is less specific than an older one, the narrower supported wording wins. Send the URL, disputed sentence, and supporting source to growit@growit.lol. A correction request is not a promise to remove a documented qualification.
- Growit O1 product page
Current first-party description of the product, feature states, and launch model.
- O1 factual media summary
Dated first-party fact sheet for reporters and reviewers.
- O1 review and creator policy
Disclosure, independence, correction, and review-loan rules.
- O1 drop rules
Entry, selection, purchase-allocation, and reserve-list mechanics.
- O1 privacy notice
Website and order privacy boundaries; device-specific explanations remain feature dependent.
- O1 returns information
Current return and cancellation information.
- O1 warranty information
Current hardware-warranty information.
- O1 purchase terms
Current first-party purchase terms; older event language should not be treated as a current offer.
- Growit founder profile
First-party profile identifying Josiah Love as the founder of Growit and JML Tech Studios.