Evidence Options

Evidence options describe the types of evidence that connectors may choose to produce while operating inside the lnkpt container substrate. Evidence generation is optional and depends entirely on the connector’s product design. lnkpt provides the environment in which such evidence can be generated and exposed through the connector’s declared API surfaces.

These capabilities apply equally to standalone deployments, where a single connector may expose a dedicated endpoint that produces retention logs, audit trails, or other structured evidence without requiring changes to existing infrastructure.

Optional Nature of Evidence

lnkpt does not require connectors to produce evidence. Some connectors may expose simple service endpoints with no evidence output at all. Others—particularly those interacting with retention systems, audit platforms, or regulated services—may choose to generate structured evidence as part of their functionality.

Standalone deployments often use this model to introduce a single evidence‑producing endpoint in a clean, isolated manner.

Types of Evidence

Connectors may produce one or more types of evidence, including:

• Retention logs — records suitable for long‑term storage.
• Audit trails — chronological logs for compliance or monitoring.
• ISO 42001‑aligned evidence packets — structured outputs supporting AI governance frameworks.
• Connector‑specific evidence — any evidence format defined by the connector’s product design.

lnkpt does not interpret evidence content; it only provides the environment in which evidence is produced.

Association with Connector Versions

Evidence produced by a connector should be associated with the connector’s declared version. This allows downstream systems—such as retention servers or audit platforms—to understand which version of the connector generated the evidence. lnkpt does not enforce version semantics; it relies on the connector to declare its version accurately.

Exposure Through API Surfaces

Evidence outputs are exposed through the connector’s declared API surfaces. A connector may:

• Expose evidence directly through an API endpoint
• Provide evidence as part of a retention or audit feed
• Forward evidence to an external system such as a retention server

lnkpt ensures that the API surfaces are reachable but does not define how evidence is formatted or delivered.

In standalone deployments, this model allows a single connector to act as a clean evidence gateway without introducing cross‑cutting dependencies.

Environment Support

lnkpt provides the stable environment required for connectors to generate evidence reliably. This includes consistent container boundaries, predictable lifecycle behaviour, and stable exposure of API surfaces. lnkpt does not store or manage evidence; it only hosts the connector that produces it.