Core concepts
Tedix separates durable organizational assets from the temporary compute and model calls used to perform one piece of work. That separation is what makes agent work accountable: the compute is disposable, the identity, the authority and the record are not.
Identity and ownership
| Term | Meaning |
|---|---|
| Organization | Tenant boundary that owns workers, applications, connections, memory, policy, and evidence. |
| Tedi | Durable digital worker with a stable identity, role, memory, skills, policies, and runtime. |
| Workspace | Organization-owned place in Tedix OS for related work, conversations, and shared workpieces. |
| CLI workspace | Local connection profile for an authenticated organization gateway. Selecting it chooses where CLI commands run; it does not create or select a Workspace in Tedix OS. |
Work and execution
| Term | Meaning |
|---|---|
| Home | Governed conversation and execution surface for durable operator requests. |
| Run | One durable execution record with status, events, rationale, artifacts, and settlement. |
| Work Item | Claimable coordination record with ownership, lease fencing, discussion, and recorded outcomes and completion. |
| Task | Durable protocol or platform handle for asynchronous work. A task identifier is not by itself proof of completion. |
| Workstation | Bounded Sandbox lease for jobs that need files, processes, a repository, or operating-system tools. It is additive compute, not the tedi’s identity. |
Capabilities
| Term | Meaning |
|---|---|
| MCP app | Tenant-configured collection of tools, resources, prompts, or widgets exposed through the Model Context Protocol. |
| Connection | Organization- or user-scoped authorization linking an app to an external provider. |
| Tool | Callable capability with a schema, scope requirements, and an execution handler. |
| Skill | Reusable procedure a tedi can learn, run, evaluate, and improve; some skills run on a schedule as automations. |
| Code Mode | Direct gateway lane where an agent discovers namespaced tools and composes bounded JavaScript calls without creating a Home run. |
Governance and proof
| Term | Meaning |
|---|---|
| Policy | Rule that permits, denies, constrains, or escalates an action. |
| Approval | Explicit human or accountable-worker decision required before a protected action. |
| Rationale | Durable explanation associated with a decision or run; it is context, not automatic proof. |
| Artifact | Addressable output such as a report, file, patch, or sealed evidence bundle. |
| Completion evidence | Receipts and live readbacks supporting exact claims about what completed. |
The key distinction is continuity: a tedi and its organizational memory survive individual runs and runtime changes. Authority stays scoped per action, no principal approves its own request, and a recorded outcome stays separate from independent verification of that outcome. Together those are what it means to hold an agent accountable.
Continue with Digital workers, Governance and audit, or the Getting started guide.