Optional local agent
Use the product-supplied agent when it is part of the institution’s deployment.
#Product component
The local agent is a Sigillum component, not an application that customer teams must build. Run the delivered agent package with institution-specific configuration. It is not required in every deployment.
#Configuration example
{
"localTransfer": {
"endpoint": "http://127.0.0.1:29520",
"token": "LOCAL_TOKEN_ISSUED_BY_THE_INSTITUTION_INSTALLATION"
}
}This is one section of an existing service configuration, not a complete file. Retain the other identity and trust fields, including the signed-scope and custody-receipt trust material. Obtain the token from the institutional installation.
#Supported address boundary
Use an explicit IPv4 loopback address and port. localhost, remote hosts, IPv6, paths, queries, fragments and proxy redirection are outside this boundary. When the agent is selected, an outage does not trigger an automatic fallback to direct remote HTTPS delivery.
#Receipt meaning
The token-authenticated local HMAC receipt confirms durable custody of the identified package and records by the agent. It does not confirm sealed publication in ClickHouse. Central forwarding, retries and profile verification continue in the product agent.
