Config-as-Code Deep Dive

Kiket treats workspaces as code: workflows, boards, automations, and agent manifests all live in Git. This guide shows you how to bootstrap a repo quickly and keep production in sync.

Repository layout

.kiket/
├── workflows/
│   ├── marketing.yaml
│   └── onboarding.yaml
├── boards/
│   └── product-roadmap.yaml
├── templates/
│   └── incident.yml
├── agents/
│   └── planner.yml
└── extensions/
    └── make-ai/

• Workflows – YAML definitions with versioned transitions, approvals, and action hooks. Reference: KiketScript Workflows.
• Boards – Reusable board layouts linked to workflows.
• Templates – Issue templates with custom field defaults.
• Agents & extensions – Optional, but recommended so automation manifests live beside workflow changes.

Sync pipeline

1. Config repo – Connect under Settings → Configuration as Code. Each workspace maps to one repo + branch.
2. Loader – The Configuration Loader service validates definitions (unique IDs, compatible versions) before applying them. See Configuration Loader for error handling.
3. Jobs – ConfigurationSyncJob runs after each push. Use bundle exec rake configuration:sync locally to test.

Validation & promotion

• Run bundle exec rake configuration:validate in CI to block invalid YAML before merge.
• Tag releases (e.g., config/v2025.11.0) so rollbacks are a git revert.
• Use onboarding_hotspots / spotlight controllers to highlight new layouts/UI when definitions change (see Skill Matrix onboarding).

Useful references

• Configuration loader docs
• KiketScript reference
• Workflow repo seeding guide

Treat infra changes like code: branch, review, test, and deploy with the same rigor you apply to application code.