Shared provider core

nmr-provider-tools owns the reusable provider package, result delivery service, network proxies and host delivery deployment. NMRNet installs its released provider-core wheel; it owns molecular input preparation, NMRNet++ execution and scientific results.

Release and installation

The shared owner publishes the wheel, source archive, installation lock and provenance record. NMRNet pins the GitHub artifact URLs and hashes and consumes the released installation lock offline. The source archive supplies reusable test fakes; consumers do not rebuild the package or import another checkout. See dependency inputs.

Delivery ownership

A provider retains a selected terminal request in memory until the shared service acknowledges durable intake. After acknowledgment, the service owns publication, retry and recovery of those exact bytes. It deletes a queued payload only after a verified matching API receipt or an explicit operator discard. Intake acknowledgment is not API completion.

If the provider stops before observing the intake acknowledgment, the remote Attempt may remain unresolved. The delivery service may still have stored the report if its acknowledgment was lost. After the delivery service restarts, it continues managing stored reports; some may require operator attention. A provider restart does not reconstruct the interrupted Attempt or repeat its scientific work. See result delivery and storage.

Shared configuration

One operator-owned binding definition supplies API identity, credentials, route and socket grants to both deployment owners. NMRNet derives those runtime settings from the selected binding. Its own definition supplies scientific policies, interpreter and Upload settings, producer retry budgets and execution limits.

Run the delivery service through the shared repository's maintained commands. Run NMRNet through its provider deployment commands. Operator-owned configuration and separate secrets are read-only inputs; shared queue and socket state stays in Docker volumes, without a generated host tree. Each owner controls its containers and storage; stopping NMRNet leaves shared delivery available to other providers.

Qualification

The shared owner qualifies core protocol, storage, proxy and deployment behavior. NMRNet checks its installed-package integration and scientific contracts. The consumer test guide describes those boundaries; API fixture provenance records the pinned contract evidence.