Role fields
Role names are contract API identifiers. Do not translate them; translate their descriptions.
Parts modes
Example design
For a bilateral service agreement:
The instance lists one provider Legal ID and one customer Legal ID as parts. The contract becomes
Signed only after both valid signatures exist.
Role-reference parameters
A role parameter copies an approved Legal Identity property into a parameter slot when that role signs. This can bind contract text to facts such as organization name, country, or another identity property without manual re-entry. If a required property is missing from the identity, role-parameter population fails. Clear populated role parameters before reassigning a part.Design guidance
- Use the minimum number of roles that expresses the legal relationship.
- Set bounded
MaxCount; an unbounded role can change signature semantics. - Explain revocation consequences in the human-readable section.
- Do not use an XMPP JID where a Legal Identity ID is required.
- Decide whether parties are fixed before proposal or selected when instantiating a template.