Get startedModels · Frontier model work
Commission The Vision Lab
Ask Score to build a frontier or unusually complex visual model when existing foundations are insufficient.
Source reviewed 2026-09-16. Availability depends on your installation, permissions, and compatible runtimes. A supported path is not a guarantee of model quality or production readiness.
Outcome
Turn a demanding outcome and acceptance contract into an evaluated production artifact.
Start here
What you need to know first
Check the inputs below before starting. If you are new, begin with the first-project guide. A dataset holds media and labels; a model produces results; a deployment makes a selected model version callable. Creating one does not create the others.
Bring these inputs
- — A precise product brief
- — Data access, constraints, baseline, and acceptance contract
Expected output and limits
- — Experimental evidence and a selected architecture
- — An evaluated production artifact and handoff package
Core workflow
Create a vision brief
Describe the operational outcome, domain, constraints, and available evidence.
Define acceptance
Set target metrics, critical slices, runtime limits, and deployment environment.
Track the commission
Review milestones, evidence requests, experiments, and evaluation history.
Accept the delivered model
Approve an evaluated version and attach it to a production workflow.
What this surface supports
Frontier architecture work
Complex multimodal systems
Evaluation contracts
Production handoff
Expert section
Contracts, signals, and failure modes
Use this section when you are defining acceptance criteria, automating the surface, or reviewing whether its output is safe to promote downstream.
Quality and operating signals
- — Delta against the agreed baseline
- — Critical-slice quality
- — Runtime feasibility
- — Reproducibility and operational cost
Common failure modes
- — Ambiguous acceptance criteria
- — Insufficient representative evidence
- — Research success without production feasibility
Expert release checklist
□ Inputs and dependencies are pinned to immutable versions.
□ Acceptance metrics include critical classes and operating slices.
□ Failure, retry, cost, and rollback behavior are understood.
□ The resulting artifact has an owner and a downstream review path.
Engineering safeguards
- — Acceptance criteria precede delivery
- — Evidence history stays attached
- — Deployment is a separate approval