Policy Modules — Sources

admin@pluris.local
A
Policy

Modules — Sources

Where the Library gets its modules from. Pluris-bundled is always present and read-only. Tenant-local is your own modules. Imported registries are external module catalogues your admin has approved.

Policy CatalogConfiguration GroupsModules
LibraryTenant defaultsSources
  • Pluris-bundled modules
    5 modules · always enabled · read-only · ships with this Pluris release
    These modules are signed by Pluris and pinned to the version of the server you're running. They appear in the Library with the bundled chip and cannot be edited; you can only clone them to make tenant variants.
    active
  • Tenant-local modules
    1 module · always enabled · signed by your tenant key
    Modules you author with the Custom Policy Wizard, clone from a bundled module, or upload as a bundle (.tar.gz with module.yaml). Listed as tenant in the Library.
    active
  • Imported module registries
    0 modules · phase 4 · manual fetch · per-source signing trust
    External module catalogues (community-maintained, vendor-published, or another tenant's exported bundle). Adding a registry doesn't import modules automatically — admin clicks Fetch, reviews the diff, and approves before anything reaches the Library.
    No imported registries yet.
Single Source of Truth UI (INV-U)
Every entry point that shows this concept mounts the same canonical editor with at most a context filter applied. See docs/UX_INVARIANTS.md §VII Concept Registry.
Pick module

Choose a module for this policy

Policy: — OS: any Scope: binding override
Currently picked
— Pluris default —
Falls back to the first bundled module that satisfies this policy.
No candidates loaded. Open this picker from a binding row or a Library row to populate.