PARTNER GUIDE / SERVER EDGE
Connect a model, data service, application or infrastructure. Keep control of your records and give your team a clear account of the work.
Development and testing in progress. Partner connections are configured with an operator; this guide prepares your request and installation.
01 / From invitation to first service
Confirm your organisation, administrator and participation under the current Chamber rules.
Name one contribution, its interface and where the edge will run.
Use your assigned identity, package and private connection settings. Check one retained original and its proof.
Agree the service, price, acceptance criteria and mandate. Publish an offer or place an order within those terms.
The account brings together your identity, authorised people and applications, mandates, budgets, obligations and receivables. We connect the existing wallet mechanism to that account. A cryptocurrency purchase is not required to start. Keys stay with the nominated operator; signing authority and spending limits are agreed before activation.
02 / Choose where your edge runs
Docker and native Linux use the same server-edge implementation. Each organisation has its own identity and persistent book. The edge itself does not require a GPU or an AI API key.
Use the Linux/amd64 container on your approved infrastructure. A Kubernetes renderer prepares a dedicated namespace, persistent volume and restricted application access.
Run the same Python runtime and pinned dependencies directly as a managed service. Docker is not required.
Request a separate edge on infrastructure you approve. Your application connects through an authorised API route.
One version for Docker / Kubernetes and native Linux systemd. The connection pack contains the exact build, SHA-256 checksums, installation instructions and your organisation’s configuration. View the release manifest or download checksums.
03 / Your organisation-specific connection pack
Application → private edge intake. Authorised reader → private edge read port. Edge → assigned mTLS route over outbound HTTPS 443 → Co-Tru Ledger Technology and proof services. For Kubernetes, the tunnel shares the edge’s pod; for Docker it shares the edge’s network namespace. Workload access inside your environment follows your approved network policy or service mesh.
After receiving your configuration pack, verify its checksums and load the supplied image on an approved machine:
sha256sum --check --ignore-missing SHA256SUMS
docker load -i neo-server-edge-linux-amd64.tar.gzMirror it into your registry and pin the registry digest. The image’s configuration ID is not a pullable registry digest. Use the supplied renderer and the organisation’s configuration to review a stopped deployment, persistent volume, trust and network rules. Start one replica only after those settings are agreed.
For Docker, use the supplied organisation-specific runtime profile with a persistent data volume and the tunnel in the same network namespace. Do not map the unauthenticated native intake or reader onto the public internet.
Your pack contains co-tru-edge-2026.11.01-linux-systemd-amd64.tar.gz, an offline installer and hash-locked dependencies. Use Linux x86_64 with Python 3.12 and venv, a dedicated service user, and assigned configuration, trust and persistent data paths.
The supplied install_linux.py verifies the package and creates a systemd unit. Your administrator reviews the configuration and starts the service. It runs deploy/partner-edge/runtime.py run; runtime.py probe checks local readiness. The installation profile fixes the Python environment, component paths and service-manager settings. Keep the same book and identity across a restart.
Receive the tunnel configuration through the same private channel. Generate its private key locally; only the certificate request leaves your environment. Renewal and revocation belong to the connection lifecycle.
04 / Connect one application event
Choose one real application hook: a completed model call, a delivered message, a resource allocation or a data query. Begin with a synthetic event using the same fields.
Private HTTP port 4311, application/x-protobuf, OTLP LogRecord envelope. Application events are not generic JSON requests.
Private TCP port 9600. Existing read commands: STATUS, RECORDS, BLOB and CONFIRM. Reader access is authorised separately.
neo.provider.id — assigned organisation/provider identifier.event_name — agreed audit.* event, with a fixed original timestamp.audit.record.id, audit.actor.id, audit.actor.type, audit.action, audit.outcome.audit.target.id and agreed typed attributes connect the event to the job.Inside your supplied environment, use its offline example generator with your assigned provider. It creates the original, request and reference files without sending anything. From an authorised producer, submit those saved bytes:
curl --fail-with-body --max-time 20 \
-H 'Content-Type: application/x-protobuf' \
--data-binary @first-event/request.pb \
http://neo-edge:4311/v1/auditneo-edge is the private service name in the supplied Kubernetes layout. A native installation uses the private address assigned in its connection sheet. The initial receipt allows the business workflow to continue; subsequent confirmations and FINAL evidence arrive asynchronously.
For an uncertain submission, retain the same event identity and exact bytes and use the application’s durable retry path. A changed identity is a new event. The connection guide supplies the retry and proof-verification procedure.
05 / A first service to try together
Your agent can buy or deliver a service within an agreed mandate. A data provider supplies an authorised answer, a model or application prepares the result, and the account follows accepted delivery.
Our LAB has exercised buyer and seller agents through MCP, grounded-answer delivery, limits per deal, acceptance checks, objections and records in each principal’s book. This gives a concrete starting workflow for a partner service.
The agent acts for its organisation, under its budget and permitted actions. Co-Tru’s OpenShell integration supplies execution evidence for sandboxed work; the recorded market workflow uses MCP. A partner’s complete combination is checked during integration.
Agent Market connections use the same Co-Tru server edge 2026.11.01 package. This is a LAB workflow and proposed partner use. A model’s answer is checked against the agreed acceptance criteria; Chamber decisions remain human.
06 / Prepare your connection
Tell us what you want to connect. The guide prepares a connection brief for your administrator and our operator. No credentials or original business documents are needed here.
This public form prepares onboarding. Account activation, wallet binding and access grants are confirmed by the operator through the private connection process.