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

# Core Principles

The ONEST architecture is based on three core principles, 

* **Access** - ONEST will leverage DSEP protocols to enable discovery and access to education, upskilling, and job opportunities irrespective of financial or geographical status thus enabling equitable distribution. It will not only facilitate discovery but an end-to-end workflow discovery-ordering-fulfilment-post fulfilment on the network between provider and consumer platforms. 
* **Trust** - The trust layer will be powered by digitally verifiable credentials (VCs) & electronic registries. VC issuance, thus, can be made available as a service for service provider platforms to issue verifiable education, training, and work certificates & licences to augment trust in the education and job ecosystem. The verifiable certificates will help the students, professionals and employers to fast-track hiring and background checks with enhanced credibility. 
* **Ownership** - ONEST will enable a consumer-centered ecosystem, where the end consumer (student, professional, organization) can store their VCs in their choice of  digital wallet. ONEST will leverage existing consent and data exchange architecture under the data protection framework. The digital wallet can also be linked to a student’s ID to facilitate government sponsorships and scholarship programs. 

<br>


---

# 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://starterpack.onest.network/readme/core-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.