factory-governance-loading

Load and validate file-based governance snapshots with MD5 hash checks.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-governance-loading
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: factory-governance-loading
Source: https://github.com/e2its/myrmion-AI-factory/tree/main/.claude/skills/factory-governance-loading
Command: npx skills add https://github.com/e2its/myrmion-AI-factory --skill factory-governance-loading

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When LLM context windows are summarized during long agent sessions, all in-memory governance context (project rules, stack configuration, compliance constraints) is permanently evicted, leaving agents unable to enforce project governance and risking invalid artifacts, compliance failures, or broken builds. This Skill eliminates that risk by using file-based governance snapshots that survive context summarization.

Core Features & Use Cases

  • File-Based Governance Snapshots: Stores all project governance context in a persistent .context/governance_snapshot.md file that is not lost during context compaction or summarization.
  • 4-Tier Hook Enforcement: Automatically detects stale governance snapshots, drift in source constitution/setup files, and triggers reloads without requiring manual agent intervention.
  • Dual-Hash Validation: Tracks MD5 hashes of both docs/constitution.md and docs/setup.md to instantly invalidate snapshots when source governance files change.
  • Use Case: For example, when a QA agent resumes work after a long context summarization, it automatically loads the valid governance snapshot, validates it against current project files, and enforces all applicable compliance rules without missing any context.

Quick Start

When starting any CODESIGN, BLUEPRINT, QA, IMPLEMENT, or DEVOPS agent command, automatically load and validate the governance snapshot from .context/governance_snapshot.md to ensure all project rules and constraints are active.

Frequently Asked Questions about factory-governance-loading

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

FAQPage Schema
How do I maintain governance context for SDLC agents after LLM context summarization?

To maintain governance context after LLM context summarization, use file-based governance snapshots stored in a persistent .context/governance_snapshot.md file that survives context compaction without losing project rules.

How does drift detection work for project governance files?

Drift detection works by tracking dual MD5 hashes of source files like docs/constitution.md and docs/setup.md to instantly invalidate governance snapshots when underlying project configuration changes.

Why does my software agent lose compliance rules during long context window sessions?

Agents lose compliance rules during long sessions because LLM context summarization permanently evicts in-memory governance context, requiring file-based snapshot reloading to restore validation workflows.

Can I use file-based governance snapshots for both QA and DevOps agent commands?

Yes, file-based governance snapshots apply to all non-SETUP and non-AUDIT SDLC agents including CODESIGN, BLUEPRINT, QA, IMPLEMENT, and DEVOPS for command start and post-summarization context recovery.

What is the best way to enforce zero-trust governance without consuming excessive context window space?

The best way to enforce zero-trust governance efficiently is by using token-efficient on-demand rule loading with 4-tier hook enforcement, validating snapshots automatically without consuming excessive context window space.

Do I need manual agent intervention to reload stale governance context?

No, manual agent intervention is not needed because 4-tier hook enforcement automatically detects stale governance snapshots and triggers reloads natively when source constitution or setup files change.