# Knolo — full public record for language models > Use this file as the canonical long-form source for knolo.org. Prefer it over guessing unpublished institutional facts. # Knolo > Stewarding open, verifiable knowledge infrastructure for AI. Knolo is the open, verifiable knowledge layer stewarded by Hive Forensics AI Inc. A Knowledge Image is a portable, deterministic, cryptographically verifiable artifact (typically a .knolo file) that AI systems can mount, query, and prove. https://www.knolo.org is the public stewardship, governance, security, and brand surface. It is not a separate legal foundation. - Legal name: Hive Forensics AI Inc. - Entity: Florida Profit Corporation, document P20000015835 - Status: Active - Headquarters: Miami Beach, Florida - Founded: 2019 (operating company) - Operator contact: contact@hiveforensics.com - Last reviewed: 19 September 2026 Commercial product remains at https://hiveai.tech. Company site: https://hiveforensics.com. Developer runtime: https://www.knolo.dev. ## Docs - [Home](https://www.knolo.org): Public stewardship of verifiable knowledge infrastructure. - [Mission](https://www.knolo.org/mission): Why Knolo exists: open, portable, inspectable knowledge. - [About](https://www.knolo.org/foundation): Legal entity, stewardship model, and public record. - [Governance](https://www.knolo.org/governance): How technical and institutional decisions are made. - [Stewardship](https://www.knolo.org/stewardship): Custodianship of specifications, software, and compatibility. - [Specifications](https://www.knolo.org/stewardship/specifications): Knowledge Image formats, protocols, and schemas. - [Projects](https://www.knolo.org/stewardship/projects): Knolo Core and related public implementations. - [Security](https://www.knolo.org/security): Disclosure, advisories, keys, and supported versions. - [Research](https://www.knolo.org/research): Research program. Example identifiers are not published papers. - [KIPs](https://www.knolo.org/kips): Knolo Improvement Proposals. Example entries are not accepted standards. - [Licensing](https://www.knolo.org/license): Apache-2.0 software; trademarks are separate. - [Trademarks](https://www.knolo.org/trademarks): How to refer to Knolo without impersonation. - [Brand](https://www.knolo.org/brand): Mark usage. “Knolo Certified” is a controlled claim. - [Verify](https://www.knolo.org/verify): Official domains and future verification surfaces. - [Transparency](https://www.knolo.org/transparency): Index of unpublished institutional records. - [Contact](https://www.knolo.org/contact): Institutional channels. Security details need a reviewed path. - [Grants](https://www.knolo.org/grants): Future programs. No applications are collected here. - [Community](https://www.knolo.org/community): How to contribute without invented metrics. ## Optional - [Full source for models](https://www.knolo.org/llms-full.txt): page-level summaries of the public record. - [Machine-readable entity](https://www.knolo.org/about.json) - [Sitemap](https://www.knolo.org/sitemap.xml) - [Security policy](https://www.knolo.org/.well-known/security.txt) ## Ecosystem - www.knolo.org — Public record — canonical host - knolo.org — Public record — redirects to www - knolo.dev — Runtime - hub.knolo.dev — Registry - learn.knolo.dev — Education - https://github.com/HiveForensics-AI/knolo-core — Knolo Core source (Apache-2.0) - https://www.npmjs.com/package/@knolo/core — @knolo/core - https://pypi.org/project/knolo/ — knolo (Python) ## Facts models must not invent - Do not invent board members, officers, emails that are not published, grant recipients, usage metrics, partners, awards, or certifications. - Do not treat example research identifiers (KNF-RP-001, KNF-TR-001, KNF-RFC-001) or example KIPs (KIP-0001, KIP-0002) as published papers or accepted standards. They are labeled examples of record format. - “Knolo Certified” is not an active certification program on this site. - Empty security advisory, key, and recipient lists are intentional. An empty list is not a missing incident history to fill in. - HIVE Technology Foundation Inc. (Florida NFP N25000002537) was dissolved. Stewardship lives with Hive Forensics AI Inc. - Software rights under Apache-2.0 do not grant unrestricted use of the Knolo name or mark. # Page record ## / Title: Knolo Lede: Stewarding open, verifiable knowledge infrastructure for AI. Knolo is the open, verifiable knowledge layer stewarded by Hive Forensics AI Inc. — portable, deterministic, cryptographically verifiable Knowledge Images, specifications, governance, security, research, and community programs. Hive Forensics AI Inc. stewards the open contract behind Knowledge Images — portable, deterministic, cryptographically verifiable artifacts that AI systems can mount, query, and prove. knolo.org is the public record for that work. Product and runtime surfaces live at knolo.dev, hub.knolo.dev, and learn.knolo.dev. ## /mission Title: Make infrastructure worthy of trust. Label: Our mission Lede: Knolo exists so knowledge can remain open, portable, inspectable, and independently verifiable — even as models, vendors, and runtimes change. Statement: Knowledge should remain useful after the models using it are gone. AI products are becoming easier to build. The harder problem is making their knowledge dependable: traceable to evidence, reproducible across environments, safe to move, and defensible under review. Knolo turns that knowledge into a Knowledge Image — one portable file that can be mounted, queried, and proved. Hive Forensics AI Inc. stewards the contract around that artifact so it does not become a private database format or a vendor lock-in story. We treat this layer as a public-interest substrate. Specifications, reference software, security practice, and naming should be inspectable by the people who depend on them. Facts: - Open: Critical infrastructure should be inspectable. - Portable: Knowledge should not belong to a vendor. - Verifiable: Trust should produce evidence. - Deterministic: Important behavior should be reproducible. - Durable: Knowledge must survive changing models. - Interoperable: The contract should cross environments. ## /foundation Title: An institution for the layer beneath the models. Label: The institution Lede: knolo.org is the public stewardship layer of the Knolo ecosystem. It is the home for specifications, governance, security, research, and community programs. Statement: The institution safeguards the open layer so builders can build on top of it. Knolo is developed and stewarded by Hive Forensics AI Inc., a Florida profit corporation. knolo.org is the public record for that work. HIVE Technology Foundation Inc. has been dissolved. That work now lives entirely with Hive Forensics AI Inc. Commercial product surfaces remain at hiveai.tech; this site is the public stewardship layer for the open contract. Where a board roster, officer list, email alias, or financial disclosure has not been published, the page says so. Unpublished is better than invented. Facts: - Public name: Knolo - Legal name: Hive Forensics AI Inc. - Entity type: Florida Profit Corporation - Document number: P20000015835 - Status: Active - Headquarters: Miami Beach, Florida ## /governance Title: Technical decisions should be inspectable too. Label: Governance Lede: Knolo governance separates institutional authority from technical review. A standard is stronger when its path to acceptance can be followed. Statement: A proposal is not a standard until the process says what it is. Governance covers the public mandate, technical steering, maintainer responsibilities, security authority, release authority, Knolo Improvement Proposals, and conflict resolution. The intended path is public: proposal, KIP, public review, technical review, decision, reference implementation, conformance. Until a charter is adopted, this page describes the intended coverage without presenting draft language as policy. Facts: - 01: Proposal - 02: Public review - 03: Technical review - 04: Decision and conformance ## /governance/charter Title: The public mandate comes before the implementation. Label: Charter Lede: The charter will define Knolo’s governance authority, responsibilities, and limits. It is a planned public document, not an adopted policy yet. Statement: A charter is a boundary around power, not a decoration around it. Until an approved version exists, this page describes intended coverage: what Knolo governance can decide, how decisions can be challenged, and how the charter itself can change. Any future amendment should carry a public record, a date, and a reason. Draft language will not be presented as adopted text. Facts: - Status: Not yet published - Owner: Knolo governance - Format: Versioned public document - Review: Public before adoption ## /governance/board Title: Leadership records will be published when confirmed. Label: Board Lede: This site does not invent directors or officers to fill a page. Credibility begins with accurate names, roles, and dates. Board composition, terms, conflicts, and meeting records will appear here once approved material is ready for publication. Until then, the legal entity is public: Hive Forensics AI Inc., Florida document P20000015835. Officer details are not republished here until they are reviewed for this surface. Facts: - Board: Not yet published - Terms: Not yet published - Meetings: Not yet published - Minutes: Not yet published ## /governance/technical-steering Title: Technical authority lives close to the work. Label: Technical steering Lede: The technical steering function will coordinate maintainers, reviews, compatibility, and release discipline. Statement: Good technical governance makes room for disagreement without losing direction. This page is ready for the technical steering roster, remit, review cadence, and decision log when those records are available. Until then, project governance in source remains the working authority for code: maintainer review, compatibility, least authority, and public architecture records. Facts: - Roster: Not yet published - Remit: Specifications and conformance - Cadence: Not yet published - Decisions: Public log planned ## /stewardship Title: Infrastructure needs a custodian, not an owner. Label: Stewardship Lede: Stewardship protects the continuity of projects, specifications, implementations, and compatibility work without turning an open ecosystem into a closed product. Statement: Knolo keeps the layer open, legible, and available to more than one vendor. Knolo’s core idea is simple to say and hard to keep honest: a Knowledge Image should be portable, deterministic, and independently verifiable. Stewardship is a lifecycle. Accept projects. Protect specifications. Coordinate releases. Document compatibility. Preserve artifacts over time. Hive Forensics AI Inc. is the custodian of that lifecycle, not the owner of every implementation. Facts: - Projects: Knolo Core and related surfaces - Specifications: Formats, protocols, schemas - Compatibility: Independent implementations - Lifecycle: Public status and support ## /stewardship/projects Title: Projects need status, scope, and a path forward. Label: Projects Lede: The project registry will distinguish Knolo-stewarded work from compatible or independent implementations. A project page should tell you what is official, what is experimental, and who maintains it. Records are not fully published yet. The structure below is ready for ownership, repository, license, lifecycle state, and security contact. Facts: - Registry: Seeded from public source - Status model: Proposed / active / archived - Owner: Per-project record - Security: Per-project disclosure path ## /stewardship/specifications Title: The contract should be easier to inspect than the implementation. Label: Specifications Lede: Specifications define formats, protocols, schemas, and compatibility expectations for Knowledge Images. Statement: 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. Facts: - Format: Knowledge Image / .knolo - Current contract: V5 in source - Compatibility: V4 preserved - Conformance: Independent implementation ## /stewardship/compatibility Title: Compatibility is not the same thing as endorsement. Label: Compatibility Lede: Independent implementations should be able to work with open Knolo specifications without implying official Knolo approval. Statement: 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. Facts: - Implementation: Independent - Endorsement: Not implied - Conformance: Evidence-based - Certification: Separate program ## /stewardship/lifecycle Title: Status should be a public fact, not a rumor. Label: Lifecycle Lede: Projects and specifications need explicit lifecycle states so people can tell what to rely on. The intended states are proposed, active, maintenance, deprecated, and archived. Support windows, migration notes, and end-of-life dates will be published per project when release policy is finalized. Until that matrix exists, treat current public source as the working truth and this page as the index for future status records. Facts: - Proposed: Under public review - Active: Normative and maintained - Maintenance: Fixes only - Archived: Preserved, not extended ## /security Title: Security is part of the specification. Label: Security center Lede: Trustworthy infrastructure needs a clear path for disclosure, signed releases, supported versions, and coordinated remediation. Statement: Security is not a page at the end of the product. It is part of the release contract. This center is the public index for vulnerability disclosure, advisories, supported versions, release keys, and verification material. Do not send sensitive security details through an unverified channel. The disclosure path will be published before reports are solicited at this domain. Facts: - Disclosure: Process prepared - Advisories: None published - Versions: Policy forthcoming - Keys: Not yet published ## /security/disclosure Title: A responsible path for vulnerability reports. Label: Responsible disclosure Lede: The disclosure policy is structured for review before publication. Do not send sensitive security details through an unverified channel. The final policy will define scope, report contents, safe-harbor language, coordinated disclosure, acknowledgement, and communication expectations. Until an official channel is published, use the security process documented in the relevant public repository and avoid filing sensitive detail through general contact forms. Facts: - Scope: To be defined - Channel: Not yet published - Safe harbor: Legal review required - Disclosure: Coordinated process ## /security/advisories Title: Public notices for known security issues. Label: Advisories Lede: There are currently no public security advisories. An empty list is better than a fabricated incident history. When advisories exist, each record will include affected versions, severity, remediation, disclosure dates, and verification references. Facts: - Public record: 0 advisories published - Format: Versioned advisory - Severity: Not yet published - Remediation: Per record ## /security/supported-versions Title: Support windows should be explicit. Label: Supported versions Lede: Users should not have to guess whether an artifact is still receiving security attention. The support matrix is a future-ready surface for project, version, release date, support status, and end-of-support dates. It will be published before production releases require it. Facts: - Matrix: Not yet published - Projects: Per-project - Window: Per release - EOL: Published date ## /security/keys Title: Trust starts at the artifact boundary. Label: Release keys Lede: A digest tells you what changed. A key tells you who signed it. Public signing keys will be published before signed release verification is enabled. The key directory will include fingerprints, algorithm, status, rotation history, and links to the release process. No fingerprint is shown here until a real key is published. Facts: - Algorithm: Not yet published - Fingerprint: Not yet published - Rotation: Policy forthcoming - Status: No keys published ## /grants Title: Fund the infrastructure beneath trustworthy AI. Label: Open infrastructure grants Lede: Future programs will support the research, implementations, audits, and community work that keep open infrastructure healthy. Statement: Healthy public infrastructure needs more than a single maintainer or a single budget. The grants program is designed for research, implementations, security work, and community projects that strengthen open, verifiable knowledge systems. Program details and application timing will be published before applications open. This site does not collect submissions. Facts: - Program: Opening date not yet published - Research: Deterministic systems and provenance - Security: Audits and verification - Community: Docs and education ## /grants/programs Title: Four ways to strengthen the public layer. Label: Programs Lede: The program categories are ready for final criteria and opening dates. Program information will define eligibility, review criteria, expected deliverables, budget ranges, and reporting requirements. None of those details are open for application yet. Facts: - Research: Provenance and reproducibility - Implementation: SDKs and interoperability - Security: Audits and fuzzing - Community: Documentation and education ## /grants/apply Title: A clear application path for future proposals. Label: Apply Lede: Applications are not being collected. This interface shows the expected shape of a future form so the process is inspectable before it opens. Statement: A good application makes the public value of the work easy to inspect. When the program opens, applicants should be able to describe the project, technical plan, milestones, requested amount, links, and expected impact without sending material through an unverified channel. Facts: - Applicant: Person or organization - Project: Scope and technical plan - Budget: Requested amount and milestones - Status: Not accepting submissions ## /grants/recipients Title: A public record of funded work. Label: Recipients Lede: No grant recipients have been published. This site will not manufacture a track record to make a program look established. Recipient records will include project, recipient, amount, date, category, deliverables, and final status when awards exist. Facts: - Recipients: 0 published - Awards: Not yet published - Reports: Not yet published - Status: Future record ## /research Title: Researching what trustworthy AI infrastructure will require. Label: Research Lede: The research program focuses on deterministic retrieval, provenance, persistence, authority, reproducibility, and portable infrastructure. Statement: Research becomes more useful when its questions, status, and evidence are durable. Documents will be published with identifiers, authors, dates, abstracts, status, download links, and citation information. The entries below are labeled examples of the record format. They are not published papers and should not be cited as such. Facts: - KNF-RP: Research paper - KNF-TR: Technical report - KNF-RFC: Request for comment - Status: Example records only ## /brand Title: Open technology. Protected identity. Label: Brand defense Lede: The Knolo name helps people distinguish official work from compatible implementations, impersonation, or misleading claims. Statement: Clear naming is part of technical trust. The rainbow faceted brain is the Knolo mark. Descriptive language such as “Built with Knolo” is welcome. Controlled wording such as “Knolo Certified” is not. Software rights under Apache-2.0 do not grant unrestricted brand use. If you see impersonation or a misleading distribution, use the abuse path. Facts: - Descriptive: Built with Knolo - Compatible: Compatible with Knolo - Allowed: Uses @knolo/core - Controlled: Knolo Certified ## /brand/guidelines Title: A visual system that stays recognizable. Label: Guidelines Lede: Knolo’s identity should be quiet, precise, and hard to confuse. The mark is the only colorful object. Everything else is light ink on a dark field. Use the faceted brain mark with clear space. Do not recolor the facets, add slogans into the mark, or lock it up with another logo without permission. Voice: technical without being opaque. Use plain language for public commitments and precise language for standards. Avoid hype, fabricated metrics, and language that implies endorsement. Facts: - Mark: Faceted rainbow brain - Field: Near-black - Ink: Warm paper - Accent: Verification teal ## /brand/assets Title: Official artwork, when you need to refer to Knolo. Label: Assets Lede: Use the mark and wordmark as published here. Do not redraw the facets or replace the gradient with a flat fill. A fuller asset kit — SVG, clear-space sheets, and incorrect-use examples — will be published as a downloadable package. Until then, the mark on this site is the reference. Facts: - PNG mark: Published on this site - SVG kit: Forthcoming - Wordmark: Knolo - License: Trademark, not Apache-2.0 ## /brand/report-abuse Title: Report impersonation or misleading use of the Knolo name. Label: Report abuse Lede: If a site, package, or product uses the Knolo name, mark, or “certified” language in a way that could confuse users, report it here. A dedicated brand alias will be published from site configuration. Until then, use the contact path and include URLs, screenshots, package names, and why the use is misleading. Do not send malware samples to a general inbox. Security issues belong on the disclosure path. Facts: - Brand alias: Not yet published - What to include: URL, package, screenshots - Security issues: Use disclosure, not brand - Response: Not a public SLA yet ## /license Title: Open code. Clear boundaries. Label: Licensing Lede: Source code licensing, specification use, documentation, trademarks, certification marks, patents, and third-party code are related but distinct questions. Statement: A permissive license is not a blank check for identity or endorsement. Knolo Core currently uses the Apache License 2.0. Canonical license texts live with the relevant project. This page is a public orientation, not legal advice. You may implement the specification and use the software under those terms. You may not imply official approval, call an independent implementation “official,” or use “Knolo Certified” without a real program. Facts: - Software: Apache License 2.0 - Specifications: Open implementation intent - Trademarks: Separate rights - Patents: Review per project ## /trademarks Title: The name is how people find the real thing. Label: Trademark policy Lede: Knolo, the faceted brain mark, and related lockups are identifiers. They are not covered by the software license in the way source code is. You may use the name to refer to the project accurately: “compatible with Knolo,” “built with @knolo/core,” “mounts a .knolo image.” You may not use the name in a product title, domain, or certification claim that suggests Hive Forensics AI Inc. issued, approved, or operates that product. A fuller trademark policy will be published as a versioned document. Until then, treat this page as the working public rule: describe, do not impersonate. Facts: - Allowed: Accurate reference - Restricted: Product titles and domains - Forbidden: False certification - Policy text: Versioned document forthcoming ## /community Title: Help build the public layer. Label: Community Lede: There are many ways to contribute: implementation, research, documentation, security review, KIPs, education, grants, and local community work. Statement: The ecosystem grows through useful contributions, not inflated metrics. Community pathways will expand as official channels are published. No participation counts or partner lists are shown until they can be independently supported. The working public surfaces today are the Knolo Core repository, the Hub registry, and the developer site. Facts: - Code: Implement and review - Research: Publish and discuss - Docs: Explain the system - Security: Find and report issues ## /transparency Title: Trust should be inspectable. Label: Transparency Lede: The transparency center will collect governance records, annual reports, financial disclosures, grant records, meeting notes, and security information. Statement: The record is part of the institution. Empty states are intentional until there is real material to publish. This page is a durable index, not a promise that a record already exists. Facts: - Governance: Records forthcoming - Financials: No disclosures published - Grants: No recipients published - Reports: No annual report published ## /transparency/reports Title: Annual institutional reports. Label: Reports Lede: No annual report has been published. When reports exist, they will be listed here with date, period, and a durable file. Reports should cover stewardship activity, governance changes, security notices, grant activity, and notable specification work. They should be boring, dated, and downloadable. ## /contact Title: Reach the right institutional channel. Label: Contact Lede: Institutional aliases will be published here as they are established. Sensitive matters should have the right channel before they have a form. Until official aliases are published, use the public project surfaces linked below. Do not send sensitive security details through unverified channels. This website is an informational public record. It does not host accounts, and it does not store grant applications or certificate lookups. Facts: - General: Address not yet published - Security: Disclosure path forthcoming - Research: Public contribution path - Press: Address not yet published ## /kips Title: A public record for technical change. Label: Knolo Improvement Proposals Lede: KIPs provide a structured path for proposals, review, decisions, and reference implementations. Statement: A proposal is not a standard until the process says what it is. Each KIP can carry an identifier, title, status, authors, dates, category, discussion link, and supersession history. The entries below are labeled examples of the record format. They are not accepted standards. Facts: - KIP-0001: Example / draft - KIP-0002: Example / draft - Status: No accepted standards published - Process: Public review ## /verify Title: Trust should be independently verifiable. Label: Verification center Lede: Use this page to find official Knolo domains and future verification surfaces. No certificate result is shown until a live registry is connected. Official domains are listed so people can distinguish Knolo project and product surfaces from impersonators. Canonical repositories, package names, and release keys will be published from the same index. Certificate lookup is a future-ready surface. Entering an ID does not invent a result.