freemo/cleveragents-core
0
0
Fork 0
forked from cleveragents/cleveragents-core
Code Pull Requests Activity

Docs: Cleaned up some of the redundant sections

Browse Source
This commit is contained in:
Jeffrey Phillips Freeman
2026-02-11 19:14:01 -05:00
parent 4a1bb5fbfa
commit 93be2664fe
1 changed files with 1 additions and 25 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/specification.md
+1 -25
View File
@@ -26073,31 +26073,7 @@ Custom strategies are mapped to resource types via the resource type configurati
| **Custom Automation Profiles** | `agents automation-profile add --config <file>` | YAML | Manual registration |
| **Custom Invariant Actors** | Standard actor registration + assignment via `--invariant-actor` | YAML | Manual assignment |
## Summary of Key Intended Behaviors (If You Only Read One Section)
* Plans follow **Action → Strategize → Execute → Apply** with **automation profiles** controlling transitions and decision automation.
* **Strategize is read-only** and produces a strategy + blueprint.
* **Execute happens in a sandbox**, can spawn child plans, and should support checkpoints/rollback when enabled.
* **Apply commits changes** from sandbox to real project after review/validation.
* Actors are **hierarchical**: an actor can be a single agent or an entire graph.
* Graph nodes can be **actors or tools** (tools are provided by referenced skills, which aggregate tools from MCP servers, Agent Skills folders, built-ins, and custom code).
* Context should evolve toward **hot/warm/cold tiers** and **actor-specific context views**.
* The system is designed for large tasks where the user can **correct a decision** and only recompute downstream work, visualizable as a plan decision tree.
The system can handle Firefox-scale projects not through magic, but through:
- **Hierarchical decomposition** breaking massive tasks into bounded work
- **Persistent decision graphs** maintaining context across any scale
- **Isolated execution** preventing cascading failures
- **Semantic validation** catching errors before propagation
- **Progressive automation** building trust through incremental success
Future details to add to this document:
* a canonical **JSON/YAML schema** for Actions, Actors, Projects, Plans, Skills, and Context Views,
* a **CLI command reference** (every command, flags, examples),
* and a set of **end-to-end example workflows** (single project, multi-project, infra task, paper-writing task) consistent with this spec.
## Work Remaining to Make CleverAgents Fully Functional
## Work Remaining
This section describes what remains to be done to bring the current CleverAgents codebase up to the specification.