anchor.diff:  
   {{TimelockController}}
   
  +[[timelock-terminology]]
   ==== Terminology
   
   * *Operation:* A transaction (or a set of transactions) that is the subject of the timelock. It has to be scheduled by a proposer and executed by an executor. The timelock enforces a minimum delay between the proposition and the execution (see xref:access-control.adoc#operation_lifecycle[operation lifecycle]). If the operation contains multiple transactions (batch mode), they are executed atomically. Operations are identified by the hash of their content.
  
positive.code: ** *Proposer:* An address (smart contract or EOA) that is in charge of scheduling (and cancelling) operations.
  ** *Executor:* An address (smart contract or EOA) that is in charge of executing operations.
  
  ==== Operation structure
  
  Operation executed by the xref:api:access.adoc#TimelockController[`TimelockControler`] can contain one or multiple subsequent calls. Depending on whether you need to multiple calls to be executed atomically, you can either use simple or batched operations.
  
negative.code: 
  In the case of batched operations, `target`, `value` and `data` are specified as arrays, which must be of the same length.
  
  [[timelock-operation-lifecycle]]
  ==== Operation lifecycle
  
  Timelocked operations are identified by a unique id (their hash) and follow a specific lifecycle:
  