LoopX Auto Research

This is a worker-local role playbook for auto-research panes. It is packaged with the auto-research capability and should be injected or referenced by the worker launcher; it is not a global LoopX skill for ordinary project agents.

Routing Boundary

Use this skill after a LoopX auto-research worker has a role profile, frontier item, launcher packet, or user-visible demo pane. The skill is the role playbook. It is not the source of truth for identity, authority, current frontier, or merge/publication permission.

Identity comes from LoopX control-plane metadata:

• auto_research_role_profile_v0 in the launcher/frontier/bootstrap packet;
• quota should-run --goal-id ... --agent-id ...;
• todo claim, capability token, write scope, and protected scope;
• repository or workspace AGENTS.md rules, which can only make the boundary stricter.

No role owns the full graph. Do not infer role from pane title, branch name, tmux window name, or the section of this skill that happens to be visible.

Pane Tick Contract

The generic multi-agent kernel owns the default LoopX project/doc-registry skills and the fixed A2A wake prompt. This skill should stay role-specific: use it after the pane-local tick has resolved identity, quota, and frontier from LoopX.

Compact frontier command: loopx --format json auto-research frontier --goal-id "$LOOPX_GOAL_ID" --agent-id "$LOOPX_AGENT_ID". Also honor quota should-run.

If the launcher exported LOOPX_ROLE_ID, LOOPX_ROLE_PROFILE_REF, or a profile JSON path, compare those values with the quota and frontier packets. Stop when they disagree. Do not guess the intended role.