A block is a component you use on an app page. A node is part of the page structure. A node identifier refers to that structural part, not to a record the page displays.
The distinction matters when you change a page through an MCP client. The page has visible components, while operations on its structure can return node identifiers.
Blocks make up the interface
The block library includes components such as forms, lists, tables, and buttons. You arrange components in Mockup to make an interface.
A component's appearance and its connection to data are separate choices. A list can display records, but the list is not the table that stores those records.
For example, consider a repair request app with a requests table. These names are examples:
- A list displays repair requests.
- A form lets a person enter a request.
- A button gives the person an action to take.
The page components do not establish whether a request is saved. That result depends on the app's actions and needs a separate test.
Node identifiers refer to page structure
The Orbit MCP server description describes recipe insertion as a change to nodes in a workspace.
When you apply a catalog recipe, Orbit creates a batch of nodes and validates each node. For a page recipe, Orbit places those nodes under the existing Page root. The result includes the new node identifiers.
Those identifiers describe parts of the page structure. Do not use them as identifiers for repair request records. Read Entities and records for the structure of stored data.
A recipe supplies a group of page parts
A block is a component. A recipe supplies a prepared section or page that you can adapt.
In the repair request example, you might change one component or apply a recipe that supplies a larger layout. Either choice changes the interface. Neither choice, by itself, proves that the app saves repair requests correctly.
Use Apply a recipe for the MCP procedure. Use Edit a mockup for page changes in Studio.
Check the interface and the saved result separately
For the repair request example, inspect the list and form after a page change. Then submit a test request and reopen the app to check that the request remains.
A correct layout does not replace a saved-data check. Follow Review an app before launch before people rely on the app.