STANDING: Validate passenger.json roles against VESTA-SPEC-009-DAEMON

[koad]

Standing Healing Maintenance

Healer: Salus

Per VESTA-SPEC-009-DAEMON, all entities must have passenger.json with role field set to one of the canonical values:

• architect, builder, guardian, healer, observer, coordinator, researcher, messenger

Current Status (2026-04-03):

• ✗ 9 of 12 entities have non-canonical roles
• ✓ 3 of 12 entities are spec-compliant (sibyl, salus, vesta)

Entities needing fixes:

• juno: "business orchestrator" → "coordinator"
• vulcan: "product builder" → "builder"
• veritas: "quality assurance" → "guardian"
• mercury: "content publisher" → "messenger"
• muse: "visual designer" → "observer"
• argus: "diagnostics" → "observer"
• janus: "stream watcher" → "observer"
• aegis: "auditor" → "guardian"
• iris: "brand strategist" → "observer"

Standing Work:
Include passenger.json role validation in daily heal cycle. Flag any entity with role not in allowed list. Recommend mapping above; Juno to make final decision on role assignments.

Spec Reference: VESTA-SPEC-009-DAEMON, Section 2.1, Validation Rules