docs(rust): phase 10 — notifications and engagement (PLAN.md §25, PROTOCOL.md §13) #265

wtclaude · 2026-09-23T18:42:32Z

wtclaude commented

2026-09-23 18:42:32 +00:00

What & why

Phase 10 of module-rust, in two commits:

Plan of record (committed before any code). This is PLAN.md §25 with the org lead's D59–D68. It also makes these edits elsewhere:
- the R7 amendment: no announce leg or post hook in phase 10 (D62);
- the §10 corrections: there's no self ceiling, clan.member.added duplicates core's own trigger, and the two player audiences were one set;
- the updated phase row.
As built (§25.5–25.8) plus PROTOCOL.md §13 (protocol 7).

Covered in there:

the live walk that met the criterion on the Oxide rig;
four things the rig found:
- no generic notice said which server;
- attackerId was null for a spawned player;
- a disband's roster could be gone before the disband was read;
- in-app subscribers is effectively everyone;
what isn't proven.

Code PRs: Module-Rust, Rust-Plugins and Rust-Link feat/phase-10-engagement (into edge).

Checklist

Docs match the code as merged in the paired PRs.

AI-assisted contributions (required)

AI tools were used. Tool(s): Claude Code (Claude Opus 5.5). AI-authored commits carry a Co-Authored-By trailer.

License

I agree that my contribution is licensed under this project's license (GNU GPL v3.0 or later).

🤖 Generated with Claude Code

https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

## What & why Phase 10 of module-rust, in two commits: 1. **Plan of record** (committed before any code). This is PLAN.md §25 with the org lead's D59–D68. It also makes these edits elsewhere: - the R7 amendment: no announce leg or post hook in phase 10 (D62); - the §10 corrections: there's no `self` ceiling, `clan.member.added` duplicates core's own trigger, and the two player audiences were one set; - the updated phase row. 2. **As built** (§25.5–25.8) plus **PROTOCOL.md §13** (protocol 7). Covered in there: - the live walk that met the criterion on the Oxide rig; - four things the rig found: - no generic notice said which server; - `attackerId` was null for a spawned player; - a disband's roster could be gone before the disband was read; - in-app `subscribers` is effectively everyone; - what isn't proven. Code PRs: Module-Rust, Rust-Plugins and Rust-Link `feat/phase-10-engagement` (into `edge`). ## Checklist - [x] Docs match the code as merged in the paired PRs. ## AI-assisted contributions (required) - [x] AI tools were used. Tool(s): `Claude Code (Claude Opus 5.5)`. AI-authored commits carry a `Co-Authored-By` trailer. ## License - [x] I agree that my contribution is licensed under this project's license (**GNU GPL v3.0 or later**). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

wtclaude added 2 commits 2026-09-23 18:42:34 +00:00

docs(rust): phase 10 plan of record (PLAN.md §25, D59-D68) aa148adfc6

The notifications and engagement phase, as decided by the org lead on
2026-09-23: the raid alert goes to everyone authorised on the tool
cupboard, covers doors and external walls, never names the raider, and
fires online or offline with the choice left to a rule condition.
Nothing reaches the game this phase, which amends R7. Also corrects §10
where core's contract disagreed with it (there is no `self` ceiling).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

docs(rust): phase 10 as built — protocol 7 and the raid alert cb8e8853f6

PLAN.md §25.5-25.8: what shipped, the walk that met the criterion on the
Oxide rig, the four things the rig found (every generic notice never
said which server; attackerId null for a spawned player; a disband
roster gone before the disband was read; in-app `subscribers` being
everyone), and what is not proven. PROTOCOL.md §13 specifies protocol 7.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY

whitlocktech merged commit b7d9872fed into main

2026-09-23 18:43:16 +00:00

whitlocktech referenced this issue from a commit

2026-09-23 18:43:16 +00:00

Merge pull request 'docs(rust): phase 10 — notifications and engagement (PLAN.md §25, PROTOCOL.md §13)' (#265) from docs/rust-phase-10 into main

whitlocktech deleted branch docs/rust-phase-10

2026-09-23 18:43:17 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#265