Skip to content
PLUR Docs

Knowledge Packs

A Knowledge Pack is a curated, versioned bundle of engrams that you can install and uninstall like a software package. Packs are how PLUR knowledge travels between people, teams, and machines.

When you’d use a pack

Section titled “When you’d use a pack”
  • Team onboarding: ship every new engineer the team’s “how we deploy” pack.
  • Open source distribution: publish a pack of conventions for your library.
  • Cross-project replay: bundle the lessons from one project and replay them in another.
  • Bench mark sets: share a calibrated pack to compare memory-driven agent performance.

Anatomy

Section titled “Anatomy”

A pack is a directory with a manifest and the engrams it ships:

my-deploy-pack/
├── manifest.yaml
├── engrams/
│   ├── ENG-PACK-001.yaml
│   ├── ENG-PACK-002.yaml
│   └── ...
└── README.md

manifest.yaml:

name:        my-deploy-pack
version:     1.2.0
description: Deploy conventions for the platform team
author:      platform@acme.com
license:     Apache-2.0
target_scope: group:acme/platform
engrams:     ./engrams/*.yaml
integrity:   sha256:9c4d...

The integrity hash is computed at export and verified on install — installing a pack from an untrusted source still gets you a tamper check.

Install a pack

Section titled “Install a pack”
Terminal window
plur packs install ./my-deploy-pack
plur packs install https://packs.plur.ai/community/python-style-1.0.0
plur packs install @plur-ai/datacore-conventions

The pack’s engrams enter your store under the pack’s target_scope. Conflicts (same id already present) are flagged for review — install never silently overwrites.

List and remove

Section titled “List and remove”
Terminal window
plur packs list
plur packs uninstall my-deploy-pack

Uninstall removes the engrams that came from the pack. Activation accumulated while installed is preserved in history but the engrams are no longer eligible for injection.

Export your own

Section titled “Export your own”
Terminal window
plur packs export \
  --scope project:my-app \
  --out ./my-app-pack-1.0.0 \
  --version 1.0.0

This collects every engram in the named scope, writes the manifest, computes the integrity hash, and emits a directory you can commit, zip, or publish to a registry.

Discovery

Section titled “Discovery”
Terminal window
plur packs discover                    # community packs
plur packs preview <pack-url>          # show contents before install

Discovery hits a small static index. PLUR doesn’t ship a centralised pack server by default — packs are just signed directories. You can publish them on GitHub Releases, S3, IPFS, or your internal artifact store.

Team packs (Enterprise)

Section titled “Team packs (Enterprise)”

In PLUR Enterprise, packs are first-class: the admin dashboard can push a pack to every team member’s local PLUR, version-bumped together, with audit trail. See Enterprise admin.

Next: Sync →