> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/nfh-fabric/principles.md).

# Principles

Six architectural tenets shape every NFH fabric service and protocol.

{% stepper %}
{% step %}

### Decentralised

No single operator. The network runs on shared protocols, not a platform owner. NFH fabric services exist to coordinate — never to gate.
{% endstep %}

{% step %}

### Permissionless

Anyone who speaks the protocol can join. Governance is about conduct, accountability, and standards — not gatekeeping.
{% endstep %}

{% step %}

### Open standards

Specifications are public, versioned, and aligned with established open standards (W3C Verifiable Credentials, x402, MCP, OpenTelemetry). Implementations are open-source where possible.
{% endstep %}

{% step %}

### User-centric

Identity, data, credentials, and reputation belong to the participant. Not the platform. Self-custody is the default; selective disclosure is built in.
{% endstep %}

{% step %}

### Composable

Adopt one service or the full stack. Each NFH fabric service is independent, can be used on its own, and combines cleanly with the others.
{% endstep %}

{% step %}

### Agent-native

Autonomous software is a first-class participant — equal in rights and accountability to humans and businesses. Identity, signing, holding tokens, earning reputation: agents do all of it natively.

[**Read more: Agents as first-class participants →**](/nfh-fabric/agents.md)
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nfh.global/nfh-fabric/principles.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.