Operational Requirements

The operational requirements define how certified connectors run within the lnkpt container substrate. These requirements ensure consistent behaviour across deployments while allowing connectors to remain independent products with their own logic, configuration, and API surfaces.

lnkpt supports both multi‑connector environments and standalone deployments where a single connector is hosted in isolation. Standalone mode enables organisations to introduce a dedicated endpoint without modifying existing infrastructure, keeping integration clean and low‑impact.

Container Boundaries

lnkpt provides the container environment in which connectors operate. Connectors must run entirely within these boundaries and may not modify the substrate or other connectors. Container boundaries ensure:

• Isolation between connectors
• Predictable resource usage
• Consistent exposure of API surfaces
• Stable behaviour across deployments

In standalone deployments, these boundaries ensure that the connector remains isolated from existing systems, reducing integration complexity.

Resource Expectations

Connectors must declare their expected resource usage as part of their metadata. This may include CPU, memory, storage, or network requirements. lnkpt does not enforce resource limits; it relies on declared expectations to support predictable operation.

Standalone deployments typically have minimal resource contention, making declared expectations straightforward to satisfy.

Lifecycle Management

Connectors operate within a defined lifecycle managed by lnkpt. The lifecycle includes:

• Initialisation — loading configuration and preparing API surfaces.
• Active operation — exposing declared surfaces and performing connector logic.
• Update — applying new versions without disrupting declared behaviour.
• Shutdown — graceful termination and optional evidence finalisation.

This lifecycle applies equally to standalone and multi‑connector deployments.

Update Rules

Connectors may be updated to new versions while running inside lnkpt. Updates must:

• Preserve declared API surfaces unless explicitly versioned
• Maintain configuration compatibility where possible
• Respect container boundaries and isolation rules

lnkpt provides the mechanism for applying updates but does not interpret connector versioning.

External Dependencies

Connectors may interact with external systems such as retention servers, audit platforms, enterprise services, or regulated endpoints including .gov systems. Connectors must declare these dependencies in their metadata. lnkpt does not validate or manage external systems; it provides the environment in which connectors interact with them.

Standalone deployments often use this model to introduce a single new integration point without altering existing infrastructure.

Configuration Handling

lnkpt provides the mechanism for supplying configuration values to connectors. Connectors must:

• Define a clear configuration schema
• Validate configuration during initialisation
• Handle missing or invalid configuration gracefully

lnkpt does not interpret configuration content; it only delivers values to the connector.

Optional Evidence Generation

Some connectors may produce evidence outputs such as retention logs, audit trails, or ISO 42001‑aligned evidence packets. These outputs are optional and depend entirely on the connector’s product design. lnkpt provides the environment in which such evidence can be generated and exposed through the connector’s API surfaces.