> For the complete documentation index, see [llms.txt](https://stellar.gitbook.io/module-library/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://stellar.gitbook.io/module-library/identity-management/tier-based-role-certifier/tuning-guidelines.md).

# Tuning Guidelines

*Authors: BlockScience and SDF, September 2023*

* Tuning Story 1: When to add new dis/auto/conditional qualifiers to a role certifier?
  * TRC's goal is to provide a comprehensive framework to make the requirements for acquiring a given role explicit. Some of them may require a requirements-based approach, on which everyone that fullfills a base set of qualities is approved for the role, whereas others may require a selection procedure for filling in a limited supply of positions. In terms of heuristics, we can have the following guidelines when creating new qualifiers:
    * Disqualifiers are useful for any vetting process: eg. ban lists and restrictions. 
    * Conditional qualifiers are useful when algorithmical procedures for attesting someone to a role is desirable. This tends to be the case with roles in which many members are expected. They can also be useful when the role belonging rules should be made particularly explicit.
    * Autoqualifiers are useful for hierarchical roles, where belonging to a higher-ranked role gives automatic access to all lower roles. They can also be useful for fast-tracking members.
* Tuning Story 2: When to add new roles?
  * Ideally, a Role Attestation is attesting that some identity should have particular rights. Those rights can than be broken down into pieces or bundled together as combos. 
    * Adding new roles can be useful when new bundles of rights are created. Alternatively, one approach is to associate each potential right with a role, in which case any new rights should be associated with new roles.


---

# 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://stellar.gitbook.io/module-library/identity-management/tier-based-role-certifier/tuning-guidelines.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.