Skip to content

Pass the WebRTC signal to decision machines - #3855

Merged
forgetso merged 1 commit into
mainfrom
feat/webrtc-dm-input
Nov 13, 2026
Merged

forgetso merged 1 commit into
mainfrom
feat/webrtc-dm-input

Conversation

@forgetso

Copy link
Copy Markdown
Member

What changed: The provider already stores a WebRTC result on each session. It's a comparison of where the browser's STUN traffic came from against the HTTP request's address. Decision machines now receive that result:

  • Routing machines: raw.webrtc, on the first pass and on the pass after a solve.
  • Verify-time decide rules: webrtc, for PoW, image, puzzle and icon-order verification.
  • Escalated sessions: keep the result from the session that collected it.
  • Session reads: the session field is now included in the projection used at verify.

Effect: Rules can route or decide on the outcome, for example sending mismatch (the UDP left from a different network than the HTTP) to a harder challenge. Nothing acts on it until a machine is written to.

Tests: The "forwards every session-derived field into decide()" tests for PoW, image and puzzle verification now include a WebRTC result and check it arrives. A new unit test covers the post-solve routing signals with and without it. Provider unit suite: 2,348 passing.

🤖 Generated with Claude Code

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@forgetso
forgetso enabled auto-merge (squash) November 13, 2026 09:40
@forgetso
forgetso merged commit a06ca60 into main Nov 13, 2026
32 checks passed
@forgetso
forgetso deleted the feat/webrtc-dm-input branch November 13, 2026 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant