Library
The Library is where Modulo primitives live and are shared. All platform primitives are first-class library citizens: schemas, workflow bundles, agents, and integrations (connector type packages).
Primitive types
| Type | Description |
|---|---|
schema |
Schema definitions |
workflow |
Workflow bundles |
agent |
Agent definitions |
integration |
Connector type packages |
Local and community primitives
Local and community primitives share a single library_primitives table with a source discriminator:
| Source | Meaning |
|---|---|
local |
Created within the org |
registry |
Cached read-only copy from the community registry |
Copy to adapt
One-click copy creates a local editable instance. forked_from is immutable provenance metadata.
- By default, copied primitives check for upstream updates (
auto_update = TRUE) - When an update is available,
update_available_version_idis set on downstream forks - The owner can apply the update or set
auto_update = FALSEto diverge freely
Trust tiers
Community registry primitives carry one of two trust tiers:
| Tier | Badge | Behavior |
|---|---|---|
| Verified publisher | Green | Ed25519-signed by a Modulo-vetted key. No warning on copy |
| Community | Amber | Unsigned or self-signed. Warning on copy: “This primitive has not been verified by Modulo. Review the prompt template and schema before use.” |
Rating system
- One rating per user per primitive
- Self-rating is blocked
- Rating requires at least one prior copy-to-adapt (you must have used it)
- 10-minute submission cooldown per user
- Ratings display as a weighted average with a review count
Battle-tested defaults
The Library is the primary onboarding path. On first boot, the UI surfaces recommended primitives for the user’s declared tool stack. Users start from library primitives and migrate to bespoke over time.