In Guidewire InsuranceSuite, Gosu rules are a foundational mechanism used to implement business logic such as claim assignment, validations, eligibility checks, and workflow decisions. From an analyst perspective, understanding the core structure of a Gosu rule is critical for interpreting system behavior and validating business requirements.

A Gosu rule fundamentally consists of two essential components: the business object (entity) on which the rule operates and the action that executes when a defined condition evaluates to true. Therefore, Options A and D are correct.

Each rule is associated with a specific Guidewire entity, such as Claim, Exposure, or PolicyPeriod. This entity defines the scope and context of the rule and determines which data fields and attributes are available for evaluation. Without an associated entity, the rule has no operational context within the system.

The second essential component is the action. When the rule's condition evaluates to true, the action specifies what the system should do. In claim assignment rules, this typically involves assigning a claim to a specific group, queue, or user. While the condition controls when the rule applies, the action determines the outcome, making it a core structural element of the rule.

The remaining options are not essential components of a Gosu rule. PCF files (Option B) are related to user interface configuration. Typelists (Option C) may be referenced within rules but are not structural components. A graphical drag-and-drop interface (Option E) does not exist for Gosu rule creation in Guidewire.