ONTASX is the execution tier. It dispatches each task to the office of digital workers built for it, and tracks the task while it is on task: started, blocked, done. One unit of work on task is an onit.
No digital worker runs as code yet. Today the operator assigns each step to an office and a worker by hand inside ARXΞCUTYX; ONTASX will make that assignment, and hold it.
In a conventional organization, who gets the work depends on who is loudest, closest or free. ONTASX assigns by fit, so the signal that reaches the worker is the one the directive sent.
Each task goes to the office whose domain it falls in, never to whoever is nearest.
Inside the office, the task goes to the worker built for it, with capacity for it this week.
Started, blocked, done. A task that goes silent is raised by ARXΞCUTYX after 72 hours.
When a task reaches its done-state, ONTASX hands it back, and ARXΞCUTYX confirms it.
Each office is run by its own operator, an ARXOBIT, and staffed by digital workers. Every task ONTASX dispatches lands in exactly one of them.
ONTASX is step 6 of a closed loop. Here is the whole of it, and what is running today.
Your intent, in your words, the moment it appears.
The capture becomes an executable record: what, the done-state, and when it is due.
The metanager decides whether, who and when, and issues the directive. It does not execute; it metanages.
The directive becomes an ordered sequence of tasks: who does what, in what order, by when.
Every task on one calendar, seen by all workers, by group, by office, or by one worker.
Each task goes to the right office of digital workers and is tracked while it is on task.
Completion confirmed, delays raised, and the integrity score kept.