metric-lock

Lock evaluation metrics, protocols, datasets, and seeds after plan freeze.

11|1|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/EvoClaw/amplify --skill metric-lock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: metric-lock
Source: https://github.com/EvoClaw/amplify/tree/main/skills/metric-lock
Command: npx skills add https://github.com/EvoClaw/amplify --skill metric-lock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Locking evaluation components after plan freeze ensures that metrics, protocols, datasets, and seeds cannot be modified without explicit authorization, preserving integrity and reproducibility.

Core Features & Use Cases

  • Immutable locking of primary metrics, evaluation protocols, datasets/splits, and random seeds after plan freeze.
  • Formal change-request workflow (explain, justify, prove, wait, log) to govern any proposed modifications.
  • Audit trail and governance support for reproducibility, compliance reporting, and peer-review preparation.

Quick Start

Submit a change request detailing the exact item to change, justification, evidence, and await user approval.

Frequently Asked Questions about metric-lock

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

FAQPage Schema
How do I lock evaluation metrics after a research plan freeze to ensure reproducibility?

You lock evaluation metrics by applying an immutable freeze to metrics, protocols, datasets, and random seeds after a plan freeze, preventing post-hoc modifications without explicit authorization and preserving research reproducibility.

What is an audit trail for evaluation protocols and why is it needed for peer review?

An audit trail for evaluation protocols is an immutable log tracking all changes to metrics and datasets. It is needed for peer review to provide governance, prove compliance, and guarantee experiment reproducibility.

How do I submit a change request to modify a locked dataset or random seed?

You submit a formal change request detailing the exact dataset or seed to change, providing justification and evidence, and then await user approval before the modification is logged and applied to the locked evaluation protocol.

Can I use change management workflows to prevent post-hoc changes in shared codebases?

Yes, you can use formal change management workflows to prevent post-hoc changes in shared codebases by requiring a structured request, justification, and approval process before any locked evaluation metrics or datasets are modified.

Does locking evaluation metrics require any specific dependencies or components?

Locking evaluation metrics requires no specific external dependencies or components, operating independently to enforce governance, immutable logs, and change-request workflows across your research experiments and shared codebases.

When should I not use a formal change-request process for evaluation governance?

You should not use a formal change-request process for evaluation governance during early, exploratory research phases before a plan freeze, as the immutable locking of metrics and datasets restricts rapid iteration and protocol adjustments.