diff --git a/README.md b/README.md
index 12144e0..35b08b9 100644
--- a/README.md
+++ b/README.md
@@ -12,13 +12,39 @@
 - [x] make the impl more robust; do more SWE
 - [x] add no self-deadlock experiments
     - I envision this would be: providing an eventually-style LTL query, sending messages onto an open channel, and asserting that the gadget doesn't somehow deadlock with itself
+- [ ] support queries over multiple properties
 - [ ] add raft, TCP, SCTP, ABP experiments from old Korg impl to the test suite
 - [ ] add labels on trace logging to gadgets
 - [ ] modify the paper? spin workshop?
 
 # Notes
 - Sound and complete attack discovery for replay, dropping, and reordering attacks on channels
-    - possible because of the finite-state modeling spin does
+    - possible because of the finite-state modeling spin does. Indeed, we can model no-limit attackers within the finite-state model, giving guarantees of decidability and complexity. 
 - Limiting the number of messages a drop/replay/reorder attacker can reason about has the ability to significantly reduce the searchspace, especially when dealing with larger models. Although KORG is always decidable, sound, and complete, using the unbounded attacker is inadvisable in practice because spin must reason about *all* such permutations of possible drop, replay, and reorder sequences, thereby increasing the search space factorially.
 - One explicit limitation of the replay attacker is not being able to transition back to listening for packets after replaying
 - Maybe change the title to: Korg: Automated analysis of channel faults
+- The inclusion of the pass on chan functionality is required to ensure liveness properties are not trivially violated by an attacker gadget that loops with itself. Thus the pass on chan functionality is the best possible "wait" we could think up. We also include no deadlock tests. 
+
+# Gadget Structures
+
+Drop:
+- drop msg off chan
+- pass on chan
+
+Replay:
+:CONSUME:
+- consume msg; may go to CONSUME or REPLAY
+- pass on chan
+:REPLAY:
+- replay msg
+- pass on chan
+- pass on chan, then go to REPLAY
+
+Reorder:
+:INIT:
+- pass msg on chan
+- go to CONSUME
+:CONSUME:
+- consume n messages on chan, then go to REPLAY
+:REPLAY:
+- replay msg
diff --git a/src/__pycache__/model_generate.cpython-313.pyc b/src/__pycache__/model_generate.cpython-313.pyc
index fd345df..58b0958 100644
Binary files a/src/__pycache__/model_generate.cpython-313.pyc and b/src/__pycache__/model_generate.cpython-313.pyc differ
diff --git a/src/model_generate.py b/src/model_generate.py
index 0db573e..4729af0 100644
--- a/src/model_generate.py
+++ b/src/model_generate.py
@@ -443,7 +443,7 @@ def gen_drop(chan : str, chan_type : List[str], mem : int, index : int) -> str:
     ret_string+="       goto MAIN;\n"
     ret_string+="    fi\n"
     ret_string+="    }\n"
-    ret_string+="  :: "+str(chan)+" ? ["+str(fs)+"] -> atomic {\n"
+    ret_string+="  :: "+str(chan)+" ? ["+str(fs)+"] -> {\n"
     ret_string+="    b = len("+str(chan)+");\n"
     ret_string+="    do\n"
     ret_string+="    :: b != len("+str(chan)+") -> goto MAIN;\n"
@@ -484,7 +484,7 @@ def gen_drop_unbounded(chan : str, chan_type : List[str], index : int) -> str:
     ret_string+="       goto MAIN;\n"
     ret_string+="    od\n"
     ret_string+="    }\n"
-    ret_string+="  :: "+str(chan)+" ? ["+str(fs)+"] -> atomic {\n"
+    ret_string+="  :: "+str(chan)+" ? ["+str(fs)+"] -> {\n"
     ret_string+="    b = len("+str(chan)+");\n"
     ret_string+="    do\n"
     ret_string+="    :: b != len("+str(chan)+") -> goto MAIN;\n"
diff --git a/tests/tests.yaml b/tests/tests.yaml
index f9f1255..190f9ee 100644
--- a/tests/tests.yaml
+++ b/tests/tests.yaml
@@ -1,3 +1,13 @@
+unidirectional-drop-abp: 
+  - command: python src/main.py --model=tests/abp/abp.pml --attacker=drop --chan=AtoB --output=temp.pml --eval --cleanup --mem=1
+  - intended: no violation
+  - explanation: abp resists drop, see https://en.wikipedia.org/wiki/Alternating_bit_protocol
+
+bidirectional-drop-abp: 
+  - command: python src/main.py --model=tests/abp/abp.pml --attacker=drop --chan=AtoB,BtoA --output=temp.pml --eval --cleanup --mem=1
+  - intended: no violation
+  - explanation: abp resists drop, see https://en.wikipedia.org/wiki/Alternating_bit_protocol
+
 drop-nodeadlock: 
   - command: python src/main.py --model=tests/no-deadlocks/t1-deadlock.pml --attacker=drop --chan=c --output=temp.pml --eval --cleanup --mem=2
   - intended: no violation