# Future options and scope

Scope and future options

Status: Reference

Documentation updated: 2026-09-26

Source: https://docs.orneos.com/docs/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](https://docs.orneos.com/docs/roadmap), [integrations](https://docs.orneos.com/docs/integrations) and [known limits](https://docs.orneos.com/docs/limits). We can discuss deeper scope and evaluation questions through the detailed client edition.

## Detailed documentation

For a closer evaluation of workflows and technical boundaries, [request access](mailto:support@orneos.com?subject=Request%20detailed%20Orneos%20documentation). Access does not change feature availability.