> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-enterprise/resources-and-tools/the-technical-standards-committee/tsc-principles.md).

# TSC Principles

The TSC operates under a set of 4 principles defined to ensure the committee operates to a very high standard, and always looks to make the best decision for the ecosystem at large. These principles are defined as follows:

1. **Industry-driven**: experts and companies, in response to a perceived need in their industry, take the lead deciding which standards should be developed, not the TSC.
2. **Created by experts**: industry experts are involved at all stages of the standard development process, from deciding whether a new standard is needed, to defining all the technical content and reviewing and monitoring industry adoption once published.
3. **Collaborative and objective**: an open process to ensure that all parties interested are offered the opportunity to be actively involved in the standard development. The recommended solution is a result of a consensus-based approach that fully considers comments gathered from stakeholders during both the internal and public review phases.
4. **Accountable and open**: TSC standard development follows transparent procedures. The implementation of standards is monitored and recorded internally with a summary of technical decisions and comments received made publicly available.


---

# 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://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-enterprise/resources-and-tools/the-technical-standards-committee/tsc-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.