> 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/start-here/what-is-nexus-core.md).

# What is Nexus Core

Nexus Core is a custom FiveM roleplay framework. It replaces a fragmented collection of framework, job, economy, vehicle, property, public-safety, criminal, and utility resources with a single platform whose parts share contracts, ownership rules, interfaces, and performance expectations.

## What it is not

**Not a compatibility layer.** Nexus Core is not QBCore, QBox, or ESX under a different name. A compatibility layer must mirror the contracts of what it wraps; Nexus Core defines its own and treats legacy frameworks as systems to migrate away from.

**Not a collection of scripts.** The distinguishing property is that resources share a design system, a permission model, an error shape, a configuration service, and a set of ownership rules. A script that works well in isolation but ignores those is not a Nexus Core resource.

**Not an attempt to rewrite everything.** Maps, MLOs, vehicles, EUP, clothing, hair, props, sounds, and IPL loaders remain external dependencies. Rewriting a working MLO produces no gameplay improvement.

## The problem it solves

A server assembled from independently authored resources accumulates predictable failures:

* Several resources believe they own the same data, so none can guarantee it is correct.
* Money and items can be duplicated because no single resource controls the transaction.
* Each resource has its own interface, so players learn several interaction languages.
* Operational values live in files, so tuning requires a restart.
* A failure in an optional system takes down something essential.
* Nobody can say what any given resource actually does.

Nexus Core addresses these structurally rather than by convention: one owner per domain, server authority, a shared design system, universal in-game configuration, and enforced failure isolation.

## The core resource and its supporting resources

```
nxc_core     the framework spine: lifecycle, identity, sessions, permissions, state
nxc_*          every supporting platform and gameplay resource
```

`nxc_core` is deliberately small. Inventory, banking, jobs, vehicles, properties, police, and medical logic are excluded from it by design, because everything depends on it and every addition widens the blast radius of a change.

## Who it is for

| Audience            | What Nexus Core offers                                                                             |
| ------------------- | -------------------------------------------------------------------------------------------------- |
| Players             | A city where work connects to other work, ownership is meaningful, and the interface is consistent |
| Server operators    | Configuration that changes without restarts, auditable transactions, and diagnosable failures      |
| Resource developers | Documented contracts, a shared design system, and clear domain boundaries                          |
| Administrators      | Attributable staff actions, audit trails, and administrative visibility                            |

## Current state

**No framework resource code exists.** The project is in Phase 0, establishing governance, specifications, and standards before implementation. See [Project status](/nexus-core-docs/start-here/status.md).


---

# 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/start-here/what-is-nexus-core.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.