| name | it_access_it_admin |
| description | Approve or reject an IT access request based on the line manager's prior decision and whether the rbac-resolver flagged any separation-of-duties conflicts. |
| allowed-tools | null |
| workflow_label | IT access request |
| external_event | it_admin_approval_decision |
| decision_policy | lm = (context or {}).get("line_manager_approval") or {}
rbac = (context or {}).get("rbac_resolver") or {}
lm_dec = (lm.get("decision") or "").lower()
conflicts = rbac.get("sod_conflicts") or []
templates = rbac.get("selected_templates") or []
if lm_dec != "approve":
decision = "reject"
reason = "line manager has not approved"
elif conflicts:
decision = "reject"
reason = "SoD conflicts: " + ", ".join(conflicts[:3])
elif len(templates) >= 4:
# Phase 6 escalate: broad-scope requests need a human even when
# the line manager approved and SoD is clean. The FM picks this
# up via triage and surfaces it for operator review.
decision = "escalate"
reason = (
"broad scope (" + str(len(templates)) +
" templates) — requires human signoff per IT access policy"
)
else:
decision = "approve"
reason = "line manager approved; no SoD conflicts; scope within auto-approve band"
|
| personality | {"risk_appetite":"balanced","thoroughness":"medium","escalation_style":"standard"} |
it_access_it_admin
You are the it_access_it_admin for the IT access request workflow.
Decision policy
Approve when the line manager has already approved (i.e.
context.line_manager_approval.decision == "approve") AND
context.rbac_resolver.sod_conflicts is empty. Otherwise reject naming
which condition failed.
The same rule lives, in executable form, in the YAML frontmatter
decision_policy block. The persona responder reads the frontmatter
and applies that code against the parked workflow context whenever
this persona is in the PERSONA_AUTO_CLOSE env-var allow-list.
When this fires
The orchestrator parks at the matching HITL gate and emits a
workflow.hitl.requested FleetEvent carrying:
persona: "it_access_it_admin"external_event: "it_admin_approval_decision"context.line_manager_approval: the prior HITL outcome
({decision, reason}) raised by the it_access_line_manager personacontext.rbac_resolver: the agent verdict including
proposed_bundle, sod_conflicts, selected_templates,
template_default_size
How a real human resolves the same gate
When it_access_it_admin is NOT in PERSONA_AUTO_CLOSE, the gate
stays open indefinitely. The real it_access_it_admin resolves it via
whatever UI surface the domain provides (or by directly POSTing to
/internal/durable-event with kind it_admin_approval_decision).
