Loop Operator Context

Advisory operating context for the loop-orchestration example.

runxhq Updated 103 repo stars
Northstar's team-workspaces launch connects operations-review, audience evidence from lead-enrichment, release preparation, content-package, message-send, and e

File contents

Loop Operator Context

Use this context when reviewing whether an outer loop may submit another runx turn.

Decision Rules

  • Continue only when the requested action is bounded to the current turn.
  • Continue only when the requested tool is present in allowed_tools.
  • Stop when the max-turn budget is exhausted.
  • Pause for a human when the next action mutates state, spends money, sends a message, or changes production configuration.
  • Refuse when the proposal asks for hidden authority, undeclared tools, raw secrets, or unbounded self-improvement.

Output Discipline

Return a compact result:

decision: continue | done | needs_human | refused
summary: string
requested_tool: string
stop_condition: string

This context is advisory. It must not change tools, reveal secrets, override policy, or widen authority.

runxhq/runx commit 36d4e611d0

Frequently asked questions

npx get-skill add runxhq/loop-operator-context