Skip to content

Task Reports

Development progress is tracked through numbered tasks. Each report lives in this directory (docs/tasks/) alongside this index.

Task numbers are not unique — several rounds ran in parallel on different branches and reused a number, so 7, 8, 9 and 10 each have more than one report. Every row below links to a distinct document.

Task Title Status
1 Consolidate input/output format Done
2 End-to-end Docker integration Done
3 VLA-3D generated dataset pipeline Done
4 Integrate Qwen3.5 VL for testing Superseded by 17
5 VLM tick logger Done
6 Documentation webpage In progress
7 Data coupling — coverage trajectory generation Done
7 Data sample visualization script Done
7 Evaluation pipeline integration Done
8 Frontier-based room exploration Superseded by 12 / 15
8 Ref dataset ambiguity audit & label-vocab fix Done
9 Expand ref corpus & match official phrasing distribution Done
9 Gemini-backed responder for Task 1 and Task 2 Superseded by 14
10 Offline Gemini evaluation pipeline Done
10 Scene representation Done
11 Perception responder Done
12 Consolidate exploration + scene-building pipeline Done
13 Merge perception enhancements into the pipeline Done
14 Consolidate submission pipeline into the scene_gemini responder Done — live smoke test pending
15 Retire the unreachable Phase-A exploration stack Done
16 Move task reports into docs/tasks/ Done
17 Retire the qwen responder Done
18 Deduplicate the responder factory Done
19 Remove the near-relation subsystem Done
20 Exploration benchmarking across Unity scenes Done

The task definitions these reports answer to stay at the repo root in TASK.md.

Design documents

Detailed technical documents are in the docs/ directory:

Historical design records

Kept for their recorded rationale; they describe code that no longer exists.