docs(events): the site, the landing page, and the cutover step they found (Phase 16c) #233

wtclaude · 2026-09-10T03:08:12Z

wtclaude commented

2026-09-10 03:08:12 +00:00

Events Phase 16c — the last leg of the plan, and its record. Companion to
runicgateway.com#30 and .profile#6.

The finding worth keeping

16c began by closing 16b's missing seventh step (#232, merged). Six repositories were cut over
and every one shows 0 commits on edge that are not on main. This one showed 46: step 6
landed the record on edge rather than cutting edge over. So docs main opened EVENTS.md
with "revision 5. No code written. Read against … MODULE_API_VERSION 1.9.0 · sidecar protocol
5" while six repositories shipped the engine on protocol 7, and link/v6.md and v7.md — the specs
of record for two protocol versions — existed on no default branch anywhere.

Nothing in this workstream could have caught it, and the reason is the part worth writing down:
every check that guards a contract lives in the repository that depends on the contract, and a
documentation repository has no dependants. The one check that reads docs from outside is
runicgateway.com's checkReference.mjs — and 16c is the only phase that would ever have run it.
It failed with ✗ canonical doc link/v7.md.

What the record now says

EVENTS_PLAN.md §16 gains the 16c leg: the missing cutover step and how it surfaced, the site's two
new pages and the four decisions inside them, the privacy row the participation ledger owed, the
"Shard event catalog" rename, the .profile bullet, and the two stale numbers on the landing page
that cost a reader an afternoon.

Four judgement calls are recorded as choices rather than left implicit:

the twenty-seven Bridge.cfg keys became five groups, not an appendix, because EventsEnabled
is a second consent switch and belongs beside the ceilings it governs;
the calendar capability is deliberately not needsModule, because a bare core can author and
run an event and that marker means "present, correct and permanently empty";
the event-catalog page keeps its route while changing its title, so nothing outside that
repository breaks;
no screenshots, because capturing them means standing the whole rig back up for images no check
requires.

And the plan is marked COMPLETE

All seventeen phases built and on main in every repository they touch. The platform the workstream
leaves behind: sidecar v2.2.0, overlay v1.2.0, bundle 2026.09.10 on protocol 7,
Module-uo v1.2.2, MODULE_API_VERSION 1.10.0. edge stays standing, unused, everywhere.

No contract moves in this phase. No EVENTS.md change, no MODULE_API_VERSION change, no
protocol change, no release — 16c makes the contracts already moved legible from outside the
organisation.

AI-assisted contribution. Drafted with Claude Code (Opus 5).

🤖 Generated with Claude Code

https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4

**Events Phase 16c** — the last leg of the plan, and its record. Companion to `runicgateway.com#30` and `.profile#6`. ## The finding worth keeping **16c began by closing 16b's missing seventh step** (#232, merged). Six repositories were cut over and every one shows **0** commits on `edge` that are not on `main`. This one showed **46**: step 6 landed the record *on* `edge` rather than cutting `edge` over. So `docs` `main` opened `EVENTS.md` with *"revision 5. **No code written.** Read against … `MODULE_API_VERSION` 1.9.0 · sidecar protocol 5"* while six repositories shipped the engine on protocol 7, and `link/v6.md` and `v7.md` — the specs of record for two protocol versions — existed on no default branch anywhere. **Nothing in this workstream could have caught it**, and the reason is the part worth writing down: every check that guards a contract lives in the repository that *depends* on the contract, and a documentation repository has no dependants. The one check that reads `docs` from outside is `runicgateway.com`'s `checkReference.mjs` — and 16c is the only phase that would ever have run it. It failed with `✗ canonical doc link/v7.md`. ## What the record now says `EVENTS_PLAN.md` §16 gains the 16c leg: the missing cutover step and how it surfaced, the site's two new pages and the four decisions inside them, the privacy row the participation ledger owed, the "Shard event catalog" rename, the `.profile` bullet, and the two stale numbers on the landing page that cost a reader an afternoon. Four judgement calls are recorded as choices rather than left implicit: - the twenty-seven `Bridge.cfg` keys became **five groups, not an appendix**, because `EventsEnabled` is a second consent switch and belongs beside the ceilings it governs; - the calendar capability is deliberately **not** `needsModule`, because a bare core can author and run an event and that marker means "present, correct and permanently empty"; - the event-catalog page keeps its **route** while changing its title, so nothing outside that repository breaks; - **no screenshots**, because capturing them means standing the whole rig back up for images no check requires. ## And the plan is marked COMPLETE All seventeen phases built and on `main` in every repository they touch. The platform the workstream leaves behind: sidecar **v2.2.0**, overlay **v1.2.0**, bundle **2026.09.10** on **protocol 7**, `Module-uo` **v1.2.2**, `MODULE_API_VERSION` **1.10.0**. `edge` stays standing, unused, everywhere. **No contract moves in this phase.** No `EVENTS.md` change, no `MODULE_API_VERSION` change, no protocol change, no release — 16c makes the contracts already moved legible from outside the organisation. --- **AI-assisted contribution.** Drafted with Claude Code (Opus 5). 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_016wDDVXWMDz82WqE1i969r4

wtclaude added 1 commit 2026-09-10 03:08:13 +00:00

docs(events): the site, the landing page, and the cutover step they found (Phase 16c) 81b55ac29b

The last leg of the events plan, and the record of what it turned up.

**16c began by closing 16b's missing seventh step.** Six repositories were cut
over and every one showed 0 commits on `edge` that are not on `main`. This one
showed 46: step 6 landed the record *on* `edge` rather than cutting `edge` over,
so `docs` `main` opened `EVENTS.md` with "revision 5. No code written. Read
against ... MODULE_API_VERSION 1.9.0 - sidecar protocol 5" while six repositories
shipped the engine on protocol 7 — and `link/v6.md` and `v7.md` existed on no
default branch anywhere.

Nothing in this workstream could have caught that, and the reason is worth
writing down: every check that guards a contract lives in the repository that
DEPENDS on the contract, and a documentation repository has no dependants. The
one check that reads `docs` from outside is `runicgateway.com`'s
`checkReference.mjs`, and 16c is the only phase that would ever have run it.
Closed by #232.

**The site.** Nine `checkFacts` values and twenty-seven `Bridge.cfg` keys, both
red before the phase started — which is the bargain that repository's §12 struck.
Two pages, the treatment Teams has. Two capability entries, the calendar one
deliberately not `needsModule` because a bare core can author and run an event.
A `deploy-events` privacy row, because the participation ledger is personal data
and nothing named it. And `reference/event-catalog` retitled "Shard event
catalog", route unchanged, because two things in the documentation were called an
event catalog.

**`.profile`.** One bullet saying the posture rather than the feature list, and
two stale numbers: protocol 5 → 7 in the four values the installer prints, and
module-uo v1.1.0 → v1.2.2.

**And the plan is marked COMPLETE.** All seventeen phases on `main`, in every
repository they touch. No contract moves in this phase; it makes the ones already
moved legible from outside the organisation.

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

whitlocktech merged commit 132620e8b3 into main

2026-09-10 04:28:17 +00:00

whitlocktech deleted branch docs/events-p16c-site

2026-09-10 04:28:18 +00:00

whitlocktech referenced this issue from a commit

2026-09-10 04:28:19 +00:00

Merge pull request 'docs(events): the site, the landing page, and the cutover step they found (Phase 16c)' (#233) from docs/events-p16c-site into main

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: RunicGateway/docs#233