How to Use tgbotx

tgbotx is structured around decision flow, not content categories.

Users are not expected to read everything. They are expected to enter, check, decide, and exit.

Tools

Use Tools when you are debugging a specific, active problem.

Tools are designed to be: - runnable once, - evidence-oriented, - decision-producing.

They do not require accounts or long-term usage.

Use Guides when a problem repeats or when configuration misunderstandings are suspected.

Guides establish baseline understanding before deeper investigation.

Use Verdicts when the question is no longer purely technical.

Verdicts exist to clarify: - responsibility boundaries, - control vs non-control, - rational stop conditions.

They are not fault assignments and not legal determinations.

Products represent existing implementations of problems that have already been validated.

They are optional and never required to use this site.

tgbotx is not designed to retain users.

You should leave when: - the problem is resolved, - the responsibility is clarified, - or the decision to stop has been made.

Leaving is a successful outcome.