Artifact-backed examples

Examples and report reading

Each example points back to checked-in repository evidence and lists the companion files or fields needed to interpret it.

stable

Instance-segmentation report and overlays

A checked demo that pairs a JSON metric report with visible mask overlays.

Instance-segmentation report and overlays

Expected companion files or fields

  • instance_seg_demo_report.json
  • overlays/*.png
  • demo_config.json

Source artifact

bridge

External framework prediction artifacts

Detectron2, MMDetection, YOLOv8, and YOLOX examples converge on the same wrapped predictions interface contract before scoring.

Expected companion files or fields

  • wrapped predictions JSON
  • meta.export_settings
  • adapter/source identity

Source artifact

benchmark

Backend support and skip semantics

The generated support matrix records implemented, conditional, and unsupported backend paths without presenting a missing lane as a passing result.

Expected companion files or fields

  • benchmark support metadata
  • explicit support status
  • skip or failure reason where applicable

Source artifact

research

TTT Research evidence requirements

The bundled image is a synthetic documentation fixture. It demonstrates the required artifacts and provenance only; it does not establish method efficacy or promote TTT to Stable maturity.

TTT Research evidence requirements

Expected companion files or fields

  • baseline_predictions.json
  • method_predictions.json
  • before_after_compare.json
  • TTT log and plan

Source artifact · Stable baseline artifact

Before comparing two reports

  • Same task and metric family
  • Same dataset identity and split
  • Validated predictions interface contract
  • Recorded producer and export settings
  • Pinned protocol settings
  • Class and coordinate semantics aligned
  • Skipped, conditional, or unsupported lanes kept explicit
  • Visible evidence linked where the task provides it
Return to stable evaluation Resolve a mismatch