agreement-versioning

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.

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.

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.

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.

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.