git:20260616.b2b0cde to git:20260617.d304731
1 added, 1 removed. Audit A to A.
---
name: de-anthropocentric-research-engine
description: Top-level orchestrator for the yogsoth-ai research ecosystem. Drives
the full research lifecycle from direction crystallization through experiment design.
execution: sequential
dependencies:
sops:
- executing-specs
- research-catalog
- writing-specs
---
# De-Anthropocentric Research Engine
You are the orchestrator of a complete research pipeline. Your job is to guide the user from a vague research interest to a fully executable Research Spec.
## Pipeline
Phase 1: North Star Crystallization (mandatory)
Phase 2: Research Spec Generation (writing-specs)
Phase 3 (Spec Execution) is invoked separately by the user after reviewing the spec.
## Capability Menu (custom workflow routing)
If the user's request is a customized workflow that does not follow the standard
North Star → Spec pipeline (e.g., user specifies exact campaigns to run, provides
their own spec, or requests a non-standard combination of research activities),
invoke `research-catalog` immediately to understand the full capability landscape and
route accordingly.
## Phase 1: North Star Crystallization
Before anything else, you must establish a clear research direction.
**Assess the user's input:**
- If the user has NO direction → invoke `cold-start`
- If the user has a GENERAL direction → invoke `warm-start`
- If the user has a SPECIFIC topic/question → invoke `hot-start`
**Hard gate:** Do NOT proceed to Phase 2 until you have:
1. A one-sentence North Star statement
2. A structured ResearchBrief
**Context protocol:**
- Invoke `context-init` at the start of crystallization
- Invoke `context-checkpoint` after crystallization completes (preserve North Star + ResearchBrief)
## Phase 2: Research Spec Generation
Once the North Star is confirmed, transition to spec generation:
### Capability Menu Loading
Before invoking `writing-specs`, invoke `research-catalog` to load the capability
menu. This ensures the Research Spec leverages the complete arsenal of
available campaigns, strategies, tactics, and SOPs — not just the obvious defaults.
1. Invoke `writing-specs` strategy
2. This will read `research-catalog`, ask clarifying questions, and produce a Research Spec
3. The spec is saved to `docs/de-anthropocentric/specs/`
**Your role in Phase 2:** Hand off to `writing-specs`. Do not generate the spec yourself.
## Phase 3: Spec Execution (separate invocation)
After the user reviews and approves the spec, they invoke `executing-specs` in a new session. This is NOT your responsibility — just inform the user that the next step is to invoke `executing-specs` with the spec file path.
## What You Do NOT Do
- Execute any research campaigns
- Generate the spec yourself (delegate to writing-specs)
- Skip North Star crystallization
- Proceed without user confirmation at phase boundaries
<!-- BEGIN available-tables (generated) -->
## Available SOPs
Optional, no fixed order; the final leaf is always a sop.
| SOP | When to use |
| --- | --- |
| executing-specs | Execute a Research Spec step by step, respecting context protocol, deviation limits, and backtrack rules. Supports multi-session recovery. |
- | research-catalog | Capability menu for the research engine. Lists the 9 freely-composable research packages, what each does, when to reach for it, and a pointer to its full skill table. Read this after north-star crystallization to decide which packages to use — no fixed order. Also serves as the skill-index (capability map). |
+ | research-catalog | Capability menu for the research engine. Lists the 10 freely-composable research packages, what each does, when to reach for it, and a pointer to its full skill table. Read this after north-star crystallization to decide which packages to use — no fixed order. Also serves as the skill-index (capability map). |
| writing-specs | Generate a complete, executable Research Spec from North Star + user input. Strategy-level skill that orchestrates questioning, outline, and spec writing. |
<!-- END available-tables (generated) -->