Part IX: the whole journey and the sentences to remember; forbidden words removed
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
45dd65b48e
commit
01f681165f
4 files changed
+111
-8
No files matched your search
@@ -88,7 +88,7 @@ Three kinds of message, named only after being used:
|
||||
|
||||
Past tense is a useful hint for Events. For Intent the test is two questions: does the message report something that happened? No. Something currently true? No. Then it requests behaviour.
|
||||
|
||||
One trap: *publishing* an Intent is of course something that happened. Classify by what the message says, not by the fact that it exists — otherwise every message becomes an Event and the vocabulary stops being useful.
|
||||
One trap: *publishing* an Intent is naturally something that happened. Classify by what the message says, not by the fact that it exists — otherwise every message becomes an Event and the vocabulary stops being useful.
|
||||
|
||||
Status deserves its own note, because the instinct is to **ask** for it: "what are your subscriptions?" But asking is a call, and a call needs the asker to know the component, to know it is up, and to wait. Status is **published**: ROT13 publishes `ROT13/S/subscriptions` whenever its wiring changes, and anyone interested reads it. The reader then needs a topic, not a component, and ROT13 never learns who audits it. Each kind answers a different question:
|
||||
|
||||
|
||||
Reference in new issue
Block a user