License
Individual protocols remain CC BY 4.0 in perpetuity. The organized body — the curated registry, the taxonomy, the four-surface protocol cards, the curriculum bundles, the implementation guides, custom adaptations, audit reports, and cohort training — is licensable under tiered terms.
Three Tiers
Open Commons
Browse, cite, and apply individual protocols.
- Registry browsing free
- Individual protocol text free under CC BY 4.0
- Citation required for academic use
- Sample curriculum overviews free
- DOI-anchored sources accessible
- SPXI Generator tool available to all
Educational License
For schools, workshops, humanities programs, AI literacy labs.
- Full curriculum bundles (Semantic Integrity 101, Prompt-Native Runtime 201, etc.)
- Slide decks and lesson plans
- Workshop materials and exercises
- Certification rubrics
- Instructional support during deployment
- Cohort training option for instructors
Professional
For organizations deploying protocols at scale.
- Implementation templates customized to your entity portfolio
- Custom protocol adaptation for novel domains
- Audit engagements (PER, CDI, Drowning Test panels)
- Longitudinal compositional-survival studies (90-day panels)
- Cohort training for your team
- Ongoing implementation support
- Inquiries route through the Semantic Economy Institute
Request a proposal
Tell us a little about your situation. We'll respond within three business days.
Frequently asked
If individual protocols are CC BY 4.0, what exactly is licensable?
Three things, primarily. First, the organized body: the curated registry, the seven-category taxonomy, the four-surface protocol card schema, the dependency graph, the cross-protocol consistency. Reproducing the registry as a system requires license. Second, the curricula and implementation materials: slide decks, lesson plans, exercises, certification rubrics, workshop kits. These are not individual protocols; they are pedagogical artifacts derived from the protocols. Third, the services: custom protocol adaptation, audit engagements, longitudinal panels, cohort training. The protocols themselves remain free; the application of them to your specific situation is paid work.
Do I need a license to cite a protocol in academic writing?
No. Citation under CC BY 4.0 only requires attribution to the source. Cite the protocol's DOI and you are in compliance. The Educational License becomes useful when you want curriculum-ready materials — slide decks, lesson plans, exercises — rather than just the protocol specification.
Can I deploy SPXI inscription on my own website without a license?
Yes. SPXI is CC BY 4.0 under RA-PROT-0001. The SPXI Generator tool on this site produces deployable output free of charge. Where a Professional License becomes useful is when you want help auditing your deployment (CDI panels, Drowning Test cycles), implementing across an entity portfolio, or developing custom SIM tag types for novel domains.
What does an audit engagement actually deliver?
Depends on scope. A baseline engagement typically delivers: (1) a Composition Divergence Index measurement for your target entities across 3–4 composition platforms; (2) a Provenance Erasure Rate measurement; (3) a Holographic Kernel composed for each target entity; (4) deployed SPXI inscription for each canonical web surface; (5) a written audit report with DOI-anchored deposit. A 90-day longitudinal engagement adds weekly Drowning Test panels and a time-series report. All measurement records are deposited to Zenodo and remain accessible to you in perpetuity.
Do you sign NDAs?
Yes, for Professional engagements when the client's situation requires it. The audit methodology itself remains open and citable; what becomes confidential is your specific deployment, your measurement data, and the strategic recommendations. The Crimson Hexagonal Archive remains the institutional source of the methodology; your engagement is your engagement.
How do I cite the registry as a whole?
Cite the Charter at DOI 10.5281/zenodo.20327083 and the Bundle DOI at 10.5281/zenodo.20327578 (which preserves the v1.0 launch state of the registry). For specific protocols, cite their individual DOIs from the source-DOI section of each card.