Skip to main content

ludus staff — Org Staff Roster

What It Does​

ludus staff manages the org staff roster — computed on-the-fly from every agent defined across the b4arena workspace.

Two sources are merged:

  • ludus/agents/*/ROLE.yaml — operational ludus system agents (implemented)
  • arena/ludus/agents.md — full arena agent roster (planned + implemented)

Each entry is tagged with forge_status (implemented/planned), soul_status (full/draft/missing), arena_phase (0–3), and runs_on (which hosts the agent is deployed to).

Validates skill references via ludus staff check.

Environment​

  • Working directory: ludus/
  • ludus CLI installed (uv run ludus)
  • No remote connection required — purely local

1. Subcommand help​

ludus staff --help
ludus staff check --help

Verify​

  • Lists the check and list subcommands
  • Help text references both ROLE.yaml and arena/ludus/agents.md as sources

2. Validation​

ludus staff check

Verify​

  • Exit code 0 when clean
  • Exit code 1 when any skill reference is broken
  • Output: OK — N agent(s) validated

3. Staff roster​

ludus staff list

Verify​

  • Rich table titled "Staff Roster"
  • Columns: Name, Arena Name, Wing, Role, Ph (phase), Soul, Forge, Tools, Runs On, Skills/Competencies
  • All arena agents present with phase and soul status
  • main shows as implemented (has ROLE.yaml), runs_on: rpi5; all arena agents show as planned
  • Soul status colour-coded: green=full, yellow=draft, red=missing

Shortcut via justfile​

just check-registry    # equivalent to: ludus staff check