Runtime · operational data · tools
Provide live state and perform the authorized action when the workflow requires it.
GitMir never holds the live values. When an agent asks whether a move is allowed, it passes the state in your own words and your own spelling — "PAID", "dirty", "open" — and gets back a verdict about the rule, not about the record. The refund, the cancellation, the ticket update all happen in your systems, under your permissions.
Read the current state of the record from your own system.
Ask GitMir whether that move is allowed from that state, and by which role.
Read the conditions the answer says are yours to check yourself.
Perform the action in your own system, if it clears.
Nothing you send in that question is stored — only the verdict is written to the usage log. One of the four possible answers is "no rule": the move exists and nothing in the product says who may make it or when. That is a finding to raise with a person, never a permission. GitMir has no write path into your systems at all.
See it on a real product.
Three models are published in full and open without an account. Ask one of them the question this page is about.