---ci--- project: orca phase: 3 milestone: v0.3 status: complete requirements: covered: [REQ-022, REQ-030, REQ-032] partial: [] ---/ci--- v0.3 milestone merged to main. Includes all v0.2 work (P08-P10) that was previously on the milestone branch but not yet merged to main, plus the v0.3 completion work (iter.Seq streaming + doctor network/db). v0.2 phases included: P08 (mTLS), P09 (scheduling), P10 (security scan). v0.3 phases: P0 (pre-execution), P1 (iter.Seq streaming), P2 (doctor), P3 (final review+ship). Total: 40 requirements, all complete. No new go.mod dependencies. Full test suite passes under -race. gofmt + go vet clean.
3.3 KiB
Roadmap: Orca
Milestone v0.1: Foundation — COMPLETE
- Phase 0: Project Initialization & Specification
- Phase 1: Core CLI Skeleton & Command Parsing
- Phase 2: Basic Node Management (Join/Leave)
- Phase 3: Simple Task Execution Engine
- Phase 4: Local State Persistence
- Phase 5: Basic Health Checking
- Phase 6: CoreCI Full Release Flow
Tagged v0.2.0 (next-minor per feature-milestone promotion rule).
Deferred to v0.2 (out of scope for v0.1)
- Multi-node scheduling (D-004 decision: single-node only in v0.1)
- mTLS for inter-node communication (REQ-011, REQ-023)
gosec+govulncheckin CI pipeline (REQ-014)iter.Seqstreaming job lists (REQ-022)- Frontend / devops personas (no web UI; CoreCI handles release)
Milestone v0.2: Networking, Observability, Security Hardening — FUNCTIONALLY COMPLETE (pending merge to main)
Scope: extend v0.1 with secure cross-node transport, multi-node scheduling, richer CI security scanning, and streaming I/O.
- Phase 8: mTLS handshake + internal CA with CSR join (Wave 1) — shipped v0.2.1
- Phase 9: Multi-node scheduling & job dispatch (Wave 1) — shipped v0.2.2
- Phase 10:
gosec+govulncheck+ gitleaks in CI (Wave 2) — shipped v0.2.3 - Phase 11:
iter.Seqstreaming job/node lists (Wave 2) — deferred to v0.3 P01
Milestone tag: v0.3.0 (next-minor per feature-milestone promotion rule) — pending merge to main.
Per-phase tags: v0.2.1 (P01), v0.2.2 (P02), v0.2.3 (P03) — all shipped.
Milestone v0.3: Scheduling & Streaming Completion — COMPLETE
Scope: complete the two work items deferred from v0.2 that were not already shipped in P08-P10. A re-init SPECIFY codebase audit confirmed that REQ-014/027/028/029/031/037/039/040 all shipped in P08-P10 despite stale REQUIREMENTS.md marking them Pending. The remaining work is lean:
- Phase 0: Pre-execution (specify → clarify → research → plan → grill) — shipped v0.3.0
- Phase 1:
iter.Seqstreaming for--watchflags (REQ-022, REQ-030) — shipped v0.3.1 - Phase 2:
orca doctornetwork + db full implementation (REQ-032 completion) — shipped v0.3.2 - Phase 3: Final review + ship + audit (milestone release) — shipped v0.3.3
Milestone tag: v0.4.0 (next-minor per feature-milestone promotion rule).
Per-phase tags: v0.3.0 (P0), v0.3.1 (P01), v0.3.2 (P02), v0.3.3 (P03 final = milestone release).
Per .ciagent/RELEASE_POLICY.md, every phase tag produces a Gitea release.
Per-phase REQ coverage
-
P01 —
iter.Seqstreaming for--watchflags- REQ-022 (
iter.Seqfor streaming job lists, Go 1.25+) - REQ-030 (
--watchoutput format mode: table default vs streaming JSON per event) - Applies to both
orca job list --watchandorca node list --watch(D-024, per ARCHITECTURE.md CLI layer + D-017)
- REQ-022 (
-
P02 —
orca doctornetwork + db full implementation- REQ-032 (completion: network reachability via mTLS
/healthzprobe, db integrity viaPRAGMA integrity_check+ migration version) - Replaces
NetworkStubandDBStubfrom v0.2 P01
- REQ-032 (completion: network reachability via mTLS
v0.3 is a completion milestone, not a direction change
The vision ("minimalist, offline-first, CLI-first orchestration engine") is unchanged. v0.3 closes out the v0.2 deferrals and merges the accumulated v0.2 work to main.