Your domain

customer-refunds

The reusable operational contract this workspace runs on, its actions, lifecycle, the agents that propose against it, and the evidence it produces.

2 of 10 domains New domain
Submitted3420before executor ran
Allowed3310authorized
Blocked32withheld
Statusidlelast seen 13 days ago

Governance posture

The mode the runtime honors for this domain. Shadow records decisions as advisory, nothing is blocked or held. Enforce makes blocks and approval-holds binding. Flip deliberately; the change takes effect on the next decision.

Shadow
Shadow · current

customer-refunds

Entity: Order · active · governing since Jul 7, 2026

Edit YAML Open Build Open evidence

Governance

How KIFF decides this domain, a projection of your code contract. The knobs below (allowed states, approval, risk) are what the runtime evaluates before an action runs. Your domain is executable software in your codebase, which is the record: edit the contract there, then re-activate. Enforcement posture (shadow / enforce) is operator-controlled, see Activity.

Governed actions

  • ISSUE_REFUND high allowed in: paid approval: support_lead
  • CANCEL_ORDER medium allowed in: created

Is what I'm governing real?

Each action reconciled against what the runtime has actually seen, where its side effect runs, and whether the gate has been exercised.

  • ISSUE_REFUND Unbacked
    No executor bound · no executor, this action cannot be governed until the contract binds one
  • CANCEL_ORDER Unbacked
    No executor bound · no executor, this action cannot be governed until the contract binds one

KIFF attests the gate, the decisions it made and the receipts it recorded. For actions that run in your code, the side effect itself runs in your codebase, which is the record; its receipts here are evidence the gate was consulted, not proof of the side effect. Confirm the codebase side in your repo with kiff verify.

Lifecycle

States: created, paid, refunded, cancelled

  • created, payment_captured → paid
  • paid, refund_issued → refunded

Agents

Connect an agent

Recently observed proposing identities, derived from real decisions, not a configured roster.

  • support-refund-agent actor 284 observed operations

Delete this domain

Removes customer-refunds and its configuration. Its recorded evidence (decisions, receipts) is kept as audit. This can't be undone.