Digital workers
A digital worker in Tedix is called a tedi. A tedi is a durable organizational asset rather than a single model invocation — the unit that carries accountability when work is done by an agent instead of a person.
What a worker owns
Each worker can have:
- a stable identity and organizational role;
- approved skills and connected tools;
- memory owned by its organization;
- policies, budgets, and approval requirements;
- durable tasks, rationale, artifacts, and audit evidence;
- a runtime that can recover without changing the worker’s identity.
What accountability requires
Tedix uses four properties to make a worker answerable for its work:
| Property | What it means |
|---|---|
| An identity that persists | The worker, its memory, and its record survive the run, the session, and a runtime change. |
| A budget that holds | Spend and capacity ceilings are owner-held. A worker cannot raise its own. |
| An approver who is never the requester | A protected action is decided by a designated approver — which may be another accountable worker, but never the principal that asked. |
| A record you can show | Who asked, who acted, under which policy, on what evidence, at what cost, with which outcome. |
One organization, many facets
An organization can create workers for departments, customers, projects, or bounded tasks. These workers can cooperate, but authority stays explicit: delegating work does not automatically delegate every credential or permission.
Durable does not mean uncontrolled
Tedix separates the worker’s long-lived identity from the compute used for an individual job. Routine work can run at the edge. Jobs needing a browser, repository, or operating-system process receive a bounded capability for that job and produce completion evidence.
The result is continuity without granting permanent, unrestricted machine access.