docs(plugin): the instruction surfaces teach moments - reading a line that arrived at one, correcting a misfire, and giving a new rule its moments (milestone 458 step 8, #4926)
CI & Build / Python lint (push) Successful in 13s
CI & Build / Plugin hooks (push) Successful in 16s
CI & Build / TypeScript typecheck (push) Successful in 56s
CI & Build / integration (push) Successful in 1m38s
CI & Build / Python tests (push) Failing after 1m59s
CI & Build / Build & push image (push) Skipped
CI & Build / Python lint (push) Successful in 13s
CI & Build / Plugin hooks (push) Successful in 16s
CI & Build / TypeScript typecheck (push) Successful in 56s
CI & Build / integration (push) Successful in 1m38s
CI & Build / Python tests (push) Failing after 1m59s
CI & Build / Build & push image (push) Skipped
Until now only the tool arguments knew moments existed. The guidance surfaces described rules as reached by resemblance alone: - using-scribe: a short reflex paragraph and a new reference file, moments.md. It covers reading "at <moment>, reached by <action>", the reply held once at reply.report, map_action / unmap_action offered in one line, and the step 7 proposal line answered with judge_rule_moments. - writing-records: asks WHEN a rule applies as well as what it is about. A rule, preference or process about a point in the work gets moments=[...] as it is written, and the trigger stays as the net. - missed-retrieval: a missed WHEN is mounted or mapped, not reworded. A misfire is unmounted or unmapped. - _INSTRUCTIONS: one clause (list_moments; mount rules about WHEN), 1594 of 1600 chars. - static context: injected lines include the rules mounted on a moment that was reached. - test_guidance_ownership: three owned topics, so the text cannot quietly drop out. Plugin minted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -185,6 +185,19 @@ TOPICS: tuple[Topic, ...] = (
|
||||
Topic("where a new rule goes, and its trigger", U, ("create_project_rule", "when_to_apply"),
|
||||
"whichever home it gets"),
|
||||
Topic("a rule vs the other entities", U, ("standing instruction",), "first ask whether it's a rule at all"),
|
||||
# Moments (milestone 458 step 8). Delivery at a moment and its in-session
|
||||
# corrections are owned by using-scribe's moments.md; the index carries one
|
||||
# clause, and a new rule's moments are asked where its home and trigger are.
|
||||
Topic("rules mounted on a moment arrive by lookup; correct a misfire in-session", U,
|
||||
("list_moments", "map_action", "unmap_action", "judge_rule_moments"),
|
||||
"it belongs in the session that noticed, not on a settings page",
|
||||
index=("list_moments", "moment")),
|
||||
Topic("a new rule about when gets its moments as it is written", U,
|
||||
("moments=[...]", "create_process(moments="),
|
||||
"then ask when it applies, as well as what it is about"),
|
||||
Topic("a missed when is mounted or mapped, not reworded", U,
|
||||
("update_rule(moments=",),
|
||||
"first ask whether it missed a when or a what"),
|
||||
# Milestone 416 step 9: the tuning tools shipped in #4102/#4104 and were
|
||||
# named on NO instruction surface — measured, `retrieval_tuning_history`
|
||||
# returned zero events. Machinery with no route to it.
|
||||
|
||||
Reference in New Issue
Block a user