Record a signed contract
Records a contract signed on an adoption, a foster placement or an intake. Its merge fields are filled from the record now, and the text as it then reads is kept on the signature for good: changing the template later does not change it. The typed name is the signature, and consent to sign electronically must be recorded. A contract with a merge field nothing fills is refused, and the refusal names them in unresolved_fields. Signed on an adoption that is active, it fills in the adoption’s contract record where it is empty. The person who made the key is recorded as the team member who took the signature. Needs write on Animals. A transport booking is signed elsewhere. A booking is on the control plane, which the Animals Worker does not bind, so its facts (the services, the miles, both organizations) arrive with the request - and only the Edge Router may supply them. Sign one through POST /api/transport-space/bookings/{id}/agreement instead, which checks the booking, that this rescue is the carrier on it, and that the rescue signing is the one taking space. Named here rather than refused in silence: 403 with that sentence is what a caller gets.

