Milestones

List view

• v1.0 — Stable

  The commitment release: the v1 API contract frozen (the OpenAPI snapshot becomes a compatibility promise), a documented and tested upgrade path between releases, performance validated at realistic dataset sizes, and complete operator documentation. Exact scope firms up as 0.6–0.9 land.

  No due date
  0% complete0 open 0 closed

• v0.9 — ERP & Manufacturing Polish

  The released engineering definition reaches the systems that buy and build. Odoo connector (paid) from working prototype to stable release 1; Carbon MS connector (community) scoped and started; polish across work orders, travelers, and physical-part genealogy driven by real manufacturing use.

  No due date

  •0/2 issues closed
  0% complete2 open 0 closed

• v0.8 — CAD Connectors

  Bring the vault into the CAD seat: browse, check out, check in, and publish geometry from inside the CAD tool, with Cascadia's ECO-branch semantics rather than a generic file lock. FreeCAD connector in the community edition; SolidWorks and Solid Edge connectors in the paid edition — each targeting a stable release 1.

  No due date

  •0/3 issues closed
  0% complete3 open 0 closed

• v0.7 — Systems Engineering Phase 1

  Requirements management and V&V traceability as a working loop, not just item types: satisfies/verifies edges between requirements, design items, and test evidence; suspect links when a linked revision changes; rollups that answer "is this requirement satisfied, and how do we know?"

  No due date

  •0/1 issues closed
  0% complete1 open 0 closed

• v0.6 — Event Bus

  Every domain event — item released, ECO transitioned, file checked in — durably recorded and consumable: a transactional event log in Postgres, ordered consumers with cursors, and webhook delivery out. This is the integration backbone the later connectors (ERP, CAD, MES) build on.

  No due date

  •0/1 issues closed
  0% complete1 open 0 closed

• v0.5.1 — Stabilization Overhaul

  A hardening release — deliberately no headline features. A systematic pass across the whole codebase, shipped as a stream of small, focused changes: program-level access isolation on every API surface, request validation from the schemas the API document declares, a consistent error envelope, concurrency correctness in checkout/merge/version resolution, migration-only schema changes at deploy time, background-job retry fixes, database-enforced invariants, and a test suite that runs in parallel against its own database. User-visible changes land in the CHANGELOG as they merge.

  No due date

  •1/1 issues closed
  100% complete0 open 1 closed