Skip to content

Ask how sure LUCID is

Machine verified A machine ran this on our install and checked the result against the CLI. A test report is linked. Proven against quoxcli 0.6.2 on 2026-11-16.

How sure is LUCID?

When LUCID ties a finding to one of your goals, ask how sure it is, what it saw, and whether anyone has confirmed the link.

What you get: the difference between what LUCID saw and what it guessed. A finding can be serious while LUCID’s link to your goal is only a hunch. This keeps the two apart.

Ask in your own words:

quox · talking to Quox

LUCID seems to think the admin login problem could put opening the Harbour Bikes shop by spring at risk. How sure is it about that, and what is it going on?

▤ AOCL │ L1 identity complete · allowed · 1ms

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

◐ LUCID │ insights ✔ LUCID │ insights │ shadow: true, 1 items · 6.7s

⛓ AEE │ envelope opened · ops.tool · lucid_insights ok

◐ LUCID │ insights ✔ LUCID │ insights │ shadow: true · 1.8s

⛓ AEE │ envelope opened · ops.tool · lucid_insights ok

⛓ AEE │ envelope opened · stream_success

LUCID isn't very sure about this. It rates its confidence as low, and the insight is
still a candidate, not a confirmed fact.

What it's based on

• One observation: a high-severity security finding, "Harbour Bikes web shop: admin
  login has no rate limit", seen on 14 November.
• The finding is linked to your goal "Open the Harbour Bikes web shop by spring" only by
  shared words (harbour, bikes, shop). Nobody has linked the two, and LUCID's own note
  calls the link "inferred" and "related".
• It lists no missing evidence. That doesn't mean the evidence is complete. It means
  LUCID hasn't named what it would need.

Why it's still flagged high priority
The priority comes from the goal, not from the confidence. You marked that goal high, so
anything that might touch it ranks high.

What the finding means
An admin login with no rate limit allows unlimited password guesses. That's a real
weakness, and it's worth fixing before the shop goes live. Nothing LUCID has shown says
it would delay the launch. It would only matter if the fix is large or the launch is
blocked on a security sign-off.

What I'd do

1. Treat the missing rate limit as a normal pre-launch fix, which is usually a small
   config change.
2. Have someone link the finding to the goal if you want LUCID to track it properly.
   That would raise or lower its confidence based on real evidence.
3. I can ask sentinel to confirm the finding and estimate how much work the fix is. Do
   you want me to?

20.6s · 2 tools · 0 approvals

A real turn on our own install (CLI 0.6.2, 16 Nov 2026), replayed at speed. Names changed. Type the same words into quox.
✔ Machine verified against the CLI on 16 Nov 2026 · test report mwjt99

Quox read LUCID’s own record of the insight and answered plainly: LUCID’s confidence in the link is low, and the insight is still a candidate, which makes it an inference rather than a confirmed fact. It said what the guess rests on (one security finding that shares words with your goal), that nobody has linked the two, and why it still ranks high: the priority comes from your goal, which you marked high, not from how sure LUCID is.

This run used a test org with a seeded goal and seeded security findings.

1. List what LUCID would tie to your goals

Section titled “1. List what LUCID would tie to your goals”
lucid insights
quox lucid insights◉ LUCID │ insights │ 1 shadow · 15 in today's briefToday LUCID says 15 things need you. 1 of what it sees touches a goal you set. (Shadow: this does not change what LUCID says yet.) WHAT                                                          WHY                                                             PRIORITY    LINK"Open the Harbour Bikes web shop by spring" may be at risk    high finding: Harbour Bikes web shop: admin login has no ...    high        a guess, not linked
From a real run on the same test org, with the id column left out.

LINK says how each insight is tied to your goal: a guess, not linked means LUCID inferred it, and you linked it means you recorded it yourself.

Terminal window
quox lucid insights show <id>

Use an id from the list. It shows what was seen, what LUCID makes of it with its confidence, the limits of that reading, and why it ranks where it does.

Quox read LUCID’s insights for your org and opened the one you asked about. Nothing was changed: the link stays a guess until you accept or reject it.

quox lucid insights status shows whether the worker behind these insights is running for your org, with its recent runs and any failures.

Nothing to undo: this only reads.