Expose the Brain Read record selector as a wizard or prompt-bar question, including inherited types and inline record creation.
Where: Brain Read → record_in socket → expose through a group → question editor → Answer from your Brain.
Key ideas
- Choose which record, not a pasted summary: Brain Read has a record_in input that identifies the record to bind. Its output rail then exposes that record’s body and typed fields. A person answering a mini-app question selects an actual accessible record, not a static list of names copied into the form.
- Type inheritance: A question wired to a Brain Read card inherits that card’s record type unless the author explicitly chooses another. Repointing the card updates the inherited choice; clearing the override returns to inheritance.
- One workflow across surfaces: The question works in both the full wizard and the collapsed prompt bar. Available choices come from the relevant Brain library, including custom record types, and inline creation can add a missing record before continuing.
Steps
- Add a Brain Read card and select the kind of record the flow needs, such as Brand or Character.
- Expose its record_in selector through the group rather than connecting the question to a body output.
- Open the question editor. Leave the inherited record type when it is correct, or use Answer from your Brain to choose a deliberate override.
- Preview the wizard and prompt bar. Select an existing record, or use the inline New action and complete the record form.
- Run with two different records and inspect the downstream text/media fields. This checks that the question changes the binding, not only its displayed label.
Authoring and answering are different
The author chooses which record type the question offers. The person answering chooses a particular record available to them in the workspace/project context. The question should not bake in the author’s personal record as though every later user can read it.
Troubleshoot the entire connection
- record_in is the reader’s selection control; record_out and rf_<key>_out carry its contents.
- The question editor shows library-loading and read-error states separately from a zero count.
- A selected record is resolved through the normal binding path, so its field schema and card identity stay aligned.
- Use a clear question label such as “Which brand?”; inherited types avoid maintaining the same type setting in two places.
Brain in projects and shared workspaces
Brain supplies Designer with structured project context through the full From your Brain picker, record mentions, pinned standing context, record-part targeting, and Save Research. It is not a hosted Designer page or right-dock tab. Folder/team homes and item-level sharing remain in the full Brain surface, and access is governed by the record/project role.
Limitations and important notes
- Only records available within the current access scope can be offered. A mini-app question does not grant access to another workspace’s private Brain.
Troubleshooting
The question offers the wrong record type.
Check for an explicit question override first. Clear it to inherit the connected Brain Read card’s type, or select the intended custom type.
Choosing a new record leaves stale outputs.
Verify the exposed input ultimately reaches record_in on Brain Read, then inspect the bound record identity before rerunning consumers.