Logic Fields
A section visible in the /org sidebar between Consumers and Logs (Accounts → Roles → AI Spaces → Agents → Consumers → Logic Fields → Logs → System).
Logic Fields are the org's custom data fields — a centrally-managed set of typed values/definitions the platform can reference.
Status: documentation pending. Beyond the one-line concept above, the behavior of Logic Fields is not yet documented in the platform sources — do not assume a schema, columns, or a
system/*resource name for it. The open questions below are leads, not answers; confirm against the live/orgUI.
Open questions
- What "Logic Fields" actually means — is this:
- A schema definition for fields that can be referenced in flows?
- A registry of typed values (booleans, enums, numerics) that admins set centrally and flows read?
- Form-builder fields shown to Consumers in the Chat?
- Something else entirely?
- Who can edit Logic Fields (which roles)?
- List page layout — what columns?
- Create / edit form — what fields?
- How a flow developer reads a Logic Field from inside a Script Node — is there a
system/<lib>for it, or does it surface in the dictionary, or is it set per-Agent? - Whether Logic Fields are scoped per Space, per Agent, or globally.