Reference/Glossary
Glossary
| Term | Definition |
|---|---|
| Ether OS | The platform backend (ether-api) — tasks, context, harness, delivery, realtime. |
| Task | A unit of work with an ID, status, timeline, and optional delivery payload. |
| Harness | External app that claims a task, executes, and submits a result. |
| Execution bundle | Package returned on claim: prompt, scope, context refs, callback URLs. |
| Run ID | Identifier for one execution attempt; must match on heartbeat, steps, and result. |
| Lease | Time-bound claim on a task; extended via heartbeat. |
| Claim | POST …/claim — harness acquires lease and receives bundle. |
| Execution result | Final payload: submitted, blocked, or no_changes. |
| Context corpus | Markdown docs (profile.md, project.md, etc.) composed for the harness. |
| Pipeline ID | Classifier output (e.g. coding.github.v1) stored on task closure. |
| Execution domain | Where work runs (e.g. engineering.bugfix). |
| Delivery domain | How results are presented to the user. |
| task.delivered | WebSocket event + payload when a task completes successfully. |
| os.harness.step | WebSocket event for user-visible harness progress. |
| Ether Code | First-party reference harness in the ether-code repo. |
| @ether/os-sdk | TypeScript client for harness integrators. |
| Pull model | Harness calls claim with a known task_id. |
| Push model | ether-api POSTs work to ETHER_HARNESS_URL/v1/runs. |