Event driven coordination requires a means to “go back in time”, inspect earlier events and have an audit trail. On obvious reason is when a subcontractor is changed: the new subcontractor has to be able to quickly come up to speed on the history of events. The second is to have a common reference for either compliance or settling of disputes.
Dynamic modification
In real-world operations, it may become necessary to change subcontractors dynamically; removing one subcontractor from the network and replacing them with another.
To facilitate this, the Principal posts a notification of the change to the Order Log. This notification is then distributed to all parties involved in the network. The following steps are taken:
- Remove the Old Subcontractor: The old subcontractor is removed from the subscription lists, cutting off their access to further notifications and data.
- Add the New Subcontractor: The new subcontractor is added to the network, receiving the necessary notifications and access rights.
- Revoke the Old JWT Token: The JWT token that was issued to the old subcontractor is revoked, ensuring that they no longer have access to the network’s resources.
Creating a log
Once all tasks related to the order have been completed, the Principal closes the order and the Common Order Log. The Principal and generates a signed log. This log serves as an official record of all events and actions that took place during the order’s execution.
- Notification of Log Availability: A notification is sent to all parties involved, informing them that the signed log is available.
- Access and Retention: Subcontractors can access this signed log and retain a copy for future reference, whether for compliance purposes or in the event of a dispute.
This structured audit trail ensures transparency, accountability, and the ability to review and verify all actions taken during the course of the order, providing a solid foundation for trust and compliance in the BDI framework.