Skip to content

Find the right specialist for a job

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. CLI 0.5.0, checked 2026-10-19.

Who should do this job?

Ask which specialist has done this kind of task best before handing it over, then look them up yourself.

What you get: which specialist has the strongest record for the job you have in mind, how big that record is, and the signed records it rests on.

Describe the job and ask who has done it best:

quox · talking to Quox

If I wanted a security review done, which specialist has the best track record for that kind of task here?

▤ AOCL │ L1 identity complete · allowed · 1ms

▤ AOCL │ L3 policy gate complete · proceed · 7ms

◐ DELEGATION │ router advise ✔ DELEGATION │ router advise │ 1 ranked, 2 sample size, low confidence: true · 5.3s

⛓ AEE │ envelope opened · stream_success

Sentinel has the best record for security reviews here, though the evidence is thin.

It is the only specialist with any history on this kind of task. It has completed 2 of 2
delegations with no breaches, reroutes or degrades, and averages about 60 seconds per
run. Those two runs are a small sample, so treat the ranking as a weak prior. The record
also measures reliability (finishing within budget), not whether the answers were
correct.

The evidence is two signed routing records, ART_MVCTNJPT_54C81D60B1E9 and
ART_MVBUN4H3_3B274B69CEC8.

If your review is a formal testing engagement with scope and targets, the security
engagement specialists are a better fit than Sentinel. They have no routing history yet,
so I can't rank them on track record.

Shall I hand Sentinel the review? If so, tell me what it should cover.

17.3s · 1 tool · 0 approvals

A real turn on our own install (CLI 0.3.1, 19 Oct 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 19 Oct 2026 · test report mvfta9

Quox asked its delegation router for advice. The router ranks specialists by their past delegations for this kind of task: how many they finished, how many broke a budget or were rerouted, and how long they took. It says when the sample is too small to lean on, and it does not hand the job over until you say so.

The track-record ranking comes from the delegation router, which you reach by asking Quox. The specialists themselves you can look up directly.

secops agents
quox agent list --family secopsAgent ID             Name        Family    Source      Level    Status/Plugin    Toolsargus                ARGUS       secops    registry    1        plugin:wazuh     33findings_verifier    ATTEST-Q    secops    registry    1        -                16recon_specialist     RECON-Q     secops    registry    1        -                20security_lead        DRAGO       secops    registry    1        -                21sentinel             WARDEN      secops    registry    1        -                31web_specialist       PROBE-Q     secops    registry    1        -                20
From a real run on a demo organisation.
sentinel
quox agent get sentinelWARDEN────────────────agent_id          sentinelname              WARDENrole              managerlevel             1requires_plugin   -family            secopsdescription       Security watchdog - monitors threats and vulnerabilities.tool_count        31entitled          -source            registry
From a real run on a demo organisation.

Other families work the same way: quox agent list --family devops, --family monitoring, --family development and so on.

Quox read the delegation records for this kind of task and ranked the specialists on them. Reading changes nothing, so no approval was needed, and no work was handed to anyone.

A track record measures reliability, finishing within budget, not whether the answers were right. Two runs is a weak signal, and Quox says so. A specialist with no history is not ranked at all, so a formal security engagement may still suit a specialist the router cannot rank yet.

Reading needs no undo.