Future options and scope
Scope and future options
The immediate focus is useful context and review for one real software change. A capability that is missing today is not automatically a commitment to build it.
How to read future direction
Planned means intended work with scope and timing still open. Exploring means no decision to build has been made. Neither is an availability claim.
Explicit boundaries
Cycles/sprints and broad bidirectional project-management synchronization are not planned. Scoped task and repository connections are planned separately. There is no supported standalone sync infrastructure offering today.
See the public roadmap, integrations and known limits. We can discuss deeper scope and evaluation questions through the detailed client edition.
Something here wrong, missing or out of date? Tell us at support@orneos.com — corrections to these pages are welcome and we would rather hear it than have you work around it.