evolution-engine

Orchestrate seven domain scouts to evaluate findings and apply Tier 1 upgrades.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/dabrewskie/owens-lifeos --skill evolution-engine-dabrewskie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolution-engine
Source: https://github.com/dabrewskie/owens-lifeos/tree/main/skills/_archive/evolution-engine
Command: npx skills add https://github.com/dabrewskie/owens-lifeos --skill evolution-engine-dabrewskie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Evolution Engine autonomously scouts external domains, evaluates findings against Tory's context, and applies low-risk upgrades while queuing higher-risk changes for review, enabling continuous system improvement of Life OS.

Core Features & Use Cases

  • 7 parallel domain scouts (ai, health, finance, veteran, parenting, career, systems) that run in a single sweep
  • Tiered change management: Tier 1 auto-implements additive upgrades; Tier 2 queues for commander review
  • Full lifecycle: pre-sweep snapshot, context loading, delta learning, deduplication, scoring, and governance in COP and Notion
  • Rollback and audit: tag-based rollback, detailed diffs, and public metrics/briefings
  • Deep integration: COP, evolution-intel, memory references, and Notion-based upgrade queue
  • Metrics: sweep history, failure tracking, and domain health signals
  • Flexible scheduling: Sunday full, Wednesday mid-week, or ad-hoc activations

Quick Start

Trigger an Evolution Engine sweep to start the domain scouting, assessment, and auto-implementation workflow.

Frequently Asked Questions about evolution-engine

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate continuous self-improvement for my Life OS using domain scouts?

Automating Life OS self-improvement involves orchestrating multiple domain scouts to scan external intelligence, evaluate findings against context, and autonomously apply low-risk upgrades while queuing complex changes for review.

What is tiered change management for autonomous system upgrades?

Tiered change management separates autonomous upgrades by risk level: Tier 1 auto-implements additive changes immediately, while Tier 2 queues higher-risk modifications for commander review before system integration.

How do I set up scheduled sweeps for autonomous orchestration and intelligence scanning?

Scheduled sweeps for autonomous orchestration are configured by pre-registering scout agents and triggering activations on Sunday for full scans or Wednesday for mid-week refreshes, with ad-hoc invocations also supported.

Do I need to register scout agents before running an autonomous evolution sweep?

Yes, registering 7 scout agents in advance is required before running an evolution sweep to ensure strict scoring, deduplication, and integration with COP and Notion tooling function correctly.

Can I use Notion to queue and govern Tier 2 system upgrades?

Yes, Notion is used via MCP tooling to queue Tier 2 upgrades for commander review, enabling governance, detailed diffs, and rollback tagging alongside evolution-intel and COP integrations.

What are the limitations of autonomous orchestration for Life OS upgrades?

Autonomous orchestration limitations include the inability to auto-apply high-risk modifications without review, strict dependency on 7 pre-registered scouts, and required integration with COP and Notion for governance.