> For the complete documentation index, see [llms.txt](https://community.threekit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community.threekit.com/platform-documentation/project-data/catalog/item-rules-and-logic.md).

# Item Rules and Logic

Rules are meant to define the configurator behavior by controlling Attribute and Attribute Value visibility, as well as setting attribute values.

Rules consist of Conditions and Actions.

Conditions leverage Attributes. Multiple conditons are evaluated based on an AND operator.

### Action Types

The following are the actions possible within a Rule

**set attribute visible** -- reveals an entire attribute on the basis of a satisfied condition

**set attribute enabled** -- makes a previously unavailable, visible attribute usable

**set attribute value** -- dynamically sets the value of a given attribute.

**set attribute value visiblity** -- reveals an attribute value on the basis of a satisfied condition

**set attribute value enabled** -- Makes a previously unavailable, visible attribute value usable

[Learn here more about the Rules and Logic System.](https://community.threekit.com/platform-documentation/project-data/logic.md)


---

# 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://community.threekit.com/platform-documentation/project-data/catalog/item-rules-and-logic.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.
