> For the complete documentation index, see [llms.txt](https://ipg.gatcg.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ipg.gatcg.com/philosophy/issuing-penalties.md).
# Issuing Penalties
After any penalty is issued, the attending judge should explain the infraction to the players in the match, the recommended procedure for resolving the infraction, and the penalty applied. During any deviations from recommended procedures, the Head Judge is expected to explain the typically recommended penalty and procedures, the intended course of action, and the reason for deviating from the presented guidelines.
If multiple infractions related to an error are made and multiple penalties might be applied, only the most severe penalty should be applied.
Penalties should only be applied to the root cause of an infraction. As an example, if an error based on private knowledge occurred or originated from a game rule violation based on public information, the error would not be a Private Card Error but would instead be treated as a Game Rule Violation and penalized accordingly.
Judges may investigate whether players have received penalties for the same infraction over the course of the tournament and upgrade the penalty if deemed to be a fair punishment. Players may not lie to judges about previously received penalties during that tournament.
These procedures and recommended guidelines for managing infractions will offer corrective steps for the initial violation. It is recommended that judges do not deviate from these procedures and that Head Judges only deviate if absolutely necessary and in exceptional circumstances. This is to ensure that any corrective actions taken are standardized and fair for all players regardless of game state or other extenuating factors.
---
# 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://ipg.gatcg.com/philosophy/issuing-penalties.md?ask=&goal=
```
`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.