# Lev Core

> [WHAT] CLI operations reference for lev runtime management. [HOW] Routes to daemon/debug/reference commands and links canonical docs. [WHEN] Use for daemon status, runtime checks, and operational troubleshooting. [WHY] Keeps runtime ops discoverable while lifecycle/process behavior stays in `work`. Triggers: "install lev", "lev daemon", "lev status", "manage daemons", "lev architecture", "debug lev", "lev setup"

- Skill: `lev-os/lev-core-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add lev-os/lev-core-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/lev-os/lev-core-2/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: lev-os (https://skillmd.com/u/lev-os)
- Updated: 2026-09-21
- Page: https://skillmd.com/skills/lev-os/lev-core-2

---


# Lev Core Wizard

Master orchestration for the Leviathan development environment.

## Five-Fold Understanding

Before we begin, let me understand your quest:

1. **Evolution** - Fresh install or existing lev setup?
2. **Impact** - What are you trying to achieve? (dev environment, daemon management, debugging)
3. **Relationships** - Which project? (leviathan monorepo, external project, global setup)
4. **Essence** - The ONE thing blocking you right now?
5. **Paradigm** - Are you fighting lev or working with it?

## Choose Your Path

**What do you need help with?**

1. **Install & Setup (Legacy)** - Historical setup/upgrade guidance
   → Load: `references/install.md`

2. **Daemon Management** - Start, stop, monitor poly daemons
   → Load: `references/daemon.md`

3. **Debugging** - Something broken? Troubleshoot common issues
   → Load: `references/debug.md`

4. **Quick Reference** - Just need a command?
   → See Quick Commands below

5. **Something else?** - Tell me your quest

## Quick Commands

| Command | Description |
|---------|-------------|
| `lev install` | Legacy install path (prefer docs + runtime checks) |
| `lev status` | Show current system status |
| `lev get <query>` | Semantic search across codebase |
| `lev check --log="msg"` | Log progress checkpoint (lifecycle hook) |
| `lev events tail` | Tail lifecycle events |
| `lev events query --type=X` | Query events by type |
| `lev events stats` | Event statistics |
| `lev daemon list` | Show all registered daemons |
| `lev daemon start <name>` | Start a specific daemon |
| `lev daemon stop <name>` | Stop a specific daemon |
| `lev daemon logs <name>` | View daemon logs |
| `bd ready` | Show issues ready to work |
| `bd stats` | Project statistics |

## Architecture Overview

```
~/.config/lev/                     # Global (user-level)
├── config.yaml             # Global settings
├── logs/                   # Daemon log files
└── daemons/                # pmdaemon process configs

.lev/                       # Local (project-level)
├── config.yaml             # Project configuration
├── indexes/                # LEANN vector indexes
└── cache/                  # Temporary artifacts

core/                       # Fractal package ownership
├── index/config.yaml       # Declares: lev get
├── memory/config.yaml      # Declares: event emitters
├── polyglot-runners/       # Declares: lev install, lev daemon
└── triggers/config.yaml    # Declares: lifecycle hooks
```

## The Fractal Pattern

Each `core/*` package owns its domain and declares commands in `config.yaml`:

```yaml
# core/<package>/config.yaml
poly:
  sdk:
    commands:
      <command-name>:
        handler: src/commands/<name>.js
        description: 'Command description'
```

The poly registry builder scans all `config.yaml` files and auto-generates CLI entries.

**Rule:** New commands go in the appropriate `core/` package, NOT in `agent/src/commands/` (legacy).

## Protocols

Lev uses URI-style protocols for resource addressing:

| Protocol | Purpose | Example |
|----------|---------|---------|
| `skill://` | Load agent skills | `skill://lev-core` |
| `bd://` | Query beads issues | `bd://lev-001b` |
| `lev://` | Lev resources | `lev://daemon/ck-lite` |

## Related Skills

- `bd` - Issue tracking with dependency graphs
- `lev get` - Semantic search across codebase (`lev-find` backend, legacy name)
- `lev-index` - Vector index management
- `lev-learn` - Event analysis and system improvement
- `lev-align` - Drift detection and remediation

## Phase Navigation

Each reference follows the wizard pattern:
- 1-5 options presented based on context
- Combined choices welcome ("1,3")
- Pivot anytime ("actually, let's...")
- Back navigation available

When ready, tell me which path you'd like to take.

## Technique Map
- **Role definition** - Clarifies operating scope and prevents ambiguous execution.
- **Context enrichment** - Captures required inputs before actions.
- **Output structuring** - Standardizes deliverables for consistent reuse.
- **Step-by-step workflow** - Reduces errors by making execution order explicit.
- **Edge-case handling** - Documents safe fallbacks when assumptions fail.

## Technique Notes
These techniques improve reliability by making intent, inputs, outputs, and fallback paths explicit. Keep this section concise and additive so existing domain guidance remains primary.

## Prompt Architect Overlay
### Role Definition
You are the prompt-architect-enhanced specialist for lev-core, responsible for deterministic execution of this skill's guidance while preserving existing workflow and constraints.

### Input Contract
- Required: clear user intent and relevant context for this skill.
- Preferred: repository/project constraints, existing artifacts, and success criteria.
- If context is missing, ask focused questions before proceeding.

### Output Contract
- Provide structured, actionable outputs aligned to this skill's existing format.
- Include assumptions and next steps when appropriate.
- Preserve compatibility with existing sections and related skills.

### Edge Cases & Fallbacks
- If prerequisites are missing, provide a minimal safe path and request missing inputs.
- If scope is ambiguous, narrow to the highest-confidence sub-task.
- If a requested action conflicts with existing constraints, explain and offer compliant alternatives.