Temporal reasoning requires evidence of how events relate over time. A model may need to understand order, a changing object state, or the connection between an early action and a later outcome. Share those dependencies with Fiund so a sourcing brief can specify more than a runtime target.
Identify the required evidence chain
Describe what the model must infer and which visible or audible observations support that inference. Define the beginning and ending conditions of a complete example. Specify whether pauses, retries, interruptions, and failed attempts should be retained. An edited highlight can remove the very transition the task needs, so make continuity and acceptable cuts explicit rather than assuming every long clip preserves causality.
Preserve relationships and timing
Keep source identifiers, clip offsets, and exact version references with the delivered footage. If labels describe event order or changing states, explain how simultaneous and uncertain events are represented. Reordered edits, speed changes, and replaced audio require review. Decide how related sessions and derived clips should be grouped for evaluation so the test reflects the intended unfamiliar situations. Include examples where the expected outcome does not occur. These help reviewers distinguish a complete observed sequence from a plausible story about what usually follows the visible action.
Pilot genuinely temporal questions
Review sample tasks that cannot be answered from a single convenient frame or an embedded title. Inspect full sequences and confirm that the required evidence remains present after preprocessing. Discuss source documentation and intended commercial use separately from technical success. Fiund reviews prospective availability, annotation scope, samples, and delivery terms for the specific project rather than guaranteeing a ready-made temporal benchmark.
Include in your inquiry
- Reasoning tasks and required evidence chains.
- Completeness, continuity, and interruption policies.
- Temporal labels, source offsets, and version requirements.
- Evaluation grouping and commercial usage brief.