Movement
A person enters the field of view.
YPAI AI DATA & EVALUATION
VIDEO DATA
Spatial intelligence begins with the real world.
Video data for AI systems that need to perceive people, motion and context as they happen.
THE SEQUENCE
A frame tells you where.
A sequence tells you why.
Useful video data preserves the change between moments, so a model can learn what happened, in context.
Context
The space changes the meaning of the movement.
Intent
The sequence makes the decision legible.
PROJECT RECORD Collection configured
Cohort, environment, capture mode and review plan are now attached.
COLLECTION AT SCALE
Designed around the data your model is missing.
A collection project can be shaped around cohort, geography, environment, capture mode and device configuration, then carried through automated checks, human review, reshoot and delivery.
- Coverage field
- Cohort / geography / environment
- Capture modes
- Remote / moderated / in-person
- Configuration
- Device / framing / sensor / metadata
- Project design Turn the requirement into a workable cohort and capture plan.
- Review loop Automated checks and human review identify recapture or rework.
- Delivery record Accepted media leaves with metadata, checksums and manifest structure.
PROJECT RECORD Project family routed
The same requirement moves into the operating family that matches its capture and evaluation reality.
THE VIDEO SPECTRUM
Seven project families. One connected operating standard.
Start with the model behaviour, the capture reality or the dataset problem. The project family follows from that requirement.
- Large-scale collection Distributed capture
Cohorts, quotas, QC and reshoot
- On-camera speech Visible speakers
Isolated tracks, waveform and timecode
- Physical AI Task episodes
Egocentric context, sensors and outcomes
- Human motion Action through time
Gesture, pose and temporal review
- Face video Controlled variation
Consent, withdrawal and identity traceability
- Video annotation and evaluation Temporal understanding
Ontology, tracks, review and quality report
- Video integrity Media authenticity
Source evidence, taxonomy and benchmark packaging
PROJECT RECORD Rights attached
Source basis, use scope, lineage and customer boundary move with the record.
RIGHTS ATTACHED
The right to use the data travels with the data.
Each project defines its applicable rights scope. The operational record keeps that scope connected to source, asset and delivery.
ASSET RECORD Source to delivery lineage
The media, its transformations and its permitted-use scope remain part of one traceable record.
- Participant or source basis
- The record identifies the participant, source and project-specific basis for collection or use.
- Applicable basis
- Consent, release, licence or another applicable project basis is recorded where the engagement requires it.
- Permitted use or release
- The agreed permitted-use or release scope stays attached to the relevant asset and delivery record.
- Lineage
- Transforms and derivatives retain their connection to the source record.
- Withdrawal or deletion path
- Project requirements for removal or deletion can be carried into the operating workflow.
- Customer isolation
- Customer media, derivatives and delivery records remain isolated within the agreed engagement boundary.
PROJECT RECORD Accept or return
Each item advances with evidence or returns to capture and rework with a reason.
ACCEPTANCE BEFORE SCALE
Define the gate before production begins.
Technical validation and human review test the same agreed specification. A failed item returns with a reason. An accepted item advances with evidence.
- Specification What must be true
- Technical validation Media and metadata checks
- Human review Context and requirement fit
- Acceptance gate Accept or reject with reason
- Evaluation Advance to final package
REJECTED ITEM
Reason and evidence return to capture, reshoot or rework.
PROJECT RECORD Package versioned
Accepted media, records, checksums and delivery version become one inspectable handover.
VERSIONED HANDOVER
The footage is only one part of the delivery.
The final package can carry the media and the records needed to inspect, accept and version the handover.
DELIVERY MANIFEST One package. Connected records.
Scope determines the exact contents of each engagement.
- Accepted video assets
- Technical metadata
- Annotation outputs
- Rights and provenance record
- Quality and acceptance report
- Checksums and manifest
- Delivery and version record
PROJECT RECORD Requirement exchanged
The delivery record becomes the basis for the next scoped project decision.
START WITH THE SPECIFICATION
Bring the footage problem. Leave with a project shape.
A useful first conversation establishes enough scope to choose the operating path, pilot and acceptance approach.
You bring
- Model or product use case
- Target modality and scenario
- Geography, language or cohort
- Approximate scale and timeline
- Technical and metadata needs
- Rights, annotation and acceptance scope
YPAI returns
- Project architecture
- Pilot scope
- Capture or sourcing plan
- QA and review architecture
- Output and delivery structure
- Acceptance proposal
Pilot scope and commercial terms are agreed for the engagement.
PROJECT RECORD Next project
The operational spine returns to a real-world requirement.
Bring the real-world video problem. YPAI designs the collection, annotation or evaluation around it.