Open Almond Studios · Licensing & Creator Permissions
Use what you need. Know which permission applies.
The licensing structure is deliberately simple: open rules, optional compatibility branding, protected game-line worlds, and direct agreements for everything else.
Four paths. Clear boundaries. No hidden prerequisites.
A project can use more than one path, but each permission stays in its own lane. CC BY controls designated IE-SRD Content. PBI controls compatibility branding. CGL controls defined uses of proprietary game-line material. A separate agreement covers only what those public permissions do not.
Open rules content
Integrity Engine System Reference Document
IE-SRD · CC BY 4.0
01
I want to use the engine in my own game.
Use material expressly designated as IE-SRD Content under Creative Commons Attribution 4.0 International. Attribution is required; an application is not.
The mechanics are open. The compatibility mark is curated. The worlds remain protected.
Think of the architecture as layers, not competing licenses. Start with the material you are actually using and add another layer only when the project needs it.
Foundation
IE-SRD · CC BY 4.0
Reusable rules content. Attribution required.
Optional brand layer
Powered by Integrity
Terms + qualification standard + Creator Kit.
Proprietary IP layer
Covenant Gaming License
Community/media permissions for covered game-line material.
Only when needed
Separate Agreement
Commercial derivatives, reserved assets, publication relationships, adaptations, and negotiated rights.
Common projects
Where should I start?
Open-access copy tools
Only the open resources are copy-ready here.
IE-SRD / CC BY attribution and the IE Action Symbols font credit remain public because neither requires creator-program approval. Powered by Integrity and commercial CGL copy-ready notices are issued inside the approved project record that authorizes their use.
IE-SRD / CC BY 4.0
Required whenever designated IE-SRD Content is reproduced or adapted.
Required IE-SRD attribution
CC BY attribution is mandatory. Powered by Integrity is not.
This work is based on the Integrity Engine System Reference Document (IE-SRD) [SRD version], published by Open Almond Studios, LLC; designed and written by Benjamin J. Schmidt, with editing and additional contributors identified in the official IE-SRD credits; and licensed for use under the Creative Commons Attribution 4.0 International license (https://creativecommons.org/licenses/by/4.0/). Source: [official IE-SRD URL].
If applicable: This work contains modified Integrity Engine System Reference Document (IE-SRD) Content.
Controlled creator programs
Read publicly. Apply only when you want controlled brand or game-line resources.
PBI and CGL policies, standards, eligibility guidance, do/don't rules, and FAQs are public. Copy-ready PBI/commercial-CGL notices, PBI badge files, Creator Kit files, and official game-line resources are issued through approved project records. The IE-SRD attribution tools and Action Symbols font remain open-access resources.
Open tools stay open. Controlled kits stay with the approval.
The IE Action Symbols font remains a public production asset under its package permission. Powered by Integrity and commercial CGL production assets are not exposed from the public Licensing Hub; approved projects receive them inside Creator Programs.
Public asset permission
IE Action Symbols Font
Official glyph font and reference package for Integrity Engine action symbols and tracking marks. Its README supplies the controlling asset permission and required artist credit.
Read the PBI Terms, Compatibility Standard, Integrity Clause, usage rules, and FAQs publicly. Copy-ready publication notices and Creator Kit files are issued only to an approved project.
Approval required for badge & Creator Kit · Terms v1.0 · Standard v1.0
I want to make fan content or media for an Open Almond Studios game line.
The CGL remains public for defined fan content, actual play, ministry, reviews, and tutorials. Commercial derivative projects and official game-line creator resources require project approval.
Public community permission · commercial project resources by approval
I need something the public permissions do not grant.
Use a direct written agreement when a project needs rights beyond CC BY, PBI approval, or the commercial CGL project pathway—for example major adaptations, co-publishing, unusual reserved assets, distribution relationships, or custom terms.
PBI and commercial CGL kits unlock per approved project.
The public pages teach the programs. They do not expose production badge files, Creator Kit archives, commercial CGL publication templates, or separately authorized game-line logo resources. Those appear inside the approved project workspace for the publication that may use them.