Program configuration & batches
This hub groups process documentation for turning a GrowthKit program configuration into confirmed settings, batches (learning groups), and publish / lifecycle behaviour on the backend. Use it when you work across confirmation, handover, publish, and batch locking.
All pages linked here are English for a multicultural team.
What belongs in this category
| Theme | What it covers |
|---|---|
| Configuration confirmation | User confirms the program configuration; configuration is persisted as confirmed; initial batches may be created when none exist. |
| Configuration handover | Sales / configuration owner hands configuration to Team Learning for operational setup. |
| Publish batch | Publishing a batch (checks, API, side effects). |
| Related automation | Auto batch lock and UI locking rules that affect what can still be edited. |
Detailed process flows (generated)
YAML manifests in documentation/process-registry/ feed scripts/generate-process-docs.js, which generates these pages:
| Document | Process ID |
|---|---|
| Program configuration confirmation | PROGRAM-CONFIGURATION-CONFIRMATION |
| Program configuration handover | PROGRAM-CONFIGURATION-HANDOVER |
| Publish batch | PUBLISH-BATCH |
Related processes (top-level in Processes)
- Auto batch lock — automatic locking around batch lifecycle.
Features and journeys
- Batches (GrowthKit) — overview
- Create/Edit Batch — feature reference
- Create/Edit Batch — Team Learning journey
Systems and how-to
- Batch UI locking — frontend behaviour when a batch is published or locked.
- Setup batch (Team Learning) — operational checklist.
Placeholders
| Topic | Status |
|---|---|
| Additional YAML processes (e.g. batch draft save, survey autosave on batch, unpublish, coach date request) | PLACEHOLDER — planned. New manifests under process-registry/ will appear in Detailed Process Documentation once added and generated. |