governed-research

Coordinate bounded governance research cycles for strategy configurations.

1|Updated Apr 28, 2026
One-click install
npx skills add https://github.com/recallnet/polymarket-cross-sectional-momentum --skill governed-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: governed-research
Source: https://github.com/recallnet/polymarket-cross-sectional-momentum/tree/main/.agents/skills/governed-research
Command: npx skills add https://github.com/recallnet/polymarket-cross-sectional-momentum --skill governed-research

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @recallnet/skunk-research-governance, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Coordinates bounded governance research cycles to safely evaluate and promote strategy configurations while preserving a strict separation between research configs and promoted/live configs.

Core Features & Use Cases

  • Enforces separation between research and promoted configs to prevent unintended live changes.
  • Runs governance evaluation using a candidate JSON artifact and a governance script, producing a ledger entry and a decision.
  • Supports reference workflow documentation to guide governance gates, budgets, and promotions.

Quick Start

Provide a governance candidate JSON and run the governed-research script to evaluate it.

Frequently Asked Questions about governed-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run bounded governance research cycles to evaluate strategy configs?

Bounded governance research cycles require a topic worktree, a governance candidate JSON, and a governance script to evaluate strategy configurations and produce a ledger entry with a decision.

What is the best way to separate research configs from promoted live configs?

Separating research configs from promoted configurations prevents unintended live changes during governance research cycles by enforcing strict boundaries between evaluation artifacts and live strategy deployments.

How do I evaluate challengers and apply governance gates across multiple executors?

Evaluating challengers across multiple executors uses a governance script and candidate JSON artifact to apply governance gates, budgets, and promotions while outputting a decision ledger entry.

Do I need a governance candidate JSON to start research guardrails?

A governance candidate JSON is required alongside a topic worktree and governance script to initiate the research guardrails that produce a structured ledger entry and promotion decision.

What limitations exist when promoting strategy configurations through governance rounds?

Promotion limitations stem from strict separation between research and promoted configs, requiring governance gates and budgets to pass before a candidate JSON can produce a valid promotion decision.

Can I use governance scripts to improve existing autoresearch strategy configurations?

Governance scripts can improve autoresearch strategy configurations by running bounded governance research cycles that evaluate candidate JSON artifacts and record ledger entries for configuration promotion.