Gideon glossary
Use this page to distinguish the main kinds of context and work in Gideon.
| Term | Meaning |
|---|---|
| Agent | A configured worker with instructions and capabilities |
| App | An installable extension for tools, services, or surfaces |
| Artifact | An output you can inspect and use |
| Connection | Access to a service you choose to link |
| Exit criteria | Conditions that must be satisfied before a task is complete |
| Goal | An outcome an iterative run works toward |
| Knowledge | Material deliberately added to your reference library |
| Loop | Work that iterates across cycles toward a goal |
| Memory | Facts, preferences, and lessons recalled across conversations |
| Project | A home for related context and work |
| Prompt | Reusable instructions for starting a request |
| Skill | A reusable method and guidance for doing a kind of work |
| Task | A work item with status, dependencies, and completion criteria |
| Tool | An action Gideon can invoke |
| Trigger | An event or schedule that starts work |
| Workflow | A process whose structure is defined in advance |
| Workspace | The files and working context available to the runtime |
Common distinctions
A workflow defines the process; a loop iterates toward the outcome. Knowledge is your saved material; memory is context Gideon recalls. An approval permits an action; it does not prove the result. A scheduled job describes future work; its history shows what actually ran.
Was this page helpful?
Edit this page