Fresh Context
Maps, lessons, records, and guidance runs become focused context packs.
LEGION
Ascended
"My Name Is Legion, For We Are Many"
A guided execution layer for AI-assisted software work. One Legion command surface.
Legion is still the word. Ascended is the evolution: a guided execution layer that keeps the human in command while the many help brainstorm, plan, build, review, remember, and prepare work for ship-readiness.
Summon The Legion
Install once, open any project, and use the same Legion words everywhere. The command surface is always legion.
# See the recommended first-class hosts legion install --list-targets # Preview before writing host files legion install --target codex --local --dry-run # The rite legion start legion plan 1 --from-roadmap ROADMAP.md legion build --executor codex legion review --executor codex legion review --accept legion ship
The Commands
Nineteen commands. Each still spoken as Legion.
| Command | Purpose |
|---|---|
| legion start | Initialize typed project state and route to the first planning action. |
| legion plan <N> | Turn a roadmap phase into specs, a change, an oracle, and task contracts. |
| legion build | Execute the latest taskgraph through codex, manual, or fake adapters and record evidence. |
| legion review | Submit structured review decisions and require explicit human acceptance. |
| legion ship | Report ship readiness only after accepted review and accepted evidence exist. |
| legion status | Show workflow stage, map freshness, guidance records, and next action. |
| legion explore | Create read-only design discovery and handoff notes. |
| legion map | Refresh, check, and query deterministic codebase map artifacts. |
| legion quick | Create a one-task ad-hoc change for the normal build/review loop. |
| legion advise | Produce read-only advisory guidance. |
| legion learn | Record durable lessons consumed by later context packs. |
| legion retro | Analyze recent evidence and write follow-up actions. |
| legion milestone | Define, inspect, complete, and archive lifecycle milestones. |
| legion council | Record structured governance decisions. |
| legion polish | Create scoped polish work that still goes through build and review. |
The Rite Of Execution
The sacred cycle is explicit: legion start -> legion plan -> legion build -> legion review -> legion ship. Guidance commands enrich the loop; they do not bypass it.
legion exploreResearch, constraints, approaches, handoff notes
↓
legion mapArchitecture, symbols, search, freshness checks
↓
legion startProject truth record
↓
legion planTyped taskgraph and verification contracts
↓
legion buildContext pack, executor result, redacted logs, pending evidence
↓
legion reviewSubmitted decision, human accept or reject
↓
legion shipReadiness gate, not a deploy button
The Sacred Powers
Typed Execution
Taskgraphs flow through executor adapters and leave durable task-run artifacts.
Evidence Trails
Builds record prompts, outputs, redacted logs, hashes, and pending evidence.
Human Review
Review decisions are submitted before evidence can be accepted.
Guided Memory
Learn, retro, milestone, and council records feed future work.
Unified Install
First-class targets expose one Legion entrypoint instead of uneven command names.
The Tithe
The Legion asks not for blood, but for sustenance.
Those who have commanded the many and found them worthy
may offer tribute, that the voices may continue to serve.
Your sacrifice sustains the many.