lev

name	lev
description	[WHAT] CLI and SDK reference surface for Lev primitives. [HOW] Maps natural language aliases to stable primitives: get/work/ask/check/go. [WHEN] Use when you need command syntax, alias mapping, protocol routing, or SDK usage. [WHY] Keeps CLI usage stable while lifecycle/process logic lives in `work`. Triggers: "lev", "leviathan", "get", "search", "find", "lookup", "read", "ls", "research", "think", "spec", "plan", "execute", "analyze", "design", "validate", "align", "lifecycle", "work", "check", "scan", "security", "daemon", "daemons", "ask", "wiz", "wizard", "go", "handoff", "exit", "learn", "workflow", "skill"
skill_type	how-to
category	cli
primitive_owner	lev
lifecycle_owner	work
lifecycle_integration	{"router":true,"lifecycle_owner":"work","mode":"delegate","delegation":{"ephemeral":["work"],"captured":["work"],"classified":["work"],"crystallizing":["work"],"crystallized":["work"],"manifesting":["work"],"completed":["work"],"discarded":["work"]}}
protocol_handlers	{"core":["lev://get?query={q}&depth={d}&scope={s}","lev://find?query={q}&scope={s}","lev://exec?task={t}&epic={e}","lev://lifecycle?from={f}&to={t}","lev://research?depth={d}&topic={t}","lev://align?check={c}"],"plugins":["workshop://intake/{platform}","timetravel://pattern/{name}"],"skill":["skill://{skill-name}?{params}"],"flowmind":["flowmind://entity-lifecycle?state={s}"]}
plankton	true
constitutional	true
reference_protocol	flowmind://lev-core-protocol
action_directives	{"handoffs":"Load lev to resume: lev://lifecycle?from=handoff","proposals":"Convert to spec: lev://lifecycle?from=crystallizing&to=crystallized","specs":"Execute: lev://exec?epic={bd_epic_id}","reports":"Design solution: lev://lifecycle?from=captured&to=crystallizing"}
sub_skills	["lev-find","lev-research","lev-index","lev-cdo","lev-ultra","lev-align","lev-test","lev-lifecycle","work","lev-learn","lev-builder","lev-workshop","lev-clwd","lev-intake","lev-ux","lev-examples","skill-builder","lev-computer-use"]

Lev: Plankton Router

IMPORTANT: This skill is "plankton" - always referenced in handoffs, proposals, specs, and compact summaries. Every mention should be action-oriented.

---

Lev Concept

What is lev? Lev is the master router and entry point for the entire Leviathan ecosystem. It's a "plankton" skill - small, foundational, referenced everywhere, and essential to the lifecycle.

Why plankton? Like plankton in an ocean ecosystem:

• Foundational: Everything feeds from it
• Distributed: Referenced in every lifecycle artifact
• Action-oriented: Always includes next actions
• Constitutional: Defines core protocols

When to use:

• ANY work request (get, think, spec, execute)
• Entity lifecycle transitions
• Protocol handler lookups
• Skill discovery

Plankton behavior: Every lifecycle artifact (report, proposal, spec, handoff) should reference lev with action directives:

• "Load lev to advance this work"
• "Use lev://lifecycle to transition states"
• "Execute via lev://exec"

---

CLI Commands

Primary: lev (entry point)

# Auto-routes based on keywords
lev get "auth middleware patterns"
lev "research authentication patterns"
lev "design user management system"
lev "spec implementation behavior for feature X"
lev "execute epic clawd-h2qg"

Core Primitive: lev get

lev get is the root external-context primitive. It progressively expands retrieval depth:

Compatibility note: if your local CLI does not yet expose lev get, use lev find as the temporary alias.

# Depth 0: current conversation/session context only
lev get "auth"

# Depth 1: include filesystem and local project artifacts
lev get "auth" --depth=fs

# Depth 2: include BD/tasks state
lev get "auth" --depth=bd


lev get  --depth=research