Compatibility is not the same thing as endorsement.

Independent implementations should be able to work with open Knolo specifications without implying official Knolo approval.

Brand policy Specifications

Compatibility

Interoperability creates choice. Clear branding protects trust.

Anyone should be able to implement an open specification within its license terms. Compatibility claims should link to versioned tests or documented support. “Knolo Certified” is a separate program and is not implied by implementation.

Implement

Build against the contract.

Software rights come from the license. Naming rights do not.

Test

Show the evidence.

Compatibility claims should point at versions, fixtures, and results.

Identify

Use the name carefully.

Clear language helps users tell compatible from official.

IndexStatus / scope

ImplementationIndependent

EndorsementNot implied

ConformanceEvidence-based

CertificationSeparate program