Cobalt Labs
Computer vision workflows, made inspectable before they are trusted
Cobalt turns open vision research into reviewable product workflows. The public demo is fixture-backed: synthetic/sample input, no customer data, no cloud calls, no account, no paid service, and no live inference.
package_exception_review_v1
review required
- mode
- demo_fixture
- artifact files
- 7
- human review
- required
mission
Close the gap between open vision research and visual workflows a business or developer can inspect.
Cobalt Labs studies package exception review, missing-label review, shelf checks, and field-photo review paths where evidence, structured outputs, review state, privacy boundaries, and handoff artifacts stay inspectable before any model-backed route is introduced.
Public demo
A small surface with explicit boundaries
Featured Cobalt initiatives
From source review to inspectable demo packets
Cobalt Inspect
A browser-only fixture workflow for reviewing detections, evidence overlays, status, counts, and JSON output.
Package exception review
The first workflow path focuses on damaged packages and missing labels using deterministic sample scenes.
Model-candidate source review
Labs records candidate routes and caveats without presenting the public demo as an active model route.
research note
RF-DETR Small adapter candidate
Candidate note: the public demo does not use this model route, customer data, measured package-review accuracy, or a production workflow.
Evidence needed for a model route
A model route would need owned or licensed images, labels, hashes, raw outputs, overlays, review notes, and repeatable evidence.
Boundary: this page is a fixture-backed educational demo with synthetic/sample input, no uploads, no customer data, and no live inference route.
Cobalt Inspect
Run the fixture-backed inspection workflow
Select a sample case, run the deterministic demo check, review each detection, then copy or export the local handoff packet for inspection.
Structured result
Ready for fixture run
Run the demo to generate deterministic fixture output and local artifacts.
0
primary flags
0
detections
7
artifact files
Reviewer corrections
{}
After the run
Choose what to inspect next
Run a fixture to see what the sample packet proves, what it does not prove, and which artifact to inspect next.
- Fixture response and review state appear after a local run.
- No live model output, customer workflow, or production use is shown here.
- Run the fixture, then inspect manifest, review, overlay, and workflow packet files.
Local decision packet
Export handoff packet
Run the package fixture to produce request, result, review, manifest, overlay metadata, overlay SVG, and workflow packet files.
Shows the fixture case, mode, query, review outcome, counts, detections, and review requirement.
Preserves confirmed, rejected, or pending detections with overlay metadata and a synthetic SVG scene.
Documents the local packet a developer would inspect; no live route is active here.
Local fixture export only: synthetic/sample input, no customer data, no cloud calls, no account, no paid service, and no live model inference.
Artifact Packet Explorer
Inspect the local decision packet
Fixture artifact explorer only: synthetic/sample input, no customer data, no cloud calls, no account, no paid service, and no live model inference.
Decision trace
- Run the fixture to populate the packet explorer.
Packet pending
Run a fixture to inspect artifact roles, fields, and caveats.
Selected artifact lens
No artifact selected
Run the fixture, then choose an artifact row to inspect role, fields, and local limits.
What the demo shows
Shows after run
Fixture response, review state, and packet shape can be inspected in this browser.
Not shown here
No customer workflow, live route output, model-backed output, measured performance, or production workflow is shown here.
No-data workflow checklist
Prepare a private evaluation without sending Cobalt anything
Use this checklist in your own workspace. This public page has no upload, account, payment, contact, or customer-data flow.
Define the human decision a visual workflow would support before any model route exists.
Use only owned or licensed examples later, with labels, hashes, and sensitivity notes.
Define what counts as confirmed, rejected, or still needing review.
Expect request, result, review, manifest, overlay metadata, overlay SVG, and workflow packet files.
Do not upload or send customer data from this public page.
Business workflow view
How a business would plug the inspection step into an existing process
The public demo shows where request data, review corrections, and exported artifacts would sit inside a larger operating workflow. It does not connect to customer systems.
Capture receiving photos
Use dock photos already taken during receiving or fulfillment checks.
Flag package damage
Return exception boxes, count, confidence, and review-required status.
Confirm real damage
Reviewer rejects tape glare, labels, or shadows that look like damage.
Hold or release package
Send confirmed exceptions to receiving review before inventory handoff.
Evidence boundary for a real workflow
Copyable review packet
Research and product notes
What Cobalt is making visible
From Open Vision Models to Useful Visual Checks
Cobalt's thesis is that a visual model route only becomes useful when its inputs, review state, output schema, evidence, and handoff packet are inspectable by non-specialists.
Read the candidate posturePublic demo updates
The demo now highlights local artifacts, review corrections, overlay metadata, fixture boundaries, and Labs context in one public page.
View updatesCandidate posture for package exception review
Detector, comparison, and auxiliary routes are tracked as research notes only. None power the public demo.
See candidate groupsLocal decision packet and file map
The fixture runner exports request, result, review, manifest, overlay metadata, overlay SVG, and workflow packet data.
Inspect packetCobalt Labs
Research notes for model candidates under evaluation
Labs is tracking how open vision model families could support candidate local adapters. These are research notes. They are not active routes in the public demo and do not claim model quality, operational use, or suitability for customer data.
RF-DETR Small adapter candidate
Candidate note: the public demo does not use this model route, customer data, measured package-review accuracy, or a production workflow.
Source-reviewed candidate contextRF-DETR, D-FINE, RT-DETRv2
Detector routes for controlled package-scene research once Cobalt has permitted images, labels, repeatable evaluation fixtures, and adapter evidence.
Grounding DINO base, OWLv2
Comparison routes for open-vocabulary prompts and label discovery work. Cobalt has not promoted either route into this public Inspect workflow.
SAM 2.1, Florence-2, PaddleOCR-VL
Support routes for segmentation, visual-language grounding, and text-region review. These remain candidate context until Cobalt has data rights, labels, repeatable outputs, and review evidence.
DINO-X, Qwen2.5-VL-3B, Depth Anything V2 Large
These routes are useful context but are not active in the fixture-backed package demo.
Evidence before any model-backed route
A promoted adapter needs Cobalt-owned or licensed images, labels, hashes, raw outputs, overlay evidence, reviewer notes, repeatable metrics, and review evidence. Until then, this site stays fixture-only.
Updates
Public demo updates
Demo flow is easier to inspect
The primary journey now reads as Run fixture demo, Review detections, Export handoff packet, with the local-only caveat next to export actions.
Labs context is visible on the page
Model candidates are grouped as research notes, with explicit caveats that they do not power the public demo.
Research remains separate from fixture behavior
The page now separates fixture-backed behavior from candidate adapter work that still needs owned data, labels, repeatable evidence, and review evidence.
Developers
Workflow fit preview
A compact local mapper for reasoning about a workflow shape before customer data, uploads, accounts, or cloud integration.
Suggested review path
Inspection Workflow Review
Fit score
Strong
Manual load
16.7 hr/week
Sample target
80 images
- Technical starting point
- Candidate detector route plus optional segmentation review.
- First deliverable
- A reviewed demo shape with failure cases documented.
- Success metric
- Define a measurable review target before any real workflow evidence.
- Evidence scope
- Map the workflow on 80 representative examples and define the first measurable review rule.
Inspect workflow
Use the fixture demo to define the decision a reviewer makes today, then inspect the artifact packet.
Evidence boundary
Evidence needed for a model route
Data rights
Images must be Cobalt-owned or licensed, with clear labels, hashes, and permitted use.
Repeatable outputs
Raw results, overlays, review notes, and packet files must reproduce under local checks.
Review corrections
Human corrections need to be first-class outputs, not hidden notes outside the workflow packet.
Public boundary
Public copy must match evidence and avoid broad model, customer, or operational claims.
FAQ
Boundaries for the public demo
Is this live model inference?
No. The public workflow uses deterministic demo_fixture outputs and synthetic/sample input.
Can I provide customer media?
No. This public page accepts no media submission and asks for no customer data.
What is Cobalt Labs?
Cobalt Labs is the research track for turning open vision work into inspectable local workflows with reviewable evidence and controlled claims.
What would make this model-backed?
Cobalt would need permitted images, labels, repeatable local outputs, overlay evidence, reviewer notes, metrics, and review evidence before presenting a model-backed route.
Does this show production use?
No. This page shows a local fixture workflow for product exploration, not a production workflow.
Can I buy or upload here?
No. The public page has no upload, account, payment, contact, or customer-data flow.
Next step
Inspect the workflow before trusting it
Start with the deterministic fixture, review the evidence overlay, and export the packet. That is the public product surface unless Cobalt can support a model route with evidence.