Make artifacts portable.
File formats should be readable and useful outside one provider or runtime.
KNF / public recordStewardship / Specifications
Specifications
The contract should be easier to inspect than the implementation.
Specifications define formats, protocols, schemas, and compatibility expectations for Knowledge Images.
Specifications
Open infrastructure starts with an open contract.
A V5 Knowledge Image is a bounded, content-addressed artifact: deterministic encodings, domain-separated SHA-256 roots, and a commit history. V4 remains a supported compatibility path.
Specification records will carry identifiers, version history, normative status, reference implementations, and conformance notes. Until those records are numbered and adopted, the working contract lives in public source and documentation.
Make systems interoperable.
Protocols define how independent components can communicate.
Make meaning durable.
Schemas clarify what an artifact contains and how it can evolve.
IndexStatus / scope
FormatKnowledge Image / .knolo
Current contractV5 in source
CompatibilityV4 preserved
ConformanceIndependent implementation