Instruction Sources and Precedence

Instruction text sources are persisted under deterministic keys and can be set at function scope or activity scope.

This controls how system/user/import/instruction text is stored and retrieved across AI operations.

Instruction source dimensions

Source type	Scope and intent
`System`	Base system-level behavior for a function type.
`User`	User-specific extension/override content for a function type.
`Import`	Imported-definition context for a specific workflow/activity pair.
`Instruction`	User instruction context for a specific workflow/activity pair.

Function-scoped key:

AI_{FunctionType}_{SourceType}

Activity-scoped key:

AI_{WorkflowId}_{ActivityId}_{SourceType}

function-scoped source text can be read or updated by function type + source type
activity-scoped import/instruction text can be read or updated by workflow/activity ids
imported text and user instruction text are tracked separately

All stored values are trimmed before persistence/retrieval usage.

Current system-source resolution routes to coded defaults directly.

Practical implications:

persisted System overrides are not used by that default call path
user/import/instruction values are still stored and available through source-specific retrieval paths
if you need custom system behavior, use generic source retrieval or change default source resolution logic

When building external AI orchestration: