> For the complete documentation index, see [llms.txt](https://docs.nxcframework.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nxcframework.net/nexus-core-docs/what-you-get/roadmap.md).

# What is coming

Eleven phases. Each ends at a gate of verifiable checks, and a phase does not begin until the previous gate passes.

> **Current position: Phase 0.** No framework resource code exists.

| Phase  | Scope                         | Gate                                                                                                                            |
| ------ | ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **0**  | Governance and specifications | Standards, decisions, registry, matrix, and documentation baseline exist and are substantive                                    |
| **1**  | Framework foundation          | Resources start in order, health is queryable, correlation propagates, configuration publishes, target and interaction clean up |
| **2**  | Character lifecycle           | Players create, customize, spawn, reconnect, and persist characters safely                                                      |
| **3**  | Inventory and economy         | Items move atomically, purchases are auditable, banking is transaction-safe                                                     |
| **4**  | Vehicles and property         | Vehicles persist through reconnects and transitions; duplicates are prevented                                                   |
| **5**  | Business and employment       | Players own businesses, hire staff, accept contracts, and create player-to-player economic flow                                 |
| **6**  | Civilian economy              | Every job produces an output another system consumes                                                                            |
| **7**  | Public safety                 | Shared dispatch, evidence custody, fire, rescue, and medical operate end to end                                                 |
| **8**  | Crime                         | Crime creates evidence, economic impact, police response, and court consequences                                                |
| **9**  | Communications and polish     | The platform feels cohesive; administrative workflows are reliable                                                              |
| **10** | Full migration                | Legacy dependencies removed, bridges gone, data migrated and reconciled                                                         |

## Phase 1 — the foundation

Eight resources, built in dependency order:

```
nxc_lib → nxc_core → nxc_config → nxc_ui → nxc_zones → nxc_target → nxc_interact → nxc_devtools
```

`nxc_config` is a foundation resource rather than later polish: every resource must register its configuration with it, so it cannot arrive after the resources that depend on it.

## The first playable milestone

A deliberately small vertical slice, spanning Phases 1 through 5. It is **not** attempted during foundation work, but every foundational contract is designed with it in mind:

connect to the server → select or create a character → customize appearance → spawn safely → use target interactions → open inventory → use basic items → access banking → purchase from a store → own and retrieve one vehicle → rent one apartment → accept one delivery contract → receive payment → disconnect and reconnect without data loss.

It tests identity, lifecycle, UI, target, inventory, banking, vehicles, property, jobs, contracts, persistence, and error recovery without requiring the full city.

## What is not scheduled

Dates. Phase gates are conditions, not deadlines, and a phase passes when its checks hold rather than when a date arrives.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.nxcframework.net/nexus-core-docs/what-you-get/roadmap.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.