Settings Control Plane
The settings control plane manages configuration for every subsystem as versioned, validated records so changes are auditable and reversible.
Configuration Model
Configuration is stored as structured records rather than flat files. Each setting has a schema, an owning subsystem and a version. Reads always resolve to a concrete, validated value; there are no undefined defaults at runtime.
- 01resolve effective scope
System, tenant and environment values resolve to one concrete setting.
- 02validate before write
The setting schema rejects invalid configuration before it can affect a subsystem.
- 03create immutable version
A successful write records its actor, timestamp and versioned value.
- 04retain rollback path
A prior version can be restored atomically without losing history.
governed outcome
VERSIONED
Validated value · author recorded · rollback available
Scopes and Precedence
Settings resolve across three scopes, from lowest to highest precedence:
- System — platform-wide defaults shipped with KAVACH.
- Tenant — overrides for an individual organization.
- Environment — per-environment overrides such as staging or production.
Validation
Every write is validated against the setting's schema before it is accepted. Invalid configuration is rejected at write time, never at the point of use, so a bad value cannot silently degrade a running subsystem.
Fail closed
If configuration cannot be resolved or validated, the subsystem refuses to start rather than falling back to an unknown state.Versioning and Rollback
Each change produces a new immutable version with an author and timestamp. Rollback restores a prior version atomically, and the full history is available for audit.
Example
{
"key": "evaluation.parallelism",
"scope": "environment",
"environment": "production",
"value": 16,
"version": 7,
"updated_by": "ops@acme.com",
"updated_at": "2026-05-02T10:14:00Z"
}