Risk tiers and confirmation controls

Risk tier model

Risk is determined by the operation effect, not by how confident a client or model appears. A simple-looking request can be consequential when it changes a customer record, sends a message, publishes content, deletes information, cancels a payment, or affects money.

Effect categories

• read retrieves approved tenant data without changing the source record.
• internal_write changes internal configuration or operational state.
• customer_record_write changes information associated with a contact, appointment, opportunity, or other customer record.
• destructive deletes, cancels, removes, revokes, or otherwise makes a hard-to-reverse change.
• external_send_publish communicates or publishes outside the private review surface.
• financial creates, changes, cancels, or reports an action with payment or monetary impact.

Fail-closed execution boundary

The Lead360 private integration gateway may describe operations across all risk tiers, but execute_operation checks the exact effect and reviewed adapter. Anything other than a supported read raises approval_required. The client cannot bypass this check with confirmation text, an extra Boolean, a different tenant field, or an alternate URL.

A permitted mutation must be prepared through the Lead360 product area that owns the record. That workflow should preserve the proposed values, exact target, evidence, actor, Piece or automation context where relevant, approval decision, apply receipt, and audit history.

Client responsibilities

1. Display the operation name, destination context, arguments, risk tier, and execution mode before use.
2. Do not convert an approval-required response into a direct request against an undocumented route.
3. Require a human review for consequential recommendations even when no technical write occurs.
4. Treat incomplete, stale, or conflicting evidence as a reason to stop.
5. Use idempotency and duplicate prevention in any later supported approval workflow.
6. Record the outcome without storing secrets or unnecessary customer content.

Preserve approval evidence

For a consequential proposal, retain the operation key, exact tenant-owned target, proposed values, evidence summary, risk tier, approving actor, decision time, and final apply receipt in the Lead360-controlled workflow. Do not treat a general instruction such as manage my campaigns as approval for every later send, publication, deletion, or financial action.

Approval must be specific enough for the reviewer to understand the customer or business impact. A material change to the target, values, audience, timing, amount, or destination requires a new review instead of reusing an earlier decision.

Expired or rejected proposals should remain unavailable for apply. Reviewers need a clear cancel path, and the integration owner should investigate repeated attempts to submit the same blocked effect through different operation names or clients.