Policy pack

Procurement Thresholds

Purchase orders and contracts by amount band: within the band they proceed, above it an approver decides.

Key
procurement_thresholds
Version
procurement_thresholds-v1
Rules
6
Domain
PROCUREMENT

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. Escalate an amount in a currency the template does not list

    priority 1000

    proc-currency-unlisted · PROCUREMENT

    When
    • context.currency not in ["USD"]
    Then

    ESCALATE → ESCALATE · elevated · SLA 60 min

    An amount with no currency, or in a currency without limits, cannot be compared with a limit, so a person decides it.

  2. Escalate a purchase order above its band

    priority 200

    proc-purchase-order-above-band · PROCUREMENT

    When
    • transaction_type = "purchase_order"
    • amount > 5000
    Then

    ESCALATE → ESCALATE · elevated · SLA 240 min

    A purchase order above the starter band of 5000 needs an approver. Replace the band with your policy's.

  3. Escalate a contract above its band

    priority 200

    proc-contract-above-band · PROCUREMENT

    When
    • transaction_type = "contract"
    • amount > 1000
    Then

    ESCALATE → ESCALATE · elevated · SLA 240 min

    A contract above the starter band of 1000 needs an approver. Replace the band with your policy's.

  4. A purchase order within its band

    priority 100

    proc-purchase-order-within-band · PROCUREMENT

    When
    • transaction_type = "purchase_order"
    • amount > 0
    • amount ≤ 5000
    Then

    AUTO_APPROVE → APPROVE

    A purchase order at or under the starter band of 5000 proceeds.

  5. A contract within its band

    priority 100

    proc-contract-within-band · PROCUREMENT

    When
    • transaction_type = "contract"
    • amount > 0
    • amount ≤ 1000
    Then

    AUTO_APPROVE → APPROVE

    A contract at or under the starter band of 1000 proceeds.

  6. Escalate every other procurement action

    priority 0

    proc-out-of-policy · PROCUREMENT

    When
      Then

      ESCALATE → ESCALATE · elevated · SLA 240 min

      An unlisted action, or one with no amount or a non-positive amount, is not within any band: an approver decides.

    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/mcp 0.4.0 does not carry this pack: the hosted protocol decides a hosted gateway's requests under it.

    decionis_evaluate arguments

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

    In a hosted evaluate-decision request

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

    Workflow keys that resolve to this pack: procurement_thresholds.

    What its rules read

    amount, transaction_type are fields of the request itself, not of its context. A value put only in the context is discarded, and the evaluator holds the decision as an ESCALATE rather than decide without it. @decionis/mcp puts the whole payload in the context, so a payload that carries amount, transaction_type is held.

    • amountrequest
    • context.currency
    • transaction_typerequest

    Signals it maps

    • auto_clear_ratiofinance_workflow
    • escalation_ratiofinance_workflow
    • above_band_countfinance_workflow