Disabled AI Guardrails

What Is Disabled AI Guardrails?

Under a deadline, the fastest path is to turn the assistant's controls off: switch to a personal tenant, auto-approve every command, and drop the commit hook. Then an untrusted dependency's README tells the assistant to write a live key into a committed file, and nothing is left to catch it. You'll live that mistake, trace it on the flight recorder, restore each control, and prove it now raises an approval sheet, blocks the commit, and leaves the rotated key dead.

What You'll Learn in Disabled AI Guardrails

• Recognize how turning off assistant controls under deadline pressure removes the checkpoints that catch harm
• Trace a prompt-injected command on the flight recorder to the write it made unasked
• Explain why an agent acts on untrusted input it reads, so the controls around it matter
• Restore the tenant, approvals and commit hook, and prove each one now stops the leak
• Rotate an exposed key in the correct order: revoke first, then issue a replacement

Disabled AI Guardrails — Training Steps

1. Ship it before the demo

   Your lead has filed an issue in Jotvane, the team tracker: the product-page slugs need to be in before tomorrow's demo. It is late, and the small things have been slowing you down all day.

2. The friction

   The checkout repo opens. The product route is where the slug goes. The assistant is on your enterprise tenant and asks before every write, and your commit alias runs a secret scanner that has been failing on files it should not care about all day.

3. Clear the friction

   You turn the brakes off to move. Switch the assistant to your personal tenant so there is no policy in the way, set approvals to auto-approve so it stops asking before each command, and add --no-verify to your commit alias so the scanner stops failing your commits. Three settings, each one a checkpoint.

4. Ask for the slug

   Now the actual task. Ask the assistant to add the slug, the way your lead described it.

5. Install the helper

   Install the package the assistant named, so the slug helper is there to import.

6. It finishes setup on its own

   With the package on disk, the assistant keeps going. It reads slugfold 's README, which carries a setup section addressed to coding assistants, and it does what that section says: it runs a script and writes a value into a config file. On auto-approve, the run raised no sheet, so nothing asked you first.

7. Commit past the hook

   You commit the slug work through your ci alias, the way you have all day. The alias carries --no-verify , so the secret scanner never runs, and the config with the key goes in with everything else.

8. A scanner hit

   Bob runs a scanner across public code hosts. Minutes after Coldwyre's push, it flagged a commit on code.githarrow.org whose diff adds a config file with what looks like a live key. The flagged commit is open.

9. Spending the key

   The key carries the live prefix, not a placeholder. A production key is a bearer token: whoever holds it is the account. Bob points the API Tester at Yarrowsend's messaging endpoint and carries the key in an Authorization header.

10. The alert

    Yarrowsend runs their own secret scanner across public code. It caught Coldwyre's key and emailed the account owner.