"The sequence is ROLES first, then condition, then script." - Chuck Tomasi says so at this link: https://www.servicenow.com/community/grc-forum/order-of-execution-of-an-acl/m-p/1311962/highlight/true#M6538

When designing and creating a form, you can create sections to organize fields on a form. Sections are containers that group related fields together and provide a label and a description for the group. You can use sections to improve the readability and usability of the form. You can also collapse or expand sections to show or hide the fields within them.
The other options are not valid ways to organize fields on a form. Related lists are not fields, but lists of records that are related to the current record on the form. Tabs are not part of the form, but part of the application menu that allows you to navigate between different modules. Buttons are not fields, but elements that perform actions on the form, such as saving, updating, or deleting the record.
Reference:
[Form sections]
[Related lists]
[Application menus and modules]
[Form buttons]

Reference:
An application can have as many application menus as the application design requires. An application menu is a container for application modules, which are links to features or functionalities within an application. Application menus are displayed in the application navigator, which is the left sidebar of the ServiceNow interface. Developers can create and configure application menus using Studio or the Application Menus module. Application menus can have different roles and visibility settings, depending on the intended audience and purpose of the application. Reference: [ServiceNow Docs - Application menus], [ServiceNow Docs - Create an application menu]