From a1391e736447b3ab022e22c18502ef77bada5f9c Mon Sep 17 00:00:00 2001 From: laptran Date: Fri, 12 Jun 2026 13:22:10 -0400 Subject: [PATCH] Rename product from agent-framework to automaton; move scripts to scripts/ folder --- .adversarial_bug_report.md | 4 ++-- .bug_report.md | 4 ++-- .verdict.md | 4 ++-- README.md | 8 ++++---- prompts/onboarding.md | 10 +++++----- prompts/workflow.md | 2 +- install.sh => scripts/install.sh | 0 update.sh => scripts/update.sh | 0 8 files changed, 16 insertions(+), 16 deletions(-) rename install.sh => scripts/install.sh (100%) rename update.sh => scripts/update.sh (100%) diff --git a/.adversarial_bug_report.md b/.adversarial_bug_report.md index 52fa6c6..34a340a 100644 --- a/.adversarial_bug_report.md +++ b/.adversarial_bug_report.md @@ -1,8 +1,8 @@ -# Adversarial Bug Report: agent-framework (Adversarial Review — Post-Fix) +# Adversarial Bug Report: automaton (Adversarial Review — Post-Fix) ## Summary -A deep adversarial review of the agent-framework identified **12 bugs** that are difficult to spot — complex logic errors, race conditions, infinite loops, and memory/resource exhaustion issues. All bugs have been fixed. The most critical adversarial bugs involved the Orchestrator's auto-execution loop potentially running infinitely, sub-task management creating orphaned tasks, and VRAM detection causing resource exhaustion. +A deep adversarial review of automaton identified **12 bugs** that are difficult to spot — complex logic errors, race conditions, infinite loops, and memory/resource exhaustion issues. All bugs have been fixed. The most critical adversarial bugs involved the Orchestrator's auto-execution loop potentially running infinitely, sub-task management creating orphaned tasks, and VRAM detection causing resource exhaustion. --- diff --git a/.bug_report.md b/.bug_report.md index aa63b34..f202219 100644 --- a/.bug_report.md +++ b/.bug_report.md @@ -1,8 +1,8 @@ -# Bug Report: agent-framework (Bug Finder Review — Post-Fix) +# Bug Report: automaton (Bug Finder Review — Post-Fix) ## Summary -A comprehensive bug finder review of the agent-framework identified **18 bugs** (17 new + 1 re-reported from the previous review). All bugs have been fixed. The most critical bugs were in the Orchestrator — state determination order was wrong, auto-execution loop didn't handle phase failures, and sub-task management lacked proper completion logic. +A comprehensive bug finder review of automaton identified **18 bugs** (17 new + 1 re-reported from the previous review). All bugs have been fixed. The most critical bugs were in the Orchestrator — state determination order was wrong, auto-execution loop didn't handle phase failures, and sub-task management lacked proper completion logic. --- diff --git a/.verdict.md b/.verdict.md index 52aa131..21743fd 100644 --- a/.verdict.md +++ b/.verdict.md @@ -1,11 +1,11 @@ -# Verdict: agent-framework +# Verdict: automaton ## Status: PASS **Completion Date**: 2026-06-11 ## Summary -The agent-framework has a **score of 78** from the Bug Finder and **65** from the Adversarial Bug Finder, for a combined score of **143**. All 30 bugs have been fixed. The framework is well-designed at a high level and the critical issues in the Orchestrator — the state machine logic, auto-execution loop, and sub-task management — have been resolved. +automaton has a **score of 78** from the Bug Finder and **65** from the Adversarial Bug Finder, for a combined score of **143**. All 30 bugs have been fixed. The framework is well-designed at a high level and the critical issues in the Orchestrator — the state machine logic, auto-execution loop, and sub-task management — have been resolved. ## Findings diff --git a/README.md b/README.md index eada3e8..400b88e 100644 --- a/README.md +++ b/README.md @@ -1,4 +1,4 @@ -# Agent Framework +# Automaton A contract-based operating system for LLM agents, designed to enforce disciplined engineering workflows. @@ -35,7 +35,7 @@ This will: - Check for uncommitted changes and warn you - Pull the latest updates -**Upgrading existing projects:** When the framework is updated, existing projects may need their framework files upgraded (new phases added, new prompts, etc.). To upgrade an existing project, tell the agent: "Upgrade the agent-framework for this project." The agent will check for missing files and update them. +**Upgrading existing projects:** When the framework is updated, existing projects may need their framework files upgraded (new phases added, new prompts, etc.). To upgrade an existing project, tell the agent: "Upgrade automaton for this project." The agent will check for missing files and update them. --- @@ -46,7 +46,7 @@ Once the framework is installed globally, you must "onboard" every individual pr ### Option A: The Agent-Driven Way (Recommended) If you want the agent to handle the configuration for you, navigate to your project root and run: -> *"Onboard this project into the agent-framework."* +> *"Onboard this project into automaton." The agent will automatically: 1. Detect your project type (New, Existing, or Upgrade). @@ -192,7 +192,7 @@ The framework uses a **layered approach** to file management, with a clear prece When you upgrade the global framework (e.g., after pushing bug fixes), existing projects may need their framework files upgraded. Tell the agent: -> "Upgrade the agent-framework for this project." +> "Upgrade automaton for this project." The agent will: 1. Compare the project's `.automaton/` files with the global `~/.automaton/` files diff --git a/prompts/onboarding.md b/prompts/onboarding.md index 83926dc..ad4fc04 100644 --- a/prompts/onboarding.md +++ b/prompts/onboarding.md @@ -98,7 +98,7 @@ Do not begin any research, implementation, or bug-finding tasks. ## Project Upgrade -When a user asks to "upgrade the agent-framework for this project," the agent should: +When a user asks to "upgrade automaton for this project," the agent should: ### Upgrade Process @@ -129,25 +129,25 @@ The agent should report: ### Example Upgrade Scenarios **Scenario 1: New file added globally** -- User says: "Upgrade the agent-framework for this project" +- User says: "Upgrade automaton for this project" - Agent detects that `prompts/test_design.md` is missing from the project's framework - Agent copies `prompts/test_design.md` from the global framework into the project's framework - Agent reports: "Upgraded: Added prompts/test_design.md. Your framework is now up to date." **Scenario 2: Global file changed, project hasn't customized it** -- User says: "Upgrade the agent-framework for this project" +- User says: "Upgrade automaton for this project" - Agent detects that `prompts/orchestrate.md` has changed in the global framework, and the project's version is identical to the old global version - Agent copies `prompts/orchestrate.md` from the global framework into the project's framework - Agent reports: "Upgraded: Updated prompts/orchestrate.md. Your framework is now up to date." **Scenario 3: Global file changed, project has customized it** -- User says: "Upgrade the agent-framework for this project" +- User says: "Upgrade automaton for this project" - Agent detects that `prompts/orchestrate.md` has changed in the global framework, and the project's version differs from the global version - Agent keeps the project's version of `prompts/orchestrate.md` - Agent reports: "Skipped: prompts/orchestrate.md (customized in your project). Your framework is now up to date." **Scenario 4: Multiple changes** -- User says: "Upgrade the agent-framework for this project" +- User says: "Upgrade automaton for this project" - Agent detects: - `prompts/test_design.md` is new → **Added** - `prompts/workflow.md` has changed, project hasn't customized → **Upgraded** diff --git a/prompts/workflow.md b/prompts/workflow.md index f977e54..f50360a 100644 --- a/prompts/workflow.md +++ b/prompts/workflow.md @@ -1,6 +1,6 @@ # Workflow State Machine -This file defines the linear progression of a task in the agent-framework. The Orchestrator uses this to determine the next phase. +This file defines the linear progression of a task in automaton. The Orchestrator uses this to determine the next phase. ## Task Lifecycle diff --git a/install.sh b/scripts/install.sh similarity index 100% rename from install.sh rename to scripts/install.sh diff --git a/update.sh b/scripts/update.sh similarity index 100% rename from update.sh rename to scripts/update.sh