Distribute your AI standards with confidence
Publish skills, commands, and rules once — then distribute them to every team and tool with built-in approval, versioning, and drift detection.
GOVERNANCE MODEL
Four roles that make distribution trustworthy
Cendis maps to how teams actually distribute AI standards — publishers set the bar, consumers pull with confidence.
- Product Domain · Publisher
-
Product Publisher
e.g. Head of Product Ops
Governs org-wide product assets
- Product Domain · Consumer
-
Product Consumer
e.g. Product Manager
Browses catalog, pulls approved assets
- Engineering Domain · Publisher
-
Engineering Publisher
e.g. Staff Engineer
Governs engineering-domain assets
- Engineering Domain · Consumer
-
Engineering Consumer
e.g. Developer
Pulls approved assets via CLI into any project
ASSET TAXONOMY
Four asset types, purpose-built
Every artifact your team creates for AI development has a type. Cendis governs each one through its full lifecycle.
Skill
A reusable AI capability unit — an action your AI tools can execute on demand.
Command
A slash command callable by name during an AI coding session.
Template
A scaffolding template for new projects or files — consistent starting points.
Rules File
A configuration file — CLAUDE.md, .cursorrules, AGENTS.md, or similar — that governs how AI behaves in a codebase.
Two views, two audiences
Consumers browse and pull from the catalog. Publishers manage distribution health across products.
• Assets organized by lifecycle phase
• Searchable with version and status visible
• One-click pull into any product
• Deployment health across all products
• Drift detection at a glance
• Version pinning per product scope
SCOPE HIERARCHY
Built for how AI tools are configured
Modern AI coding tools use layered configuration — from org-wide policies down to project-level rules. Cendis governs which assets are approved at each level, across every tool your teams use.
Enterprise (org-wide)
Cendis manages
Project
Cendis manages
User
Cendis distributes to
Conversation
Assets active here
CLI
First-class terminal experience
Engineers pull approved assets directly into their environment. No context-switching, no manual downloads.
Cendis vs. copy-paste distribution
What changes when you stop copy-pasting and start distributing.
| Capability | Copy-Paste Distribution | Cendis |
|---|---|---|
| Approval workflow | PR review (ad hoc) | Structured phase gates |
| Drift detection | None | Automatic per-product |
| Version pinning | Git tags / branches | Semantic per scope level |
| Onboarding time | Manual repo clone + docs | cendis init (one command) |
| Audit trail | Git log (unstructured) | Per-asset event history |
| PM visibility | Requires Git access | Built-in dashboard |
Approval workflow
PR review (ad hoc)
Structured phase gates
Drift detection
None
Automatic per-product
Version pinning
Git tags / branches
Semantic per scope level
Onboarding time
Manual repo clone + docs
cendis init (one command)
Audit trail
Git log (unstructured)
Per-asset event history
PM visibility
Requires Git access
Built-in dashboard