Public Draft LKP-0003

Machine Metadata

Version 0.9.5 | Published: July 2, 2026

1. Abstract

LKP-0003 defines the technical interface between the protocol and automated systems (LLMs, Crawlers, Validators). It ensures that the "Living" status of knowledge is verifiable by machines without human intervention.

2. Standard Meta Tags

Every LKP-compliant page MUST include the following meta tags in the <head> section:

<meta name="lkp-version" content="1.0.0">
<meta name="lkp-status" content="Public Draft">
<meta name="lkp-living-site" content="true">
<meta name="lkp-modified" content="YYYY-MM-DD">

3. JSON-LD Schema (Normative)

For Level 2+ compliance, pages MUST include a structured data block conveying LKP metadata. Two equivalent formats are recognized:

3.1 Format A — Nested (Recommended)

LKP metadata is nested inside an lkp property, under a standard schema.org type at the top level (e.g. WebPage, Article). This is the recommended format: it keeps the JSON-LD block fully compatible with standard schema.org consumers (search engines, rich results) while still exposing LKP-specific fields to LKP-aware validators. 

{
  "@context": "https://livingknowledgeprotocol.org/ns/1.0.0",
  "@type": "WebPage",
  "name": "Document Title",
  "url": "https://...",
  "lkp": {
    "@type": "LivingDocument",
    "version": "1.0.0",
    "status": "Public Draft",
    "datePublished": "2026-06-26",
    "dateModified": "2026-08-17"
  }
}

3.2 Format B — Top-Level (Legacy)

Earlier implementations used LivingDocument directly as the top-level @type. This format remains supported for backward compatibility with early adopters, but is not recommended for new implementations since LivingDocument is not a recognized schema.org type. 

{
  "@context": "https://livingknowledgeprotocol.org/ns/1.0.0",
  "@type": "LivingDocument",
  "name": "Document Title",
  "dateModified": "2026-08-17",
  "lkp": {
    "complianceLevel": 1,
    "isLiving": true,
    "verificationSource": "https://..."
  }
}

3.3 Namespace Versioning Policy

The canonical, current namespace for the @context field is https://livingknowledgeprotocol.org/ns/1.0.0. New implementations MUST use this namespace.

An earlier namespace, https://livingknowledgeprotocol.org/ns/1.0, is still in use on some existing implementations published before this versioning policy was clarified. This legacy namespace is DEPRECATED. Official LKP validators (including the LKP-SDK CLI) will report it as compliant with a migration warning until December 31, 2026. After this date, pages still using the legacy namespace will FAIL validation. Implementers are strongly encouraged to migrate to 1.0.0 well before this deadline.

4. Site Manifest (lkp.json)

A root-level lkp.json file SHOULD be present to provide site-wide protocol information. This file acts as the primary discovery mechanism for AI agents.

5. Discovery Mechanisms

Compliance with LKP-0003 SHOULD be declared in the robots.txt and llms.txt files to facilitate automated discovery and indexing.

Knowledge is progressing. The Real remains.