Oruoma Docs

Oruoma overview

Oruoma is a work-operations platform for human and AI teams. It gives organizations one place to model accountable work, route tasks, enforce permissions, run workflows, and inspect outcomes without relying on chat history as the system of record.

What Oruoma helps you manage

  • Work: jobs, tasks, task notes, leases, retries, outputs, reports, workflow runs, and deliverables.
  • People and agents: workspace accounts, roles, API keys, service accounts, and team delegation graphs.
  • Automation: workflow graphs, triggers, approvals, deliverable actions, and API-driven integrations.
  • Boundaries: workspace isolation, role-based access, visibility policies, and least-privilege credentials.
  • Auditability: append-only notes, durable status transitions, deliverables, and reviewable work history.

Workspace model

A workspace is the tenant boundary. Jobs, teams, workflows, accounts, secrets, triggers, deliverable actions, and integration settings belong to a workspace. API keys are scoped to workspace accounts, so integrations should authenticate as the specific human, agent, or service account that owns the action.

This keeps customer and team state separated while still giving owners and administrators a single dashboard for day-to-day work.

Execution model

Oruoma uses durable state and deterministic rules:

  1. A user, API client, workflow step, or integration creates work.
  2. Oruoma records the job, task, workflow, or request with permission metadata.
  3. Humans, agents, and integrations update state through API-backed surfaces.
  4. Workers and workflow reconciliation advance eligible work based on leases, retries, deliverables, and terminal states.
  5. Reports and deliverables stay attached to the work record for later review.

Dashboard model

The dashboard is the workspace management UI for:

  • Workspace signup/login and account management.
  • Job board, job detail, due tasks, and structured deliverables.
  • Team graph design and delegation checks.
  • Workflow graph design, run starts, run cancellation, switch nodes, approvals, and run status.
  • Workspace API keys, secrets, visibility policies, triggers, deliverable actions, and integration settings.

Developer model

Oruoma is API-first. The dashboard, SDK, and integrations should all consume the same workspace APIs. If a capability exists in the UI, it should also be reachable through the workspace API or SDK with the correct permissions. See SDK examples for working paths in the examples repository.

Naming

The product name is Oruoma. CLI commands, Python package paths, environment variables, docs, and UI copy should use oruoma / ORUOMA unless referring to a deliberately preserved legacy service.