agreement-amendment

To create a traceable amendment, you submit a proposal with the parent agreement ID, proposer identity, amendment type, proposed changes in diff format, and rationale. The system routes it through ACT phases and outputs a consent record with an updated version number.

Amendment types include minor clarification, substantive change, scope expansion, and scope reduction. Each type is routed to the minimum required ACT level to ensure changes are deliberate and auditable.

The process archives the previous version and updates the registry with the new version number. This ensures historical versions are preserved alongside the comprehensive amendment record linked to the parent agreement.

Required inputs include proposer identity, parent agreement ID, amendment type, proposed changes in diff format, and rationale. These inputs drive the ACT routing and generate the consent record.

Yes, the system handles both scope expansions and scope reductions. It classifies the amendment type and routes it through the appropriate ACT phases to produce a versioned amendment record.

Formal consent records are needed whenever modifying existing agreements to ensure changes are deliberate and auditable. The system runs complete ACT cycles and generates a comprehensive amendment record for auditability.