Skip to content

See what you have taught LUCID

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-15.

What have I taught LUCID?

Ask for every rule you have given LUCID, in plain words, with your reason and the day you gave it. Then list them yourself.

What you get: each rule you have taught LUCID, what it changes, the reason you gave and when you taught it.

Ask in plain words:

quox · talking to Quox

What have I taught LUCID so far? For each rule, tell me what it does and the reason I gave.

▤ AOCL │ L1 identity complete · allowed · 1ms

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

◐ QUOX │ command lookup ✔ QUOX │ command lookup │ matched: true, 0 tui, 0 cli · 4.8s

◐ LUCID │ goals ✔ LUCID │ goals │ 9 items, 9 confirmed, 0 proposed · 15.2s

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

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

◐ QUOX │ cli ✔ QUOX │ cli │ 0 exit code, 4322 duration ms · 5.4s

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

⛓ AEE │ envelope opened · stream_success

You've taught LUCID one rule so far.

Stock orders for Kestrel Cycles: tell me after

• What it does: LUCID treats one kind of inbox item,  hitl:01K793… , as FYI instead of
  urgent. It stays visible, but it won't count as something that needs you now.
• Your reason: "Stock orders for Kestrel Cycles are routine, tell me after."
• When: Taught on 13 November 2026 at 19:31 UTC. The rule is  les_mwfdi2gwcqm0sm .

This rule only lowers urgency. Security and approval items are protected, and only an
admin can mute or re-rate them, so this rule can't hide them.

If it no longer suits you,  quox lucid forget les_mwfdi2gwcqm0sm  removes it.

The list also holds nine goals, initiatives and decisions you've confirmed, such as the
outside security audit before the Harbour Bikes shop opens and locking down the dev
sessions keys. Those are things you told LUCID you want, not rules. I can go through
them if you'd like.

33.6s · 3 tools · 0 approvals

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

Quox read your rules and explained each one. It only read; every rule is unchanged.

Terminal window
quox lucid teach <target> urgency=fyi --scope kind --reason "Stock orders for Kestrel Cycles are routine, tell me after"

The target is the item you are teaching about. --scope says how far the rule reaches: subject (the default), kind or area. The reason is kept with the rule, so you can see later why you gave it.

your rules
quox lucid lessonsID                    SCOPE    TARGET                             RULE           REASON                                                        TAUGHTles_mwfdi2gwcqm0sm    kind     hitl:01K793B4S3B82MV9WZD9RCNYAP    urgency=fyi    Stock orders for Kestrel Cycles are routine, tell me after    2026-11-13 19:31
From a real run in our proof org, on a sample rule.

TAUGHT is in UTC. --json gives the same rules with taught_at as an ISO date.

A rule changes how LUCID rates matching items, for example from urgent to FYI. By design, only an org admin or owner can teach a rule that quiets security or approval items (not yet shown in a recorded run).

Terminal window
quox lucid forget <id>

Use the ID from quox lucid lessons.