SEO / GEO Growth Loop
Weekly content growth cycles for search and AI-answer visibility, including plans, drafts, publishing, feedback, review, and memory.
- WeChat articles
- Xiaohongshu notes
- SEO and GEO content
Open-source control plane / AI feedback loops
Centaur Loop turns agent work into a full operating cycle: plan, approve, execute, review, publish, collect feedback, reflect, remember, and improve the next run.
Goal, memories, tool registry, business context, and previous suggestions become structured tasks.
Plans, drafts, publishing, feedback, and memory candidates become first-class checkpoints.
Drafts are generated through adapter-ready tools without losing the loop state.
Feedback is reviewed into lessons, corrections, preferences, and next-cycle suggestions.
What's different
Centaur Loop models the whole business iteration around agent work, not just the task execution step.
AI runs where it can, then stops at checkpoints where people own taste, compliance, publishing, and final judgment.
Real outcomes, screenshots, notes, and metrics are reviewed into memory candidates that improve the next cycle.
Lifecycle
Most agent systems end when the answer is generated. Centaur Loop keeps the operational surface open until the work is reviewed, measured, and turned into next-cycle guidance.
Generate a structured plan and task list from goals and memory.
Pause for owner confirmation or edits before work begins.
Create drafts through registered AI tool definitions.
Approve, reject, or request changes per draft.
Keep manual publishing visible as a governed checkpoint.
Capture metrics, notes, screenshots, and outcome signals.
Analyze what worked, what failed, and why.
Ask humans which lessons deserve long-term memory.
Carry suggestions forward into the next run.
The loop starts again with reviewed experience.
Architecture
The current prototype is a working React workbench plus TypeScript loop runtime. It is early, but the core contracts are already visible: cycle state, human checkpoints, feedback, reviews, memory candidates, and adapter boundaries.
Explicit state machine that advances cycles and stops at human gates.
Turns goals, memory, business context, and tools into a structured plan.
Generates reviewable drafts and keeps failures inside the cycle record.
Converts feedback into retrospectives, lessons, and next-cycle suggestions.
Maps runtime state to chat messages, cards, and user actions.
OpenAI-compatible model access, tool registry, and memory boundaries.
Starter loops
Weekly content growth cycles for search and AI-answer visibility, including plans, drafts, publishing, feedback, review, and memory.
Daily topic and script cycles with feedback-driven improvement and a path toward fast-loop / slow-loop orchestration.
Designed to wrap existing execution systems instead of replacing them, with examples planned for common workflow and agent runtimes.
Positioning
| Layer | What it handles | What Centaur Loop adds |
|---|---|---|
| Cron / schedules | Wake a job at a time | Govern the full cycle before and after the job runs. |
| Workflow engines | Move tasks through steps | Make review, feedback, and memory part of the product surface. |
| Agent frameworks | Plan and execute with models/tools | Add human gates, business outcomes, and next-cycle improvement. |
| Publishing bots | Push generated output somewhere | Keep publishing accountable and learn from real-world response. |
Open source / MIT license
Run the workbench locally, inspect the state machine, and help shape the core package, adapters, storage, notifications, and memory layer.