Moments: skills teach moments, and a mount that misfires proposes its own removal (milestone 458 steps 8, 7b) #204
@@ -22,8 +22,8 @@ did not arrive, the action did not reach the moment on this install — offer
|
||||
does not apply — is a mount or a mapping that is wrong: take the moment off
|
||||
the rule, or `unmap_action` the action that reached it. Each of these
|
||||
changes what the operator's sessions receive, so offer it in one line and make
|
||||
it on their yes. [moments.md](moments.md) has the
|
||||
detail. A rule about a subject missed its WHAT, and the rest of this page is
|
||||
it on their yes. The skill's moments
|
||||
reference has the detail. A rule about a subject missed its WHAT, and the rest of this page is
|
||||
for that.
|
||||
|
||||
**Take it to the record first and the dial second.** A rule's `when_to_apply`
|
||||
|
||||
@@ -62,5 +62,5 @@ stops the question being asked again.
|
||||
The same tool answers proposals from a pass over the rules
|
||||
(`rules_to_mount`, `propose_rule_moments`, `rule_moment_proposals`): a pass
|
||||
proposes, and only the operator's yes mounts. Writing a NEW rule is different
|
||||
— its moments are part of writing it, and
|
||||
[writing-records.md](writing-records.md) says how.
|
||||
— its moments are part of writing it, and the
|
||||
skill's guide to writing records says how.
|
||||
|
||||
Reference in New Issue
Block a user