| name | coordinator-cycle |
| description | Use when running multi-mission Kamino (or campaign) research via the deterministic coordinator — plan, delegate, cycle, journal. |
Coordinator Cycle (Layer 6)
Deterministic mission orchestration: one narrow template per cycle. Creative work stays in delegate_task; prioritization and debrief are Python coordinator only.
Cron role (v2.0.10): weekly nss-investigate-queue (Sun 05:00) — Kamino depth. Daily cross-platform hunt is bounty-loop, not this skill.
Prerequisites
cd /home/kt/projects/rtp/night-shift-security
git pull --ff-only
Initialize once per campaign:
.venv/bin/python -m night_shift_security.cli.main \
--config src/night_shift_security/config/kamino_shoestring.json \
coordinator init
Standard cycle
.venv/bin/python -m night_shift_security.cli.main \
--config src/night_shift_security/config/kamino_shoestring.json \
coordinator plan --top 1
.venv/bin/python -m night_shift_security.cli.main \
--config src/night_shift_security/config/kamino_shoestring.json \
--proposals data/security_results/hermes_proposals/latest.json \
coordinator cycle
.venv/bin/python -m night_shift_security.cli.main coordinator status
Trust boundary
- Coordinator is deterministic — never override gates, scoring, or evidence grades in agent logic.
delegate_task proposals remain metadata.trusted=false.
- One mission = one template. Retire after
coordinator cycle; do not reuse mission_id.
Gotchas
- Run
coordinator init before first plan/cycle — state lives at data/security_results/knowledge/coordinator_state.json.
coordinator plan after a cycle should surface a different template unless refinement (lineage_expansion) fired.
- Debrief JSON:
data/security_results/knowledge/debriefs/<mission_id>.json — use for Same vs different notebook entries.
- Full pipeline in
cycle can take minutes; cron should use plan + expansion + cycle as separate steps if needed.
- Read
data/security_results/day_shift/current.md Night Shift handoff before cron — skip targets Day Shift marked complete.