Milestones
List view
Expansion of batch pre-labeling to project-wide and filtered asset scopes (#689). Scheduled after 0.1.0 because the expansion carries its own design questions — the durable work unit that owns a selection, its schema pin, and how a caller expresses a stable filter — and the single-batch scope it builds on ships first.
No due date•1/1 issues closedEach issue here records a regression that reached a branch, a review, or a person because the check that should have caught it could not. The wire-roster gate needs an anchor outside its two hand-kept transcriptions (#675), hand-built browser stubs need to be held to the shapes the generated checks require (#682), a failed browser walk's retry needs a workspace it can actually pass (#688), the documented check commands need to say they are a subset of the full gate (#674), and seven routes declare a 422 the application already declares for every route (#657). **Exit criterion:** each gate demonstrably fails on the regression class its issue documents, and the documented checks either are the full gate or say plainly that they are not.
No due date•8/8 issues closedThe kernel's write gates and the interface's story about them say the same thing. The orphan-invariant decision (#585) comes first; the class-removal flow, whose three dialogs currently contradict each other (#588), is rebuilt on whichever answer that decision records; and the geometry-bounds decision (#525) settles what a stored shape may claim about where it sits. **Exit criterion:** the orphan invariant is decided and enforced against one version, the class-removal flow tells one consistent story in the user's vocabulary, and the kernel's rule for out-of-frame geometry is written down and enforced.
No due date•4/4 issues closedThe http half of the connection model stops being a form that leads nowhere. The credential-storage decision (#519) comes first, then the adapter that speaks to a real endpoint (#648), a connection recording which driver serves it (#649), and browser coverage for editing a connection (#510). **Exit criterion:** an http connection pre-labels a batch end to end against a real endpoint, and the connection edit flow is exercised by a browser suite against a real server.
No due date•5/5 issues closedA model can label a batch nobody has opened; this milestone makes that output workable. It covers reviewing a few hundred model-labeled frames at volume (#676), naming the classes a run will and will not ask for before it starts (#677), a Home attention row for a batch a model labelled and nobody has read (#681), and re-run semantics so the first pass over a piece of media is not the only pass it can ever get (#683). **Exit criterion:** a pre-labeled batch can be triaged and reviewed at volume, a run's scope is visible before it starts and its result is visible from Home, and a deliberate re-run over already-labeled media is possible.
No due date•4/4 issues closedScope (Armando, 2026-08-06): 3D/point clouds, video tracking, more formats, import of external datasets. Product boundary: VisionSet stays a simple local server — one workspace, projects as the unit, each project is a dataset. Multi-tenancy, scale and identity concerns are out of scope for this distribution. Draft scope issues in this milestone are planning seeds, not implementation tickets.
No due date•1/11 issues closedThe stable release. Done when M7 (the pre-label loop), M8 (remote inference), M9 (schema lifecycle coherence) and M10 (gate hardening, tagged 0.1.0-beta) are done; each of those milestones carries its own exit criterion and maps to a pre-release tag. Release-engineering tasks — changelog, version bump, wheel gate — are filed directly here. The due date is a tentative target; the exit criteria are not.
Overdue by 4 day(s)•Due by August 27, 2026•170/170 issues closed