Domain packs
A domain pack bundles the things an engagement needs for a particular kind of work — some or all of: a capability set, standards content, deliverable templates, an engagement role, and seed data. Everything in a pack is content, never code.
The packs that ship
Section titled “The packs that ship”Two are active by default:
- AI-readiness pack — the flagship. It carries the deliverable template that turns the agentic-readiness assessment into a client-facing report. (The assessment engine is always-on core code — the pack is the report content around it.)
- General IT baseline pack — a small, general starting set for IT transformation work.
Additional packs may be present in a given deployment and switched on for a particular target domain.
How a pack changes an engagement
Section titled “How a pack changes an engagement”An active pack can:
- seed the capability model with a starting structure,
- add deliverable templates to the Phase 4 library,
- add an engagement role.
A pack never removes governance or changes the loop — it changes the content you start from, not how eavantage works. A pack also isn’t how you add a new entity type — for that, see The metamodel.
Choosing active packs
Section titled “Choosing active packs”Which packs are active is a deployment-level setting (an environment variable), not something you change per engagement. It’s one target domain per deployment. If you need a different pack active, talk to whoever runs the deployment.