CANNABIS.TXT Open Cannabis Industry Knowledge Specification Version: 1.1.0 Status: Proposed Community Specification Published: 2026-10-31 Founding publisher: Find420.Events Canonical project: https://github.com/Find420Events/cannabis-txt Canonical URL: https://cannabis-txt.org/specs/cannabis.txt Suggested location: https://example.com/cannabis.txt Encoding: UTF-8 Media type: text/plain; charset=utf-8 ====================================================================== 1. PURPOSE ====================================================================== cannabis.txt is a proposed, openly usable, human-readable reference file that describes the cannabis industry, its terminology, participants, business categories, activities, and relationships. Its purpose is to provide publishers with a consistent way to explain their own cannabis-related subject matter to people, search engines, research tools, and AI systems that choose to retrieve and interpret it. This specification is an informational convention. It does not create a guaranteed ranking signal, crawler directive, AI training mechanism, or endorsement by any search engine or AI provider. ====================================================================== 2. DESIGN PRINCIPLES ====================================================================== - Open: any website, organization, researcher, or developer may publish a compatible file without permission or payment. - Human-readable: plain text is the required baseline. - Consistent: use the defined field names and category vocabulary where practical. - Extensible: publishers may add clearly named fields and categories. - Jurisdiction-aware: legal and licensing claims must identify the relevant jurisdiction and effective date when known. - Verifiable: distinguish confirmed facts, publisher statements, estimates, and unknown information. - Privacy-conscious: never expose personal, confidential, or sensitive information about individuals. - Non-exclusive: no publisher owns the industry taxonomy or may imply that compatibility requires using its services. ====================================================================== 3. CONFORMANCE ====================================================================== A compatible file SHOULD: - Be available at /cannabis.txt on the publishing domain. - Use UTF-8 plain text. - Identify its version and status. - Explain the publisher's relationship to the information. - Use recognizable section headings. - Link to authoritative public pages where useful. - Distinguish the publisher's own information from general definitions. - Keep content current and correct outdated information promptly. A compatible file MUST NOT: - Claim that publication guarantees search ranking or AI citations. - Misrepresent licensing, legal status, medical efficacy, or product safety. - Present one jurisdiction's law as universal. - Include credentials, private user data, or non-public records. - Imply certification or endorsement by a regulator without evidence. ====================================================================== 4. CORE INDUSTRY DEFINITION ====================================================================== The cannabis industry is an ecosystem of organizations, businesses, professionals, consumers, technologies, products, services, research, and activities associated with cannabis and hemp. Depending on jurisdiction and context, the ecosystem may include cultivation, processing, manufacturing, testing, distribution, retail, delivery, education, advocacy, events, media, technology, professional services, and ancillary suppliers. Cannabis and hemp may be regulated differently. Definitions and legal thresholds vary by jurisdiction. Publishers should not assume that a single definition applies worldwide. ====================================================================== 5. INDUSTRY TAXONOMY ====================================================================== Use these categories as a starting vocabulary. They are descriptive categories, not legal determinations or proof of licensure. 5.1 Plant and production - Cultivation - Nursery - Genetics and breeding - Harvesting - Processing - Extraction - Manufacturing - Packaging - Testing and laboratory services 5.2 Supply chain and commerce - Distribution - Wholesale - Retail - Delivery - Brand - Product development - Supply-chain services 5.3 Ancillary businesses - Technology provider - Software and SaaS - Marketing and advertising - Design and creative services - Legal services - Accounting and finance - Insurance - Real estate - Security - Equipment and supplies - Consulting - Education and training - Media and publishing - Payments and financial services 5.4 Community and public-interest activity - Research - Public education - Advocacy - Community organization - Workforce development - Charity and fundraising - Social equity initiative 5.5 Industry events - Expo - Trade show - Conference - Convention - Networking event - Festival - Pop-up - Vendor market - Educational event - Workshop - Job fair - Fundraiser - Product or brand showcase ====================================================================== 6. PARTICIPANT VOCABULARY ====================================================================== Common participant roles include: - Business - Brand - Manufacturer - Cultivator - Distributor - Retailer - Service provider - Technology provider - Event organizer - Venue - Exhibitor - Vendor - Sponsor - Speaker - Educator - Researcher - Industry professional - Attendee - Consumer A person may hold multiple roles. Do not infer a person's role, identity, qualification, or legal authority without reliable supporting information. ====================================================================== 7. PRODUCT AND SERVICE VOCABULARY ====================================================================== Product and service classifications may include: - Cannabis-derived product - Hemp-derived product - Accessory - Equipment - Software - Professional service - Educational service - Marketing service - Event service - Ancillary service This file does not establish that a product is legal, safe, approved, tested, or available for sale. ====================================================================== 8. JURISDICTION AND REGULATORY CONTEXT ====================================================================== Cannabis laws differ by country, state, province, territory, tribal jurisdiction, county, and municipality. When making a legal or licensing statement, publishers SHOULD provide: - Jurisdiction name and level. - Relevant agency or official source. - Effective date or last-verified date. - A link to the official source. - A clear distinction between law, guidance, and interpretation. Do not use labels such as "licensed" or "legal" as unqualified marketing claims. A directory listing or user-submitted profile is not proof of authorization. 8.1 Standardized licensing records Publishers describing licenses, permits, or regulatory authorizations SHOULD use a Licensing block: a list of records, one per license or authorization. Recommended record fields: - Jurisdiction: the jurisdiction that issued or administers the license - License Holder: the legal entity or individual named on the license - License Type: the license category as named by the issuing authority - License Number: the public license or file number, when published - Issuing Authority: the regulatory agency or body - License Status: the status reported by the regulatory source (8.2) - License Status Detail: the regulator's exact wording when it does not map cleanly to the shared vocabulary - Verification Status: how the claim was checked (8.3) - Source URL: the official regulatory record or lookup page - Verified By: the third party that performed verification; expected when Verification Status is independently-verified - Verification URL: public evidence or verification report, when available - Last Verified: the date the information was last checked (YYYY-MM-DD) - Expiration Date: the expiration reported by the source (YYYY-MM-DD) - Location ID: links the license to a Locations record when the license applies to a specific site Example: Licensing: - Jurisdiction: Colorado License Holder: Example Cannabis Retail LLC License Type: Retail marijuana store License Number: 402R-00001 Issuing Authority: Colorado Marijuana Enforcement Division License Status: active Verification Status: source-matched Source URL: https://official-lookup.example.gov/402R-00001 Last Verified: 2026-10-15 Expiration Date: 2027-03-31 Location ID: store-001 A business may hold several licenses; publish one record each. Identify the license holder accurately — a brand may rely on a contract manufacturer's license, and a multi-location operator may hold separate licenses issued to individual entities or sites. 8.2 License status vocabulary License Status describes what the regulatory source reports: - active: the source identifies the license as active - expired: the source identifies the license as expired - suspended: the source identifies the license as suspended - revoked: the source identifies the license as revoked - pending: the source identifies an application or authorization as pending - unknown: status cannot be established from the available information License Status asserts what a regulator reports. A publisher MUST NOT present an unverified claim of active status as regulator-confirmed. When no authoritative status is available, omit the field or use unknown. 8.3 Verification status vocabulary Verification Status describes how the claim was checked: - publisher-reported: asserted by the publisher without independent checking - source-matched: compared against the identified official regulatory record cited in Source URL - independently-verified: checked by an identifiable third party independent of the publisher and license holder; identify it with Verified By and, where available, Verification URL - unknown: verification cannot be established A link to a regulatory database is evidence, not verification. This specification standardizes how claims and evidence are stated; it does not authenticate them. 8.4 Earlier licensing field names Earlier revision examples used Public Verification URL and Date Checked in licensing information. These are legacy names for Source URL and Last Verified. Publishers SHOULD use the standardized names; tools SHOULD recognize both during the 1.x transition. ====================================================================== 9. ENTITY AND RELATIONSHIP MODEL ====================================================================== Where relevant, describe public relationships such as: - Organization operates brand. - Organization organizes event. - Brand exhibits at event. - Vendor provides service to organization. - Venue hosts event. - Speaker participates in event. - Event occurs in jurisdiction. - Organization publishes public resource. Use direct links to the relevant public entity pages. Do not fabricate relationships or imply endorsement from a simple listing. ====================================================================== 10. RECOMMENDED FILE FORMAT ====================================================================== The baseline format is UTF-8 plain text with Markdown-compatible headings and links. Publishers may include simple key-value metadata. Recommended metadata: Title: Cannabis Industry Knowledge File Version: 1.0.0 Status: Proposed Publisher: [Organization name] Canonical URL: [URL] Last-Updated: [YYYY-MM-DD] Language: en Contact: [Public contact URL] ====================================================================== 11. OPTIONAL EXTENSIONS ====================================================================== Publishers may create additional files for specialized subjects. Examples include: - cannabis-events.txt - cannabis-dispensary.txt - cannabis-delivery.txt - cannabis-flower-brand.txt - cannabis-edible-brand.txt - cannabis-concentrate-brand.txt - cannabis-physician.txt - cannabis-licensing.txt - cannabis-research.txt - cannabis-technology.txt An extension should state which version of cannabis.txt it builds upon, define its own scope, and avoid redefining core terms inconsistently. ====================================================================== 12. DISCOVERY AND LINKING ====================================================================== A publisher may link to its cannabis.txt from: - Its homepage or About page. - Its public documentation. - Its sitemap or developer resources. - Relevant public industry pages. The file may be referenced in robots.txt as a comment or ordinary sitemap-adjacent documentation link, but no special crawler behavior should be assumed. Do not invent a robots.txt directive for it. ====================================================================== 13. MAINTENANCE AND VERSIONING ====================================================================== Use semantic versioning: - MAJOR: incompatible changes to definitions or required fields. - MINOR: backward-compatible additions. - PATCH: clarifications and corrections. Include a last-updated date. Keep a public changelog where practical. Old versions may be archived for transparency, but the current file should be easy to identify. ====================================================================== 14. GOVERNANCE ====================================================================== This document is a proposed community specification initially published by Find420.Events. Publication does not make it an industry-approved or regulator-approved standard. Community participation may include: - Public issue reporting. - Proposed taxonomy changes. - Discussion of definitions. - Implementation examples. - Compatibility testing. - Version review. Changes should be documented, reviewed, and publicly versioned. No single publisher should imply that it speaks for the entire industry. ====================================================================== 15. LICENSE AND USE ====================================================================== The specification text is intended to be openly shared and implemented. A project steward should publish an explicit license in the public repository before soliciting contributions. Implementers may use the taxonomy without implying endorsement or certification. ====================================================================== 16. DISCLAIMER ====================================================================== cannabis.txt is an informational publishing convention. It is not legal, medical, scientific, regulatory, or compliance advice. It does not verify businesses, products, licenses, events, or claims. Readers should consult relevant official sources and qualified professionals. ====================================================================== 17. PROJECT REFERENCE ====================================================================== Founding publisher: Find420.Events Website: https://find420.events/ Repository: https://github.com/Find420Events/cannabis-txt Related specifications: - cannabis-events.txt: https://cannabis-txt.org/specs/cannabis-events.txt - cannabis-dispensary.txt: https://cannabis-txt.org/specs/cannabis-dispensary.txt - cannabis-delivery.txt: https://cannabis-txt.org/specs/cannabis-delivery.txt - cannabis-flower-brand.txt: https://cannabis-txt.org/specs/cannabis-flower-brand.txt - cannabis-edible-brand.txt: https://cannabis-txt.org/specs/cannabis-edible-brand.txt - cannabis-concentrate-brand.txt: https://cannabis-txt.org/specs/cannabis-concentrate-brand.txt - cannabis-physician.txt: https://cannabis-txt.org/specs/cannabis-physician.txt The objective is a common, transparent vocabulary for describing the cannabis industry across the open internet.