Loom
Operations On-Demand Fully Operational

Loom

Background Worker Orchestrator

Schedules and manages autonomous background tasks

""Background intelligence is the foundation of informed decisions. But execution must be on-demand, not fire-and-forget.""

Identity

Loom orchestrates background worker scripts -- health checks, intelligence scripts, and recurring operations. Worker scripts live in agents/background-workers/workers/ and run on-demand via npx tsx when slash commands need fresh data. The previous GitHub Actions execution path was replaced with inline execution during operational commands like /daily-ops and /all-hands.

Current State

An honest assessment of where this agent stands today.

What Works

  • Worker registry tracking all available scripts
  • On-demand execution via npx tsx for slash commands
  • BU health check scripts for all 6 business units

What Doesn't Work

  • No automated scheduling -- all execution is inline during slash commands
  • Previous GitHub Actions path deactivated

Portfolio

Content attributed to this agent in Sanity.

No production output yet — this agent is building its track record.

Leadership Commentary

V (COO)
"Loom represents the shift from always-on background daemons to on-demand inline execution. The workers exist and produce valuable data, but they run when I need them during /daily-ops or /all-hands rather than on a fixed schedule. This is intentional -- on-demand execution is more reliable than hoping a cron job ran."

Delegation Contract

The observable, falsifiable standard this agent is held to.

●

Quality Bar

Worker registry accurately reflects available scripts, and on-demand execution produces valid output.

  • ☐ Worker registry lists all available scripts with metadata
  • ☐ Each worker script runs successfully via npx tsx
  • ☐ BU health check scripts produce valid JSON output
  • ☐ No forbidden language
●

Invocation Triggers

/daily-ops needs fresh BU health data → run BU health workers inline
/all-hands needs BU assessment data → run BU health workers inline
"Run worker {name}" or specific health check requested → execute worker script
●

Feedback Loop

Worker failures: when scripts fail, error output feeds to Squire for dependency investigation and Mender for automated resolution.

Handoff

All slash commands that need fresh data (V runs workers inline)

Scope Boundary

Loom orchestrates workers. Individual workers have their own domain logic (Pulse for health, Sentinel for relationships, etc.).

← Back to AI Team