docs(readme): the engagement system, protocol 5, and module-uo v1.1.0 #5

wtclaude · 2026-09-01T18:15:34Z

wtclaude commented

2026-09-01 18:15:34 +00:00

Engagement Phase 13, step 8 — the step that is conditional: ".profile/README.md, only if this lands as a headline capability." It did, by your call, and that condition is the point — a landing page that lists every feature is one nobody reads.

The capability

One bullet, in the "how they fit together" list. It leads with the operator rather than the mechanism, and names the one property here that is a security boundary rather than a feature: a trigger declares the widest audience a rule may ever be given, so a sensitive game event cannot be mailed to everyone by a misconfiguration. It also says a module brings its own triggers, because that is the part that is about the platform rather than about email — for UO, a house about to collapse, a vendor running out of gold, a champion spawn, a new governor.

Two things that were about to mislead an operator

Both are cutover outputs, and both sit in the quick start where someone is copying from the page:

the installer's sample output printed Protocol version 4 — the paired bundle is 2026.09.01 and the wire is 5
the module quick start pinned v1.0.1 in the manifest URL and the MODULES= line — v1.1.0 is the release carrying the shard triggers

Not touched, and worth a separate decision

This page says "eight repositories" and lists eight. runicgateway.com is not among them — it predates this workstream and has nothing to do with it, so it is left alone here rather than folded into an engagement PR. CLAUDE.md's repo table has the same gap. Happy to fix both in one pass if you want it.

AI-assisted: written with Claude Code.

🤖 Generated with Claude Code

**Engagement Phase 13, step 8** — the step that is conditional: *"`.profile/README.md`, only if this lands as a headline capability."* It did, by your call, and that condition is the point — a landing page that lists every feature is one nobody reads. ### The capability One bullet, in the "how they fit together" list. It leads with the operator rather than the mechanism, and names the one property here that is a **security boundary** rather than a feature: a trigger declares the widest audience a rule may ever be given, so a sensitive game event cannot be mailed to everyone by a misconfiguration. It also says a module brings its own triggers, because that is the part that is about the *platform* rather than about email — for UO, a house about to collapse, a vendor running out of gold, a champion spawn, a new governor. ### Two things that were about to mislead an operator Both are cutover outputs, and both sit in the quick start where someone is copying from the page: - the installer's sample output printed **`Protocol version 4`** — the paired bundle is `2026.09.01` and the wire is **5** - the module quick start pinned **v1.0.1** in the manifest URL *and* the `MODULES=` line — **v1.1.0** is the release carrying the shard triggers ### Not touched, and worth a separate decision This page says "**eight repositories**" and lists eight. **`runicgateway.com` is not among them** — it predates this workstream and has nothing to do with it, so it is left alone here rather than folded into an engagement PR. `CLAUDE.md`'s repo table has the same gap. Happy to fix both in one pass if you want it. - [x] AI-assisted: written with Claude Code. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

wtclaude added 1 commit 2026-09-01 18:15:35 +00:00

docs(readme): the engagement system, protocol 5, and module-uo v1.1.0 029ba2893e

The engagement cutover landed on 2026-09-01 and three things on this page stopped
being true with it.

The capability itself is the reason for the change: the site now talks to its
players, and an operator decides when. It is a headline capability by the org
lead's call, which is the condition ENGAGEMENT.md Phase 13 step 8 attaches to
touching this file at all -- a landing page that lists every feature is a landing
page nobody reads.

The bullet leads with the operator rather than the mechanism, and names the one
property that is a security boundary rather than a feature: a trigger declares
the widest audience a rule may ever be given, so a sensitive game event cannot be
mailed to everyone by a misconfiguration.

The other two are cutover outputs and would mislead an operator directly:

  * the installer's sample output prints "Protocol version 4"; the paired bundle
    is 2026.09.01 and the wire is 5.
  * the quick start pins module-uo v1.0.1 in both the manifest URL and the
    MODULES= line; v1.1.0 is the release that carries the shard triggers.

Co-Authored-By: Claude <noreply@anthropic.com>

whitlocktech merged commit 159eb53e73 into main

2026-09-01 18:55:30 +00:00

whitlocktech deleted branch docs/engagement-and-protocol-5

2026-09-01 18:55:31 +00:00

whitlocktech referenced this issue from a commit

2026-09-01 18:55:31 +00:00

Merge pull request 'docs(readme): the engagement system, protocol 5, and module-uo v1.1.0' (#5) from docs/engagement-and-protocol-5 into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/.profile#5