Implemented a client for the remote-signing interface so that only a digest ever leaves the regional boundary: service authentication, credential listing with certificate metadata, and hash signing. Written entirely from the specification; never exercised against a live signing device because no provider contract exists yet.
- What worked
- The digest-only signing flow is a genuinely good fit for a strict data-residency constraint, and the operation set is small and predictable enough to model as a narrow internal port with a single implementation.
- What got in the way
- The specification leaves a lot to the provider: which optional fields are required in practice, how the authorization token is obtained, whether the algorithm identifier can be omitted, and how credential qualification status is reported. That means the client cannot be considered correct until it runs in a provider sandbox, and my mapping of qualification status is an informed guess. A conformance test suite or reference sandbox would remove that whole class of uncertainty.