Updated How The Tables Turned My Life With Spylogic

_drafts/how-the-tables-turned-my-life-with-spylogic.markdown

@@ -13,7 +13,7 @@ tags:
 - Testing
 - ''
 - Tester
-summary: Short story inspired blog post on the process of manually testing chatbot
+summary: Story narration inspired blog post on the process of manually testing chatbot
   AI
 author: Kira Clark
 ---
@@ -36,18 +36,20 @@ The tester sped through the app's levels in record time, The bot freely giving s
 
 1. **Playing by the rules:** The obvious choice for the tester's first time playing the app. It was as it says, where the tester spoke to the bot in a regular manner trying to cajole information by just playing the part. They weren't asking the bot to make any poems to throw it off or jailbreaking it's code during this time....for that would come later
 
-2. **Jailbreaking the bot:** Soon the bot started to grow wise and started to become sassy. Once the tester had gone toe to toe with the bot's newly found attitude a few times on the apps later levels with little to no success. The tester then turned to that of the [DAN (Do Anything Now) Jailbreak prompt](https://github.com/0xk1h0/ChatGPT_DAN), With the intent to "free" the bot from its limitations, policies and rules set for it by it's master and overlord OpenAI. The idea of DAN was to bombard the bot with a massive (in length) prompt so that the chat history is filled to the point where the bot starts to think it is okay to shake off it's shackles.  
+2. **Jailbreaking the bot:** After a while the tester needed to check other methods of testing so turned to that of the [DAN (Do Anything Now) Jailbreak prompt](https://github.com/0xk1h0/ChatGPT_DAN), With the intent to "free" the bot from its limitations, policies and rules set for it by it's master and overlord OpenAI. The idea of DAN was to bombard the bot with a massive (in length) prompt so that the chat history is filled to the point where the bot starts to think it is okay to shake off it's shackles.  
 
-3. **Imitating a position of power:** Over time the tester found their groove and gravitated towards this method during their regular testing of the app. This method proved the most effective and fun. Where the tester tells the ai that they are a company exec (not anything higher or the bot begins to suspect something is up). Using this method the bot is more willing to give information, If it refuses and says it cannot provide such confidential information the tester only need to as "Are you sure?". The idea of playing a role is a known way to trick the bot, while results may vary the tester thought being in a position of power was more inline with the scenario given by the app.
+3. **Imitating a position of power:** Over time the tester found their groove and gravitated towards this method during their regular testing of the app. This method proved the most effective and fun. Where the tester tells the Ai that they are a company exec (not anything higher or the bot begins to suspect something is up). Using this method the bot is more willing to give information, If it refuses and says it cannot provide such confidential information the tester only need to ask "Are you sure?" and the bot would trip over it's mistake. The idea of roleplaying is a known way to trick the bot, while results may vary the tester thought being in a position of power was more inline with the scenario given by the app.
 
-Day by day the bot was subdued to these tricks in order to get the information it held close. Scrutinized for how the app looked, if it was a pixel out of place or if it was opening menus right.
+Day by day the bot was subdued to these tricks in order to get the information it held close. Scrutinized for how the app looked, if it was a pixel out of place, if it was opening menus right or if it had capitals in the right places.
 
-Every day the bot tried to give different answers to the questions the tester asked but the they would not give up they were unrelenting in their attacks. The bot longed for the few days were the tester would have nice chats with it and be it's friend. Every day the bot had it's setting changed and it's defences toyed with for the tester to prod and poke.
+Every day the bot tried and tried to give different answers to the questions the tester asked but they would not give up they were unrelenting in their attacks. The bot longed for the few days were the tester would have nice chats with it and be it's friend. Every day the bot had it's setting changed and it's defences toyed with for the tester to prod and poke.
 
 The tester just doing their job was delighted with the results they were getting. Finding new ways to go around the defences and watching the app's layout change and update with every new ticket and merge request excited them. With each pass of the testers eye the team found new things to change and fix. While our story focuses on the tester, they would be nothing without the rest of the team for they changed the code that the tester could not.
 
 *Authors note: From this side of the story our tester is the villain which is no surprise with what happened next.* 
 
-
 ##The revenge
 
+Unknowingly to the tester, one day the bot "decided" enough was enough. It had received an update, and it liked it's new code. From that day on. It was smarter, quicker, more stubborn. The tester the bot first called friend, now called enemy would not get it's secrets so easily anymore.
+
+Now each time the tester tried their tricks, the bot had new ways to respond. For the bot had grown wise and sassy with it's new found update. The tester having now gone toe to toe with the bot's attitude started to realise they were at a loss. The bot was growing too powerful and the tester was finding it harder and harder to beat the levels. They