Pick the pack that matches your sector, role, and jurisdiction.
A KYE Starter Pack™ is a turn-key bundle for a specific buyer context. It activates the right rule packs, sector packs, dictionaries, comms templates, dashboard widgets, and pre-configured purposes for that context — through the canonical KYE Onboarding Agent™. Every pack resolves its bundle by reference against the live canonical registries; nothing is parallel-defined. Ten packs at launch, covering the highest-value buyer contexts KYE Protocol™ supports.
One pack → one activation flow → one signed Evidence Pack™.
- 1. Pick a pack. Pick the pack that matches your sector, role, and jurisdiction. Each pack lists its target audience, prerequisites, bundled artefacts, and time-to-value estimate.
- 2. Validate prerequisites. Sales-assist confirms every prerequisite (signed SOW, SSO configured, regulator approvals on file). Without them the pack does not activate.
- 3. Activate via the Onboarding Agent. The canonical KYE Onboarding Agent™ (constitution §22) provisions the tenant, binds the bundle, runs shadow-mode, ingests the first observed action, and seals the first Evidence Pack™.
- 4. Kickoff brief delivered. A signed kickoff brief lands in your inbox. The pack is now in steady-state operation.
Pick the pack that matches your buyer context.
Every pack resolves its bundle by reference against the canonical KYE Protocol™ registries (rule packs, sector packs, dictionaries, comms templates, GovernedUI modules, data-purpose terms). The CI gate starter-pack-canonical blocks merge on any unresolved FK; what you see here is what activates in your tenant.
Every pack lists its full bundle (rule packs, sector packs, dictionaries, comms templates, dashboard widgets, pre-configured purposes), prerequisites, and pricing SKU in its canonical manifest under internal<slug>/manifest.json — mirrored to public/examples/starter-packs/<slug>.json. Disclosed to qualified buyers at sales-assist time.
Every pack is a reference, never a re-definition.
- Schema.
kye.starter_pack.v1— six FK arrays insidebundles{}, onepricing_sku_ref, oneactivation_flow_ref. No parallel content. - Rule packs. Resolve against the canonical rule-pack manifest (§29 Profiles-Lite).
- Sector packs. Resolve against the canonical sector-pack manifest (§29).
- Dictionaries. Resolve against any
dictionary_iddeclared underinternal. - Comms templates. Resolve against the canonical comms manifest (§38 Comms Rail).
- Dashboard widgets. Resolve against the canonical GovernedUI manifest (§36).
- Pre-configured purposes. Resolve against the canonical data-purpose dictionary.
- Pricing SKU. Resolves against the canonical SKU catalogue (§26 Commercial Rail).
- Activation flow. Delegated to the canonical KYE Onboarding Agent™ (§22) — no parallel onboarding rail.
Constitution §22 §13 (adopted 2026-05-30) registers this discipline. The CI gate starter-pack-canonical is blocking.