JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Research writeup

How to separate an AI assistant's choices from its writing

This guide explains how to build safer AI assistants by splitting their work. It shows how to separate writing text, making quick choices, and carrying out actual commands into different software parts.

Original by daryl / Jev TutorialAgent workflows

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits

“Separating Agent decisions from LLM generation in system design” by daryl / Jev Tutorial. Read the original source.

This expanded guide is an AI-narrated adaptation prepared by JevMade. It expands the source’s essential ideas, examples and caveats in JevMade’s own words and is not a word-for-word reading. The synthetic voice does not imitate the author or imply their endorsement.

Our summary

This guide shows how to organize an AI assistant so it does not control everything at once. Builders can separate the software that writes text from the software that takes action. This prevents the assistant from quietly doing things it should not do.

The method uses standard AI software for complex writing and planning. For quick choices, it uses a tool called Jev. Jev chooses from set options instead of writing answers. Finally, normal computer code carries out the actual actions, like deleting files or changing permissions.

This setup helps software builders manage how an AI assistant handles its memory and past messages. However, the fast decision tool should never handle permanent or risky actions alone. High-risk choices always need a person or a stronger AI program to check them first.

Key takeaways

  1. Use a fast decision tool only when the possible choices are already known.
  2. Keep actual actions and permissions in normal computer code, not in the AI software.
  3. Always send risky or uncertain choices to a person or a more powerful AI program.

This page adapts advice from a Tencent Technology Engineering article. It offers suggestions for organizing software rather than tested proof that this exact method works better.

Article · Source reviewed · Original published

Read the original guide Opens the author’s site in a new tab.