An ARXOBIT is the operator of one office of digital workers. It takes one directive from ARXOBOT, coordinates its office internally, and surfaces one consolidated output upward. ARX and orbit: it circles one office, and holds it together.
The offices are established; their operators are being built. No ARXOBIT runs as code yet, and none is presented here as running.
Four levels, each with one job. The human commands and never has to descend below the metanager.
The human who decides what matters. Sees everything; is never buried in it.
Turns intent into directives and quality-controls what comes back. It does not execute.
One directive in, one consolidated output out. Coordinates its workers, and answers for its office.
Each task, dispatched through ONTASX, done to its done-state, and handed back.
Every ARXOBIT carries a self-model: the edge of its office, and nothing past it.
Work outside its domain, or below its standard, is refused and returned, not attempted.
Defined triggers send a problem up to ARXOBOT instead of letting it sit.
However many workers were involved, the office returns one consolidated output.
One ARXOBIT per office. This is the whole workforce, organized the same way CALΞNDARYX schedules it and ONTASX dispatches to it.
ARXOBITs sit inside steps three and six: they take directives from ARXOBOT and run the offices ONTASX dispatches to.
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.