Rename product from agent-framework to automaton; move scripts to scripts/ folder

This commit is contained in:
2026-06-12 13:22:10 -04:00
parent 502f47eb21
commit a1391e7364
8 changed files with 16 additions and 16 deletions
+4 -4
View File
@@ -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