Every task knows why it exists.

Operium links goals, decisions, tasks and the actions of people and AI agents into one graph — showing not only what is being done, but why, by whom, and toward which result.

OPERIUM HQ / WORKER
⌘K
Open tasks
48
+6 THIS WEEK
In progress
18
37% LOAD
Completed
124
+12%
Space tempo
72
+8 PTS
Space tempo · 30 days
72Stable
OPER-218Worker V2: shell and routingHighToday
OPER-221Canonical space switcherMediumJul 15
OPER-226Entity cache synchronisationHighJul 18
OPER-229Route transition telemetryLowJul 22
6 — 1213 — 1920 — 2627 — 23 — 9
Worker V2: shell and routing
Canonical space switcher
Entity cache synchronisation
Route transition telemetry
07
Services in the platform
04
Views of the work
01
Execution graph
OPERIUM ID · WORKER · NOTES · DRAW · DESIGN · MESSENGER · ORCHESTRA · LEX ·  OPERIUM ID · WORKER · NOTES · DRAW · DESIGN · MESSENGER · ORCHESTRA · LEX · OPERIUM ID · WORKER · NOTES · DRAW · DESIGN · MESSENGER · ORCHESTRA · LEX ·  OPERIUM ID · WORKER · NOTES · DRAW · DESIGN · MESSENGER · ORCHESTRA · LEX · 

A new species of execution system. Operium is built around the execution graph: goals, decisions, tasks and the actions of people and AI agents live in one structure instead of five separate tools.

FIG 0.1
One structure
A single graph instead of a pile of trackers, docs and spreadsheets.
FIG 0.2
People and agents
AI agents act as participants in execution, not as a plugin on the side.
FIG 0.3
Faster decisions
Context sits next to the work — fewer approvals and fewer questions.
LEX / LINKED EXECUTION GRAPH

Our own graph model linking goals and work

LEX is Operium’s architectural concept, not an industry standard. Goal, decision, task and action live in one graph, and every edge answers the question “why”.

01
Goal
Why we do this and how we know we got there.
02
Decision
What we chose, the alternatives, and who decided.
03
Task
A unit of work with a date, an owner and a status.
04
Action
What a person or an AI agent did — and how it moved the result.
Goal
WHY
Decision
CHOICE
Task
WORK
Action
ACT
HUMANAI AGENT
01 / Views

One body of work, four points of view

List
SECTIONS & PRIORITY
Timeline
DEPENDENCIES & MILESTONES
Calendar
DATES IN CONTEXT
Overview
TEMPO & RISK
OPER-218Worker V2: shell and routingHighToday
OPER-221Canonical space switcherMediumJul 15
OPER-226Entity cache synchronisationHighJul 18
OPER-229Route transition telemetryLowJul 22
6 — 1213 — 1920 — 2627 — 23 — 9
Worker V2: shell and routing
Canonical space switcher
Entity cache synchronisation
Route transition telemetry
MON
Worker V2: shell and routing
Canonical space switcher
TUE
Worker V2: shell and routing
Entity cache synchronisation
WED
Canonical space switcher
Entity cache synchronisation
THU
Worker V2: shell and routing
Canonical space switcher
FRI
Worker V2: shell and routing
Entity cache synchronisation
Open tasks
48
+6 THIS WEEK
In progress
18
37% LOAD
Completed
124
+12%
Space tempo
72
+8 PTS
Space tempo · 30 days
72Stable
01 / LIST
02 / Analytics

A tempo you can read, not a report

Metrics readable from across the room: tempo, load, the risks of the week. No exports, no dashboards assembled by hand.

Open tasks
48
+6 THIS WEEK
In progress
18
37% LOAD
Completed
124
+12%
Space tempo
72
+8 PTS
OPERIUM / OVERVIEW
Space tempo · 30 days
72Stable
OPER-218Worker V2: shell and routingHighToday
OPER-221Canonical space switcherMediumJul 15
OPER-226Entity cache synchronisationHighJul 18
OPER-229Route transition telemetryLowJul 22
03 / AI

Voice turns into structure

Orchestra transcribes a voice note and breaks it into tasks, owners and dates — straight into the right node of the graph. AI agents act as participants in execution, not as a plugin on the side.

Todo12
OPER-2704
Track app startup timing
ANALYTICS
OPER-2703
Faster Worker shell launch
PERFORMANCE
OPER-926
Remove UI inconsistencies
UI
In progress03
OPER-1487
Remove contentData from the API
API
OPER-1028
Launch page assets
DESIGN
OPER-2187
Duplicate requests on poor network
BUG
Done48
OPER-924
Upgrade the agent engine
ORCHESTRA
OPER-901
Cache write paths
CORE
OPER-880
Entity cache metrics
ANALYTICS
THREAD IN #PRODUCT
···
AK
Anna4:28 PM
Feels like we could render sooner and load the rest in the background. Worth tracking startup timing too.
IL
Ilya4:40 PM
@Orchestra create the issues and assign them to me
▶
0:24
O
OrchestraAI
Created 3 issues:
Collect migration risksANNA · JUL 23
Approve the cutover planILYA · JUL 25
Update the runbookAGENT · TODAY
Reply…⌘↵
1.1Orchestra
1.2Triage
1.3Customer requests
1.4Approvals
04 / Personal productivity

A person’s day, not only a team’s sprint

The personal layer sits inside the same system: what you do today is linked to the team’s goals instead of living in a separate app.

01
To-do list
Important first, urgent second.
02
Eisenhower matrix
Do, schedule, delegate, drop.
03
Habit tracker
A weekly rhythm without another app.
04
Focus timer
One block of attention, one task.
OPERIUM / MY DAY
OPER-218Worker V2: shell and routingHighToday
OPER-221Canonical space switcherMediumJul 15
OPER-226Entity cache synchronisationHighJul 18
OPER-229Route transition telemetryLowJul 22
05 / Platform

Seven services, one account

Operium ID
Single sign-on, roles and access.
ACCESS
Worker
Tasks, projects and views.
WORK
Notes
Documents and knowledge base.
DOCS
Draw
Diagrams and shared boards.
CANVAS
Design
Mockups, review and handoff.
UI
Messenger
Discussion in the context of the work.
TALK
Orchestra
AI agents and automation.
AGENTS
One account, one graph, one permission model. Turn services on as you need them.
Start free →
06 / Who it is for

For teams that measure results, not tickets

01
Product teams
10–50 people running several projects in parallel.
02
Operations departments
Mid-size and large business with recurring processes.
03
Startups and founders
When the goal changes faster than the backlog.
04
Moving off Jira
A clear migration path for processes and history.
OPERIUM

Start with a single goal

Create a space, link your first goal to real tasks — and see what execution looks like end to end.