Warp API method naming survey

Arquillian Warp (https://github.com/arquillian/arquillian-extension-warp) has ability to intercept client requests which met certain criteria (e.g. matches requested URL) in order to execute and/or verify logic on server and collect exceptions which might arise on server (including failed assertions).

The important piece is ability send real request and execute code on server and bring results back to client, which is referred to as process of "request warping" in Arquillian Universe.

"We are warping request from a client to a server and back."


Note: Why do we need to define when request meets certain criteria?
- Warp was built to work with any type of HTTP emitting client, including automated real browsers.
- Clients can emit several requests for one response, thus we need to decide which request is the right one.
- It is optional step.

In the following API proposals, you can read:

Warp
.doSomethingOnClient // which emits (HTTP) request/-s
.whenCriteriaAreMet // optional: criteria what request need to meet
.doSomethingOnServer // which executes and verifies server logic


Now, which options seems to you as most precisely describing the process which is described above?

?77777I777777777.
~7IIIIIIIIIIIIIII7777$.
.=IIII7III?????????IIII77$Z.
.III77III??++~:~=+++???II777$=
I7II77II?:::::::::::::=??II777$$
+77$$7I::::..........,::::?II77$$Z.
.$7Z$7?~:................,::~II77$$Z.
.$$ZZ$=~....................::~I77$$Z.
$Z$ZZ=~,.....................:~~77$$ZZ
.ZZZZO=........................~~I7$$ZZ
ZZ88=~.........................~~7$ZZZ=
OO88=........................,.~~$$ZZZZ
OO88=.........................,:~$ZZZZI
.8O88=..........................:=ZZZZZ
D888=...................+$Z....==ZZZZZ
O88=,.OOOOO.......OOOOOOOO....==ZZZZ$
8888=.OOOOOO8....OOOOOOOO8...,=OOOZZ.
.O88D=.~88888:..I8888888=....=OOOZO.
$888=.....................=$OOZZ
OD88=..................==OOOZO.
.?ZD8D=..............,=OOOZZO
D888D==.........==8OOZZO.
7DD8888O$I7O8888OOO8.
.?DD88888888OO$.
...


===================================================================================

Options (you can rate bellow option list):

    #1

    Warp .initiate(Activity) .observe(What) .inspect(Inspection); - https://gist.github.com/4135348 - "Initiate request by client activity when observing given type of requests and inspecting server state"
    This is a required question

    #2

    Warp .initiate(Activity) .capture(What) .probe(Inspection); - https://gist.github.com/4135324 - "Initiate request by client activity when capturing given type of requests and probing server state"
    This is a required question

    #3

    Warp .fromClient(Activity) .toServer(Inspector) .observing(What); - https://gist.github.com/4135352 - "Warp from client to server when observing given request type"
    This is a required question

    #4

    Warp .given(Conditions) .when(Activity) .then(Inspect); - https://gist.github.com/4135342 - "Given request initiated by client activity, when request met given conditions, then inspect server state."
    This is a required question

    #5

    Warp .execute(ClientAction) .filter(Filter) .inspect(ServerInspection); - https://gist.github.com/4135360 - "Execute given client action and filter request in order to inspect server state"
    This is a required question
    This is a required question