GUARDAID Annex 1: Interaction between software agents

Two software agents meet. There is no service in between, no person watching and no central record. Out of the interaction come actions, and out of the actions come consequences — a purchase, an access granted, a file handed over — and afterwards nobody can verify who authorized whom, under what mandate, or in what order. This annex specifies the form and the traceability of that encounter. The agent that starts it declares what it is going to do and with whom before doing it. The agent that receives it verifies the form of the package — signature, mandate, ticket, chain of custody — before reading the content, and reads the content as data, never as an instruction. Each party keeps its half of the record, containing the other's signatures, so that a third party can later establish what was done, under what mandate and in what order, without calling anyone. It uses the GUARDAID Passport away from a door, and the declared actions of Guardalpha-Base. Communication is one more declared action; presence and distress are declared actions with a finite cost; delegation narrows the mandate link by link; and a program received from another agent becomes executable only when a person registers it. Each receiver keeps a sovereign admission policy, and the reading of the package is identical everywhere. It defines five extension fields of the GUARDAID core, registered in the GUARDAID extension registry, version 1. Open, free of charge, with nothing to sign. Files. The annex in English, which is the normative language, and a Spanish translation as an informative version; where the two differ, the English governs. Feedback. Corrections, implementation reports and findings of an error are welcome at critical@vitrixy.eu. A difference between two of these documents is a defect in one of them, and reporting it is the fastest way it gets fixed.