A XIMΞTIX instrument · the loop ledger

Every loop it opens, it closes.

ARXECUTYX takes each capture and turns it into an executable record: what gets done, how anyone can tell it is done, and when it is due. Then it holds the loop open until completion is confirmed, and raises it the moment it slips.

Free with an email sign-up. Captures arrive from CAPTURYX.

01 · Two gates · running now

ARXECUTYX does not direct work. It makes sure it finishes.

It stands at both ends of the loop. At the start, it turns a raw capture into something that can be executed. At the end, it confirms the work reached its done-state, and counts it.

Receive

Word for word.

Captures arrive from CAPTURYX exactly as they were written, and stay that way beside the record they become.

Open

No done-state, no loop.

A loop opens only with a what, a done-state and a due date. Each one gets a directive number.

Hold

Nothing goes quiet.

Open, on task, ready to verify. Past its due date, or silent for 72 hours, a loop rises to the top of the ledger.

Close

Confirmed, not assumed.

A loop closes when its done-state is confirmed. Then it counts toward the one number that matters.

02 · Execution integrity

One number for follow-through.

How much of what was decided actually got done. Aborted loops stay in the count: a loop that was opened and never finished is not quietly forgotten.

Loops closed÷loops openedTarget 98%
WhenARXECUTYX
Completed within its parametersConfirms completion and closes the loop.
Past its due dateFlags it as overdue, at the top of the ledger.
No signal for 72 hoursFlags the loop as silent, so it is re-routed or re-scoped.
Integrity below 90%Turns the score red: the loop discipline itself needs attention.
03 · The loop

From captured to confirmed.

ARXECUTYX is steps two and seven of a closed loop. Here is the whole of it, and what is running today.

  1. 01

    CAPTURYX captures

    Your intent, in your words, the moment it appears.

    Running
  2. 02

    ARXΞCUTYX opens the loop

    The capture becomes an executable record: what, the done-state, and when it is due.

    Running
  3. 03

    ARXOBOT directs

    The metanager decides whether, who and when, and issues the directive. It does not execute; it metanages.

    In build
  4. 04

    TASXYX sequences

    The directive becomes an ordered sequence of tasks: who does what, in what order, by when.

    In build
  5. 05

    CALΞNDARYX schedules

    Every task on one calendar, seen by all workers, by group, by office, or by one worker.

    Running
  6. 06

    ONTASX dispatches

    Each task goes to the right office of digital workers and is tracked while it is on task.

    In build
  7. 07

    ARXΞCUTYX closes the loop

    Completion confirmed, delays raised, and the integrity score kept.

    Running

Until ARXOBOT, TASXYX and ONTASX run, the operator directs, sequences and assigns by hand inside the ledger. The loop still opens, and still closes.

04 · Yours

The ledger stays on your device.

The ledger is kept in your own browser. Captures come in, and the schedule goes out to CALΞNDARYX, inside the link itself; no server stores either. Each directive exports as a Markdown file for your own records, and the whole ledger backs up to one file.

Open the ledger

Your first loop is one step away.

Enter your email and the ledger opens straight away. This device stays signed in; there is no password to remember.

We use your email for one thing: to tell you when the next part of the loop opens. What you record stays on your device.

You already have access on this device. Open the ledger →

Free. When email links are switched on, you also receive a link to open the ledger on your other devices.