lattice-governor

Govern lifecycle and quality of public delivery-capability contracts in the Lattice repository.

Updated Jun 1, 2026
One-click install
npx skills add https://github.com/aurora-atoms/lattice --skill lattice-governor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lattice-governor
Source: https://github.com/aurora-atoms/lattice/tree/main/skills/lattice-governor
Command: npx skills add https://github.com/aurora-atoms/lattice --skill lattice-governor

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a structured governance framework for managing public delivery-capability contracts, ensuring that reusable assets remain evidence-grounded, version-controlled, and free of private business context.

Core Features & Use Cases

  • Capability Governance: Author, refactor, and validate public Skill packages and Agent contexts using strict semantic versioning and authoring gates.
  • Registry & Schema Design: Maintain machine-readable registry records and schemas to ensure interoperability across the Lattice ecosystem.
  • Use Case: When proposing a change to a public capability standard, use this Skill to perform a token-efficient refactor, verify compatibility against existing registry records, and generate the required validation evidence.

Quick Start

Use the lattice-governor skill to validate the current capability package and generate a refactor report for the target skill directory.

Frequently Asked Questions about lattice-governor

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

FAQPage Schema
How do I validate reusable capability contracts for semantic versioning compliance?

You can validate reusable capability contracts by applying automated trigger and output evaluation gates that enforce strict semantic versioning and public-private boundary rules. This ensures registry records remain evidence-grounded and version-controlled.

What is public-private boundary governance for delivery-capability schemas?

Public-private boundary governance ensures that reusable schemas and registry records remain free of private business context. It enforces strict adherence to public delivery-capability contracts during creation and refactoring.

Can I use Python to automate registry record refactoring for Lattice capabilities?

Yes, Python is required to run the scripts that govern the lifecycle and quality of public Lattice capabilities. These scripts perform token-efficient refactoring and generate validation evidence for target skill directories.

What's the best way to refactor public Skill packages without breaking existing registry records?

The best way to refactor public Skill packages is to verify compatibility against existing machine-readable registry records and generate validation evidence. This maintains interoperability across the Lattice ecosystem.

When do I need automated trigger and output evaluation gates for capability governance?

You need automated trigger and output evaluation gates when proposing changes to public capability standards. They enforce authoring gates and verify that refactored assets remain evidence-grounded.