Use case

Customer-data update

Require context, data class, owner approval, and evidence before an agent changes customer records.

The Kernel is live. Company OS is preview. Enterprise is coming soon.

Receipt shape

effect: Create, update, export, or delete a customer record.
policy: Data class, business reason, requester, retention, and approval must be present.
approval: ESCALATE for sensitive fields, bulk scope, unclear owner, or missing business reason.

Systems touched

CRM, support desk, data catalog, approval channel

Side effect

Create, update, export, or delete a customer record.

Policy

Data class, business reason, requester, retention, and approval must be present.

Approval

ESCALATE for sensitive fields, bulk scope, unclear owner, or missing business reason.

Receipt

Data-action receipt with field class, policy, actor, approver, and target system.

Evidence export

EvidencePack export for customer-data review.

Turn this action into a reviewed HELM path.