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

# Core principles

These principles apply across the Protocol, SDK, and bloxchain.app.

## On-chain enforcement

If policy denies an action, the contract rejects it — regardless of which UI or SDK client submitted it.

## Separation of duties

Protected roles (Owner, Broadcaster, Recovery) and custom RBAC roles are **distinct**. Sensitive paths can require multiple wallets and phases.

## Explicit operations

Every governed call is a registered **operation** with a **function schema**. Ad-hoc `call` bypass is not the default model.

## Observable state

Transaction records, roles, and allowlists are readable on-chain. Operators and integrators share the same source of truth.

## Non-custodial product

**bloxchain.app** does not hold private keys or custody assets. Wallets sign; contracts enforce.

## Open protocol, pinned releases

Integrators pin **@bloxchain/sdk** and contract artifacts to the same [Protocol release](https://github.com/PracticalParticle/Bloxchain-Protocol/releases). See [Versioning strategy](/resources/releases.md).

## Documentation honesty

Public docs describe **published, audited scope**. Planned features are on the [Roadmap](/resources/roadmap.md), not implied as shipped.

## Next steps

* [Security model](/security/security-model.md)
* [Documentation standards](/readme.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.bloxchain.app/introduction/core-principles.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.