This project is a public Rust and AI learning lab. It is useful for engineers and teams who want AI foundations that are inspectable, typed, and small enough to understand completely.
Companies should sponsor this work when they care about:
- Rust-first AI education
- internal AI literacy beyond framework usage
- typed and auditable ML teaching examples
- category theory as an engineering tool
- workshop material for engineers moving into AI systems
- public technical education with reproducible examples
The strongest sponsor targets are:
- polished diagrams for every major pipeline
- workshop-ready exercise tracks
- facilitator notes for engineering teams
- advanced modules for attention and Transformer blocks
- CI-verified examples that stay runnable over time
- a public issue queue for clarity feedback and terminology review
Sponsorship funds time for:
- expanding skeletal chapters
- improving diagrams
- reviewing mathematical precision
- adding exercises and answer keys
- testing examples on clean machines
- maintaining public feedback loops
The online book will always remain open access at https://hghalebi.github.io/category_theory_transformer_rs/. Sponsorship is not wired to a payment platform in this repository yet.
When Kindle or hard copy editions are available, buying the Kindle version or a hard copy is a direct way to support continued public work on the project. Paid editions are support editions, not access gates. Paid editions will not remove free public access to the online book.
Plain rule: one reader may study, cite, link, clone, and run the project for personal learning. A company, team, class, cohort, workshop, course, or other commercial or organizational group with more than one person needs written permission before reproducing, adapting, distributing, or teaching substantial material from the book or repository.
Commercial or organizational reuse involving more than one person requires written permission when it reproduces, adapts, distributes, or teaches material from the book or repository beyond short quotation, linking, review, and individual-study allowances. This includes company workshops, company-sponsored workshops, internal team workshops, company reading groups based on copied or adapted material, paid training material, and course packs. If the material is reused by or for a company, team, class, workshop, cohort, course, or training program with more than one person, request written permission first. Citation is required where reuse is allowed, but citation alone is not permission and does not replace written permission for group commercial or organizational reuse. See LICENSE.md. Permission requests should start through the source repository: https://github.com/hghalebi/category_theory_transformer_rs.
Opening an issue or sending a request does not itself grant permission. Only an explicit written approval from a project owner or maintainer grants permission for the requested commercial or organizational group use.
Support editions are different from permission. Buying a Kindle version or hard copy supports the project, but commercial or organizational group reuse still follows the written-permission rule in LICENSE.md.