Try it as Hollis.

What to look for

Nobody enters a Pool without saying yes. §5.1: “A Profile MUST NOT be added to a Pool without the owner’s explicit consent. Silent inclusion is forbidden. There is no exception.”

1. The confirmation step. “Each link MUST open a confirmation step that shows the Pool’s name, charter, curator and visibility and asks the owner to confirm.” (§5.2) The page Hollis sees shows all four, numbered.
2. Only the button counts. “Only an explicit action on that step, such as a button that sends a POST request, records a decision. A GET request to either link alone MUST NOT record a decision.” (§5.2) The reason takes one line: “email security scanners open every link in a message.”
3. A no is remembered. A decline “MUST be recorded as declined for that Pool and MUST NOT be re-submitted by the same Curator without owner permission.” (§5.2) Press “Ask again” after a no and watch it be refused.
4. Silence expires. “A request’s expires_at MUST equal its sent_at plus the window,” and the window is literally 14 days unless the manifest sets handshake_window_days (§5.2). Press “Let the window pass.”
5. The log. Every step shows the exact JSON message the protocol would send. Check each against schemas/handshake_message.schema.json.

Builders: K.1 maps the handshake and the 6 message types. Curators: K.4 lists the rules you enforce, and its Field exercise 3 runs an invented profile through the whole handshake.