EyeAuras Structure Discovery Map

Reference map for the product model: Aura Tree, folders, auras, triggers, actions, overlays, behavior trees, macros, variables, and script workspaces.

User Intents

• Understand what kind of host a script is running inside.
• Find the current aura, folder, behavior tree, macro, trigger, action, or overlay context.
• Decide whether an API is product runtime, script runtime, SDK metadata, or optional package surface.
• Move code from top-level script into ordinary helper classes safely.

Concept Model

• EyeAuras is an automation host, not only a C# library.
• The user-facing project is an Aura Tree made of folders and auras.
• Auras own enabling conditions, triggers, overlays, and action lists.
• Triggers determine active state; actions perform work; overlays display UI.
• Scripts run inside a host-owned context with live services and current aura metadata.
• SDK references expose symbols; live host services still depend on runtime context and loaded modules.

API Details

• IEyeContext - broad runtime context for an EyeAuras object, including its current IHasLoaded.IsLoaded state.
• IAuraContext - aura-specific runtime context.
• IFolderContext - folder-specific runtime context.
• IEyeItem - shared tree item shape.
• IAuraTreeScriptingApi - script-facing tree lookup/navigation API.
• IAuraAccessor - script handle for one aura.
• IFolderAccessor - script handle for one folder.
• IMacroAccessor - script handle for one macro.
• IBehaviorTreeAccessor - script handle for behavior trees.
• EyeAuras.BehaviorTree.Nodes.IControlFlowNode - runtime nodes own child routing; marked ActionNode<T> implementations return their action status directly. MacroIfThenElseNode ticks Condition once and returns the chosen branch status, without replaying the first child. Ordinary actions continue into it after Success. Break in Repeat's Loop body, including a chosen If branch, exits the Repeat. Structural role blocks pass it to that owner; explicit nested MacroBlock nodes keep their own exit scope. Return finishes the whole macro with its configured status.

Prefer

• Identify the current product context before choosing APIs.
• Use accessors for script-facing aura/folder/macro work.
• Use auras/entities.md when researching how user-facing components are registered.
• Use scripting/runtime.md when top-level script vs helper-class behavior matters.

Avoid

• Avoid treating top-level script helpers as global C# APIs.
• Avoid using UI/editor classes as the first source of runtime semantics.
• Avoid assuming SDK-only code can access live host services.

Search Synonyms

• Aura Tree
• aura context
• folder context
• current aura
• current folder
• script workspace
• behavior tree
• macro
• action list
• overlay
• runtime context

Related Maps

• scripting/runtime.md
• auras/overview.md
• auras/entities.md
• core/app-runtime-contexts.md
• core/deployment.md