JevMade hello@JevMade.com
← Back to guides

JevMade field notes / Research architecture guide

Organizing choices and memory for an AI assistant

This guide explains a proposed way to help an AI assistant handle complex tasks. It suggests organizing large lists of choices into smaller pages and sorting saved information by how important it is for the current step.

Original by 6Mikao9Agent workflows

Listen to this guide

JevMade’s plain-English explanation

0:00 /

AI narration

Credits

“Decision-Native Agent Runtime” by 6Mikao9. 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

The author shares a plan to help an AI assistant find useful information without getting overwhelmed. It focuses on Jev, an AI tool that chooses from options rather than writing an answer. This design explores how to manage large amounts of data by breaking it into smaller pieces.

The proposed method groups long lists of choices into smaller pages so the software only looks at a few options at a time. It also suggests sorting the assistant's memory by importance and updating only the specific steps affected when a task changes.

This project is useful for researchers exploring new ways to build AI tools, but it is mostly an unfinished plan. Many features are not built yet. The saved tests used a simple substitute instead of the actual Jev tool to process the text.

Key takeaways

  1. Group large lists of choices into smaller pages so the AI assistant is not overwhelmed.
  2. The author proposes sorting saved information by importance and only updating steps affected by a change.
  3. Different backup plans are suggested for missing choices, confusing options, and missing information.

Many proposed features, like unified scheduling and long evaluations, remain unbuilt. The saved dialogue and speed tests used a simple local substitute instead of the actual Jev tool.

Repository README and linked design documents · Source reviewed

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