Archon vs Prompt Language

# Archon Vs prompt-language

## Core distinction

Archon is orchestrator-first. prompt-language is runtime/language-first.

### Archon

- packaged AI workflow engine
- YAML workflows plus markdown prompt commands
- worktree isolation
- multiple execution surfaces
- operator-friendly product story
- stronger public adoption signal

### prompt-language

- control-flow and supervision DSL around coding agents
- explicit gates and termination criteria
- persistent state, variables, imports, memory
- `approve`, `review`, `spawn`, `await`
- better framed as a verification or supervision substrate

## Strategic conclusion

Do not chase Archon by turning prompt-language into a shallow workflow clone.

Instead:

1. own the stricter supervision layer
2. prove outcome improvements beyond gates
3. become a substrate that could sit under higher-level orchestrators

## Risk if ignored

The pack warns that prompt-language could drift into a crowded “AI workflow tool” bucket while giving up the strongest differentiator it currently has.

## Proposed positioning

> prompt-language is a verification-first supervision runtime for existing coding agents.

The review considers that sentence cleaner and more defensible than broader claims about becoming a universal software-construction medium before the evidence exists.