Introduction

lnkpt is a container substrate for certified connectors. It provides a stable, predictable environment where connectors can operate consistently and expose their defined API surfaces. These surfaces may include retention server endpoints, audit log feeds, or connections to regulated services such as .gov systems.

lnkpt is intentionally lightweight and can be deployed as a standalone container to host a single connector or a dedicated endpoint. This allows organisations to introduce new API surfaces without modifying existing infrastructure, keeping integration clean and low‑impact.

Purpose

The purpose of lnkpt is to provide a consistent runtime for certified connector products. lnkpt does not define or certify connectors; instead, it offers the environment in which connectors run, ensuring that each connector behaves as designed and exposes its API surfaces reliably. This separation keeps connector design independent while allowing lnkpt to focus on stability, predictability, and operational clarity.

Scope

This specification defines the conceptual model, connector model, API surface model, operational requirements, and versioning rules that govern how connectors operate within lnkpt. It does not prescribe connector content, domain‑specific behaviour, or policy requirements. lnkpt is designed to support a wide range of connector products without imposing assumptions about the APIs they expose or the environments they interact with. These concepts are expanded in the Conceptual Model and Connector Model.

Role of lnkpt

lnkpt provides the container environment in which certified connectors operate. Its role is to ensure that connectors run consistently, expose their API surfaces predictably, and interact with their configured environments in a stable manner. Some connectors may also produce optional evidence outputs—such as retention logs or audit trails—when their product design requires it. These evidence options are described further in the Evidence Options section.

Because lnkpt can operate as a standalone deployment, it is suitable for incremental adoption. Organisations can introduce a single connector—such as a retention endpoint or a regulated‑service interface—without restructuring existing systems or introducing cross‑cutting dependencies.