Connect an existing GSP deployment
Bind an approved native service without replacing it or guessing its endpoints.
Operator-bound configuration
The native bridge is disabled until all settings are present, including explicit approval. Use a TLS endpoint you administer; its token stays server-side. The included adapter defines a new website integration contract. An existing GSP service must implement or map this contract before the connection is usable.
GSP_NATIVE_URL=https://approved-gsp-host.example
GSP_NATIVE_RELEASE=exact-controlled-release
GSP_NATIVE_TOKEN=<secret from your secret store>
GSP_NATIVE_APPROVED=1
GSP_NATIVE_WORKFLOWS=approved-workflow-idCapabilities and execution
GET /capabilities and POST /execute must return schema garmo.native.bridge/1 and the configured release_id. Execution also echoes request_id and input_sha256 and reports completed, blocked or failed. The bridge rejects redirects, mismatched identity, non-JSON and responses over 1 MiB. Only approved workflow names are forwarded.
Organization access
Staff must record an executed-agreement reference and document digest before granting an organization access to the exact native release. A successful handshake alone does not grant rights. A customer must explicitly confirm that inputs may leave the website environment. Revocation is rechecked after the call before results are exposed.
What is not claimed
This release does not establish a live connection to a native GSP installation. Contract tests use a controlled test endpoint. The existing GSP must retain its own execution, resource, evidence, foundry and authorization policies. The website does not run a substitute EDA implementation.