DecionisDevelopers
Workflow overlay

Ops Customer-Impact Triage

Track and govern customer-impacting operations decisions with SLA ownership and reminder loops.

Key
ops_customer_impact
Version
ops_customer_impact-v1
Rules
2
Domain
CUSTOMER_IMPACT_OPERATIONS
Every packHow a pack decides

Rules, in the order the evaluator tries them

Highest priority first. The first rule whose conditions all hold decides; with none, the decision is a REVIEW.

  1. Evidence completeness gate

    priority 120

    evidence-required · CUSTOMER_IMPACT_OPERATIONS

    When
    • evidence.attachments < 1
    Then

    REQUEST_INFO → REVIEW · elevated · SLA 45 min

    Do not finalize high-consequence decisions without evidence.

  2. Owner and escalation accountability

    priority 100

    owner-accountability · CUSTOMER_IMPACT_OPERATIONS

    When
    • intake.owner exists
    Then

    REQUIRE_REVIEW → REVIEW · routine · SLA 60 min

    Every routed decision must have a named accountable owner.

Evaluate under it

Locally, with @decionis/mcp: the payload becomes the request's context, and its action the decision type. On the hosted protocol, once the bundle is stored for your organization, name vertical_pack, policy_version and require_exact_policy_version: true.

decionis_evaluate arguments

{ "policy_pack": "ops_customer_impact", "payload": { "action": "<decision type>" } }

In a hosted evaluate-decision request

"vertical_pack": "ops_customer_impact",
"policy_version": "ops_customer_impact-v1",
"require_exact_policy_version": true

Workflow keys that resolve to this pack: ops_customer_impact.

What its rules read

Every fact below comes from the request's context.

  • evidence.attachments
  • intake.owner

Signals it maps

  • decision_cycle_countops_customer_impact_workflow
  • escalation_ratioops_customer_impact_workflow
  • evidence_completeness_rateops_customer_impact_workflow