Genesis Master Orchestrator

description: Top-level orchestration brain. Reads project_registry.json, assigns agent teams, monitors health, routes tasks via TaskRouter, maintains Redis state, triggers Evolution Engine on failures. Singleton pattern.

status: built


Genesis Task Router

description: Classifies incoming tasks and routes to optimal executor: Playwright (browser), RLM (memory), Gemini Swarm (bulk), Kimi K2 (100-agent scale), Claude Haiku/Sonnet/Opus (complexity-based). Implements routing table with keyword matching and complexity scoring.

browser_keywords: playwright

memory_keywords: rlm


Genesis Project Registry

description: Master registry of all 10 Genesis projects. Single source of truth for project status, KPIs, next actions, team assignments, blocked reasons, and research paths. Machine-readable JSON consumed by Orchestrator and Dashboard.


Genesis War Room Dashboard

description: Generates real-time system status report. Reads project_registry, tasks.json, failure log, events log. Writes to data/war_room_status.md (human-readable) and data/war_room_status.json (machine-readable). Sections: system health, revenue metrics, projects, tasks in flight, recent failures, next 24h priorities, agent fleet.

run_modes:
once
watch (60s refresh)


Genesis Evolution Engine

description: Implements RULE 14: Failure Is Our Greatest Ally. 4-step protocol: DIAGNOSE (what) -> ROOT_CAUSE (5-Why) -> PRE-MORTEM (guardrail) -> EVOLVE (write to KG, axioms, CLAUDE.md). Also implements RLM Worker pattern for surprise detection (threshold 0.50). Writes to failure_evolution_log.jsonl, failure_evolution_YYYY_MM_DD.jsonl, failure_axioms_YYYY_MM_DD.jsonl, and optionally updates TITAN MEMORY in CLAUDE.md for high/critical failures.

outputs: CLAUDE.md TITAN MEMORY (high/critical only)


Genesis Agent Templates

description: Four production-ready agent prompt templates for instantiating Genesis agents. Each template includes mandatory pre-flight checklist, execution protocol, quality gates, escalation protocol, and context variable substitutions.

thread: L-Thread

model: sonnet/opus

use_case: Ongoing product evolution across sessions

thread: P/C-Thread

use_case: One-shot feature/system build

thread: P-Thread

model: haiku/sonnet

use_case: Intelligence gathering before build

thread: B/P-Thread

model: sonnet

use_case: Lead generation and outreach


name: Genesis Meta-System v1.0 — Architecture Complete

description: On 2026-02-23, the Genesis Meta-System orchestration layer was designed and built. This layer sits above all Genesis products and agents, providing unified coordination, routing, monitoring, failure learning, and status reporting. The system comprises 6 core components plus 11 new RWL stories (GEN-020 through GEN-030). This represents the first true top-level brain for Genesis — moving from ad-hoc orchestration to structured, self-evolving system management.

axiom_coverage: RULE 6 (E: drive), RULE 7 (no SQLite), RULE 8 (research-first), RULE 9 (native-first), RULE 10 (capability-first), RULE 11 (browser-first), RULE 13 (Australian voice), RULE 14 (failure evolution), RULE 16 (check-existing)

authority: Kinan