Lens Artifact Review

Inspect the software artifacts before anyone argues about claims.

Foveo's public console is built around reviewing generated artifacts, not releasing lenses. The useful output today is a clear packet: STL, design spec, cross-section, clearance statistics, warnings, and replay identity.

Primary artifactWatertight STL preview
Machine recordDesign spec JSON
Review layerWarnings and hashes

Review Point

What reviewers can inspect

The review flow exposes the shape of the software pipeline in a way that labs and advisors can critique without needing patient data or production equipment.

Review Point

What review is not

Artifact review is not a claim that the output is clinically appropriate, manufacturable, wearable, or approved. It is a way to make the software output visible enough for serious feedback.

Review Point

What comes next

The next software work is stronger validation, scanner-neutral schema design, advisor review loops, and a safer handoff model for future collaborators.

Fast Answers

What is a lens artifact?
In Foveo, it means a generated software output such as an STL, design spec, render, metric set, warning record, or hash.
Does artifact review approve a lens for wear?
No. The public product does not approve, manufacture, dispense, fit, or release wearable lenses.
Who is the page for?
Labs, clinicians, researchers, and technical advisors who want to critique the software workflow safely.

Search Context

Useful phrases for this page

These terms describe the public software research lane. They are not medical, fitting, dispensing, manufacturing, privacy, or regulatory claims.

Start Clean

Review the artifact, not a patient case.

Send only non-confidential collaboration context. Do not send patient records, prescriptions, scans, protected health information, real lens orders, or proprietary methods.

Open the console [email protected]