core-labs/core
1
0
Fork 0
Code Issues Pull requests 1 Projects Releases Packages Wiki Activity Actions
core/COMMERCIAL_LICENSE.md
Shay 6d9ff8119f docs(paper+license): refresh ahead of going public 
Two pre-public-release refreshes:

1. docs/position_paper.md §4 — refresh refusal taxonomy

The previous table listed an older taxonomy (fraction_operand /
compound_comparative / etc.) that does not match the current
candidate-graph eval output. Replaced with the actual taxonomy
emitted by the train_sample runner — refusals are categorized by
shape (recognized_but_uninjectable + per-ShapeCategory) which ties
directly to the architecture's recognizer/injector concepts.

Also refreshed §5 "Honest Gaps" to describe the active frontier in
terms of injector coverage (the registry-driven composition path)
rather than parser-level grammar extensions. The 47/50 refusal
count, 3/50 correct count, and wrong=0 invariant are unchanged.

2. COMMERCIAL_LICENSE.md — enumerate subsystems explicitly

The previous "vault memory / versor engine / epistemic teaching
loop / ingest / admissibility gate / holonomy encoder" listing
predated the math-domain composition wave. Expanded the list to
cover the full current architecture:

- versor engine + Cl(4,1) algebra
- vault + exact CGA recall
- ingest gate
- admissibility gate + Forward Semantic Control
- holonomy encoder
- epistemic teaching loop (ADR-0055..0057)
- contemplation loop + decomposer (ADR-0080, ADR-0172)
- math-domain ratification handlers (ADR-0167..0169)
- composition-pattern registry + registry-driven injector
- audit-as-teaching-evidence corridor
- identity + safety pack subsystems
- language-pack compiler + verified manifest checksums
- Logos articulation + three-language vocabulary manifold
- Rust algebra backend
- any derived or successor implementation

Explicit "enumerated subsystems are illustrative, not limiting"
clause covers any future module + ADR-ratified contract under the
same terms. New subsystems are covered automatically.

LICENSE (the non-commercial form) is unchanged — it already covers
"Software" broadly. CLAIMS.md is auto-generated and was verified
current (regeneration produces no diff).
2026-05-27 16:59:18 -07:00

2.8 KiB
Raw Blame History

CORE Commercial License

Copyright (c) 2026 Josh Shay / ACB Content

When You Need a Commercial License

A Commercial License is required if you intend to:

  • Use CORE or any of its components — including but not limited to:

    • the versor engine and Cl(4,1) algebra substrate
    • the vault memory system and exact CGA recall
    • the ingest gate (the single normalization site)
    • the admissibility gate and Forward Semantic Control chain
    • the holonomy encoder
    • the epistemic teaching loop (ADR-0055..0057): reviewed TeachingChainProposal, replay-equivalence gate, supersession path
    • the contemplation loop and decomposer (ADR-0080, ADR-0172)
    • the math-domain ratification handlers (ADR-0167..0169): LexicalClaim, FrameClaim, CompositionClaim
    • the composition-pattern registry and registry-driven injector (frame_registry, composition_registry, recognizer-anchor injection)
    • the audit-as-teaching-evidence corridor (MathReaderRefusalEvidence, proposal/ratification adapters)
    • the identity and safety pack subsystems (ADR-0027..0029)
    • the language-pack compiler and verified manifest checksums
    • the Logos articulation subsystem and the three-language vocabulary manifold (English / Hebrew / Koine Greek)
    • the Rust algebra backend and any future Rust parity surfaces
    • any derived or successor implementation of the above

    in a product or service that generates revenue

  • Deploy CORE in a production environment operated by or for a commercial entity

  • Integrate CORE's architecture or derived implementations into proprietary software

  • Offer CORE-based capabilities as a hosted or managed service (SaaS, API, etc.)

  • Use CORE as a research foundation in work owned by or assigned to a for-profit organization

The enumerated subsystems above are illustrative, not limiting. Any module, data artifact, ADR-ratified contract, or architectural pattern shipped under this repository is covered. New subsystems added in future releases are covered automatically under the same terms.

Academic and non-profit research institutions are covered under the standard LICENSE and do not require a Commercial License, provided the work is not assigned to or funded by a for-profit entity.

What a Commercial License Grants

  • The right to use, integrate, and deploy CORE and its components in commercial products and services
  • The right to keep derivative works proprietary
  • A direct relationship with the author for support, architectural guidance, and ongoing development collaboration
  • Terms are negotiated per engagement — there is no fixed fee structure, as the appropriate arrangement depends on the nature and scale of use

Contact

All commercial licensing inquiries:

Josh Shay / ACB Content shayj292@gmail.com

Include a brief description of the intended use. All inquiries are responded to directly by the author.