Velnor is a drop-in replacement for the GitHub Actions runner, built in Rust and specialized for Rust projects.
GitHub still parses your .github/workflows/*.yml, expands matrices and reusable
workflows, manages secrets, schedules jobs, and renders the Actions UI. Velnor
replaces only the runner side: it registers as a self-hosted runner (V2 JIT),
runs each assigned Linux job in a Docker container, and executes the known action
surface through native Rust adapters. Because it is self-hosted and controls
execution, it aims to be faster, cheaper, nicer, and more informative than
GitHub-hosted runners.
Phase 0 scope: run the existing Rust CI/CD workflows of jackin-project/jackin
and ChainArgos/java-monorepo unchanged, proving correctness against the public
fixture first. No Velnor-native workflow language, no YAML scheduler, no macOS
job execution.
All direction lives in docs/ — keep it current; everything else
defers to it.
- Mission — what Velnor optimizes for (fastest, Rust-first, nicer output, cheaper).
- Vision — product goal and Phase 0 scope.
- Roadmap — the plan: what must be implemented, target analysis, protocol decisions, verification order.
- UI comparison — Velnor vs GitHub-hosted runner output, with the GitHub-API extraction method.
- Runner usage — how to configure, run, and prove the runner locally and against the fixture.
- Docs index — everything else (adapter contract, automation policy, runbook, runner V2 reference).
Large, scoped work is driven by goal prompts in prompts/ — run
them with /goal (Claude Code or Codex), one per day, in the recommended
sequence. See prompts/README.md.
Contributor rules are in AGENTS.md.