agreement-versioning

Track immutable governance agreement versions with semver-based snapshots and diffs.

2|Updated Mar 13, 2026

Search Tags:#versioning #audit #provenance #governance #diff #immutability

Ready to run

npx skills add https://github.com/Community-Chests/neos-operating-system --skill agreement-versioning-community-chests

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agreement-versioning
Source: https://github.com/Community-Chests/neos-operating-system/tree/main/neos-core/layer-09-memory/agreement-versioning
Command: npx skills add https://github.com/Community-Chests/neos-operating-system --skill agreement-versioning-community-chests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Organize and preserve a complete, immutable history of every governance agreement so there is a verifiable record of changes, rationales, and approvals.

Core Features & Use Cases

Automatic version creation on agreement creation, amendments, and reviews.
Immutable snapshots with full history and rationale for each version.
Diff generation between versions to show exactly what changed.
Provenance capture including author, date, source skill, and approval record.
Support for rollback proposals via the ACT process while maintaining a complete audit trail.

Quick Start

Trigger an agreement-creation process to generate the initial version record and begin the immutable history.

Frequently Asked Questions about agreement-versioning

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

FAQPage Schema

How do I track immutable governance agreement versions across their lifecycle?▼

Immutable governance agreement versioning uses semver-based versions and immutable snapshots triggered during creation, amendment, and review events. This preserves a verifiable record of changes, rationales, and approvals throughout the lifecycle.

How does diff generation work for agreement amendments?▼

Diff generation for agreement amendments compares immutable snapshots of different versions to show exactly what changed. It highlights the specific text modifications made between versions while linking to the author, date, and approval record for full provenance.

Can I rollback a governance agreement to a previous version while maintaining an audit trail?▼

Yes, you can rollback a governance agreement to a previous version via the ACT process while maintaining a complete audit trail. The rollback proposal is tracked as a new event, ensuring provenance and historical integrity remain intact without overwriting past records.

What provenance data is captured during agreement versioning?▼

Provenance data captured during agreement versioning includes the author, date, source skill, and linked approval records. This audit-focused provenance ensures every version snapshot has a verifiable history of who made changes and when they were officially approved.

When do I need immutable snapshots for legal compliance agreements?▼

You need immutable snapshots for legal compliance agreements when you must maintain a verifiable, tamper-proof history of governance changes. This is essential for passing audits, proving the rationale behind amendments, and demonstrating that all changes followed proper approval workflows.