An operator says, 'Schedule a review with the launch team next Tuesday.' The final Calendar event is only the visible endpoint. A trustworthy system preserves the chain from intent to evidence.
Discover the capability
The agent searches by intent and selects an immutable Calendar contract. It requests the full schema only for that candidate, reducing context use while keeping the action version and OAuth requirements explicit.
Build a valid request
- Resolve the calendar, start and end time, timezone, and attendee list.
- Reject missing required fields and unknown argument names.
- Generate a clear preview of the event and invitations.
- Bind the request to the agent, principal, tenant, and connection.
Authorize before side effects
Policy may auto-allow a free/busy read while requiring approval for an event that emails attendees. The pending action records its risk, reason, expiry, and pinned approval threshold. No invitation is sent before the decision completes.
Record the result and check when supported
After supported execution, the Calendar provider result enters the signed ledger. If the selected contract has an implemented post-condition, Pakkawork reads the event back and checks time, attendees, and identifiers; otherwise the outcome remains explicitly unchecked. The trajectory can later be inspected or replayed where replay support exists.
Frequently asked
Why preserve the original contract version in a trajectory?
Without the pin, a later replay could use a changed schema or behavior and no longer represent the original execution.
Does a trajectory include approvals?
For supported execution, the lifecycle connects the request, policy decision, human decisions, and provider result. Verification and compensation events appear only when the selected contract implements those capabilities.