Extension Claim Types
Extension claim types allow publishers to carry information beyond the core claim set defined in the LLMO specification. Extensions use the format namespace.type (for example, acme-corp.compliance_note), where namespace is a short identifier under the publisher’s control and type is a claim name within that namespace. The specification defines extension claims in §3.6.
Extensions do not require registration to be valid. A publisher may emit any well-formed namespaced claim type in a published llmo.json document, and conforming consumers ignore types they do not recognize, per §3.6. The LIP registry exists for discoverability of widely-adopted extensions, not as a permission gate on usage.
Proposing an extension
The LIP (LLMO Improvement Proposal) process is the mechanism for proposing new extension claim types to the registry. The authoritative process document is LIP-1. The full registry index is available at /spec/lips.
A Standards Track LIP is the LIP type used for extension claim type proposals. At a high level, the submission path is: open a public GitHub Discussion, observe a 7-day discussion period with at least one non-author response, request a LIP number and nonce from the editor, publish a DNS TXT record at the namespace domain as proof of control, then open a pull request adding the LIP document at /spec/lips/lip-NNNN.mdx. The complete process, including lifecycle states, editor role, anti-flood provisions, and namespace rules, is specified in LIP-1.
Why a formal process
The LIP process mirrors established governance mechanisms from Bitcoin (the BIP process, originating with BIP-1 by Amir Taaki in 2011, revised by BIP-2 and BIP-3) and Python (the PEP process, originating with PEP-1). The LLMO adaptation adds measures appropriate to its threat model: a DNS TXT proof-of-control record at submission raises the floor on flood economics by requiring a real-world domain registration; a mandatory pre-submission Discussion period filters casual submissions and creates a public deliberation record; one-open-Draft-per-domain prevents a single controlled domain from flooding the pipeline with parallel proposals; editor discretion covers apparent machine-generated submissions at volume. These provisions reflect the reality that format-compliant content can be generated at near-zero marginal cost, a condition earlier proposal processes were not designed around.
Promotion into the core specification
Promotion of Standards Track LIPs into the core LLMO specification is a separate governance action that occurs as part of a specification version bump per the versioning policy. LIP-2 (currently in governance) will formalize the submission mechanics.