-
Notifications
You must be signed in to change notification settings - Fork 0
Enterprise Trial Distribution Sync
Huzefaaa2 edited this page Jun 28, 2026
·
1 revision
This public-safe sync records that the private Enterprise repository now has a trial distribution pipeline for licensed evaluator access.
Private implementation status:
- private repository:
Huzefaaa2/cavra-enterprise; - private PR:
#86; - distribution target: gated GHCR image
ghcr.io/huzefaaa2/cavra-enterprise-trial:<version>; - release evidence: private trial package readiness JSON, release approval JSON, and image digest evidence;
- release gate: trial package approval is blocked unless private license-service readiness is true;
- runtime boundary: the private trial runtime image is built in the private repository and validated for Enterprise source exclusion in the runtime package layer.
The public Community repository may document:
- trial request and evaluator onboarding instructions;
- the private image name and expected pull pattern;
- license activation requirements;
- public-safe trial success criteria;
- Community-to-Enterprise upgrade boundaries.
Do not publish:
- Enterprise source code;
- trial image layers or binaries;
- bytecode artifacts;
- private workflow logs with operational details;
- license keys, signing material, or revocation state;
- registry credentials or pull secrets;
- customer records or tenant identifiers;
- paid policy packs;
- SaaS backend implementation details.
Approved evaluators should receive one of these access paths:
- gated private GHCR image access plus a time-limited trial license;
- private compiled binary access plus a time-limited trial license;
- hosted SaaS trial tenant using hosted license validation.
Community Edition remains usable without a license key. Enterprise Trial access is licensed and must validate through private Enterprise or SaaS services.
Connect private trial release approvals to live license issuance and evaluator access workflows, then sync public docs again with only public-safe references.
CAVRA Field Compass
Before the agent acts, CAVRA asks: who is acting, what will change, what policy applies, and what evidence will prove it?
Before the agent acts, CAVRA asks: who is acting, what will change, what policy applies, and what evidence will prove it?
| Start | Build | Operate | Assure |
|---|---|---|---|
| Quick Start | CLI | Enterprise Guide | AISPM |
| Reader Paths | Policy Syntax | Deployments | Evidence |
| Community | GUI | Troubleshooting | Conclusion |
Textbook home: Before the Agent Acts |
Development archive: development and testing artifacts |
Source repository: github.com/Huzefaaa2/cavra
- Foreword And Reader Paths
- Why CAVRA Exists
- Runtime Authority Model
- Architecture
- Editions
- Install And Deploy
- Community Guide
- Enterprise Guide
- CLI Reference
- GUI And Sandbox
- AISPM Guide
- Policy And Evidence
- Operations And Integrations
- Labs And Use Cases
- Appendices And FAQ
- Policy Language Reference
- Troubleshooting Playbook
- Conclusion