RAES Environment Packs

RAES environment packs give a scenario a standard shape. This package defines that shape and gives you the tools to build, check, and ship a pack.

A pack holds the declarative content for one reference environment: the scenario start state, its assets, and the record of where the content came from. Authors build packs; consumers validate a pack before they trust it. Because the format and the tools ship together in one installable package, you validate a pack against the same version you built it against.

This repository defines and validates the format, publishes the first-party kit collection, and hosts major example packs. Third-party catalogs use the same package and contracts.

Start here

New to environment packs? The quickstart scaffolds a pack and validates it in about five minutes.

pip install raes-env-packs

Choose your route

• Author a pack — scaffold one with the pack tools and plan it against the golden-readiness checklist, then add common infrastructure from reusable kits. The defensive-tooling composition is a verified multi-kit example. To keep one scenario unchanged while varying participant guidance, follow the two-audience bundle walkthrough.

• Use an MCP host — search, inspect, and author packs with explicit review before preparation and writes.

• Consume a pack — check a pack you received with raes-pack-check, or call the validate_pack API, before you trust its bytes. To install and verify a signed release, see distribute and verify.

• Publish a catalog — render a machine-readable catalog projection with raes-pack-catalog so a static catalog, browser, or Hub can list your packs.

• Understand the format — read what a pack is and the pack reference.

• Know the limits — see what this is and is not.

• Contribute — start from the contributing guide.