Dataset design
The recording is only the visible layer
Pangeanic structures egocentric video programs around explicit capture protocols and acceptance rules. Before collection scales, the protocol defines what participants must do, which viewpoints and devices are required, how multiple cameras are synchronized, what must remain visible, which metadata travels with every recording, and what causes footage to be rejected or recollected.
01 · Task ontology
Activities with defined boundaries
Tasks and subtasks are defined before collection begins, including start and end conditions, objects, tools, expected outcomes, permitted variations, interruptions, and failure cases.
02 · Capture architecture
Viewpoint, device, and camera configuration
Programs can specify head mounted, chest mounted, wrist, handheld, mobile, robot mounted, or multi camera configurations together with camera position, orientation, resolution, frame rate, field of view, recording duration, and environmental conditions.
03 · Synchronization
Multiple viewpoints aligned in time
Where the model requires coordinated perspectives, collection can include synchronized cameras and associated audio or sensor streams. The protocol defines timing tolerance, recording start and stop behavior, file relationships, and synchronization validation.
04 · Audio and narration
Language connected to visible action
Narration can be captured while a task unfolds or added afterward. The choice depends on whether the model needs concurrent reasoning, natural verbalization, cleaner retrospective explanation, or a combination of these signals.
05 · Metadata and annotation
Context that turns footage into training data
Structured metadata can describe task, geography, environment, language, device, camera configuration, participant attributes, duration, objects, validation status, and permitted use. Optional annotation can add temporal segments, action labels, object references, transcription, captions, and event boundaries.
06 · Quality control
Acceptance rules established before scale
A pilot calibrates automated checks and human review against explicit thresholds for visibility, framing, task completion, synchronization, audio, metadata, technical integrity, and protocol compliance. Rejection, recollection, escalation, and delivery rules are agreed before production volume increases.
Pilot first: custom egocentric programs normally begin with a controlled pilot that tests capture instructions, devices, synchronization, contributor behavior, data quality, metadata, and rejection criteria before the collection is expanded.