Contact

This page routes contact to the right channel for the right kind of matter.

For spec bugs and proposed changes

Open an issue on the GitHub repository:

• Spec bug or typo: open a spec-bug issue
• Proposed core claim type or change: open a core-claim-proposal issue
• Other spec feedback: open a general issue on the repository

For substantive changes, the LIP process is the formal mechanism. Issues are appropriate for smaller matters and initial discussion.

For security vulnerabilities

Security disclosures go through private channels described in the security policy. Do not file security vulnerabilities as public GitHub issues.

Preferred path: GitHub Private Vulnerability Reporting. Alternatives are encrypted email to [email protected] with PGP, or plain email to the same address.

For governance matters

The project author can be contacted directly at [email protected] for matters that cannot be discussed in public or that are not appropriate for the issue tracker. See the governance page for the full governance model.

For discussion of proposed changes

GitHub Discussions is the venue for discussion of LIPs and proposed changes during their review period. LIP frontmatter links to the specific discussion thread for each proposal.

For everything else

Send general inquiries to [email protected].

Response times

• Security reports: acknowledgment within 5 business days per the security policy.
• Other contact: best effort, typically within a few business days. LLMO is maintained by a small team and is not a commercial product; response times are not SLA-bound outside the security policy.