anchor-wrapper

Lock a write-once anchor from an experiment plan into anchor.md.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/LinkDry/Link-Research --skill anchor-wrapper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: anchor-wrapper
Source: https://github.com/LinkDry/Link-Research/tree/main/skills/anchor-wrapper
Command: npx skills add https://github.com/LinkDry/Link-Research --skill anchor-wrapper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locks a write-once anchor for the active experiment plan to ensure the contract remains stable across validation phases.

Core Features & Use Cases

  • Locks a write-once anchor from projects/<slug>/plans/<idea>/experiment-plan.md to establish the scientific contract for the active experiment line.
  • Prevents the current branch from mutating the anchor after it's created, until re-anchor is explicitly allowed.
  • Applies when project-brief is sufficiently defined and the branch is ready for validation.

Quick Start

Run the anchor-wrapper step immediately after finalizing the experiment plan to create and bind the immutable anchor to the active branch.

Frequently Asked Questions about anchor-wrapper

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

FAQPage Schema
How do I lock an experiment plan to prevent state mutation during validation?

Locking an experiment plan involves creating a write-once anchor that binds an immutable contract to the active branch. This prevents state mutation by writing identity, hypothesis, and success criteria to an anchor.md file before running validation or drift checks.

What is an immutable experiment anchor and when do I need one?

An immutable experiment anchor is a stable scientific contract locked to an active branch to enforce reproducibility. You need one when your project plan is sufficiently defined and ready for validation, drift checks, or judge verdicts.

How do I enforce reproducibility for an active branch before running a drift check?

You enforce reproducibility by locking a write-once anchor for the active experiment plan. This establishes a binding contract that prevents the current branch from mutating the anchor, ensuring stable state management across validation phases.

Does the experiment anchor lock the active branch permanently?

No, the anchor lock does not permanently lock the active branch. It prevents mutation of the anchor after creation until re-anchor is explicitly allowed, ensuring stable governance and versioning across validation phases.

What state files are updated when locking a write-once experiment anchor?

Locking a write-once anchor writes an anchor.md file and updates experiment-memory.md and STATE.md to reflect the anchored state. These files capture identity, hypothesis, success criteria, evidence boundaries, and disconfirming signals.