Application governance router SOP

Purpose

Give anyone with a governance question a single starting point, so they reach the right skill without knowing the kit's tool names, and so every result comes back with its reasoning and its open decisions.

Scope

Applies to requests about the application portfolio, ITAM maturity, framework mapping, access, AI systems, and device lifecycle. It routes to the kit's other skills and does not do their work itself. It does not cover requests outside the kit; it says so.

Roles

• Requester — states the goal, supplies the data, and makes the decisions.
• Router — the agent or person who picks the skill, runs it, and reports.
• Decision owner — whoever the chosen skill names for each Decision needed: point.

Frequency

Run on demand, whenever a governance question arrives without a chosen tool.

Steps

1. Confirm what the requester is deciding and by when XW-027
2. Pick the skill from the routing table and say why; if two fit, run the one closest to the decision first XW-027
3. Name the data the skill needs and ask for it, or offer the demo estate XW-001
4. Load the chosen skill and follow its steps and output rules XW-025
5. Offer any second skill the result points to; run it only if the requester agrees XW-027
6. Report the answer first, then the reasoning, then the open decisions XW-025
7. Hand the requester the routing log row to record, since the router is read-only XW-020

Evidence to retain

• The routing log: date, request, skill chosen, reason, follow-up, and open decisions.
• The chosen skill's output for each run.

Related

• Governance framework crosswalk (crosswalk)
• Stand up a governance program (program-setup)
• ITAM maturity check (itam-maturity)
• Application rationalization (rationalization)
• Access review pack (access-review)
• AI system intake and risk tiering (ai-intake)
• Hardware lifecycle check (hardware-lifecycle)
• Certification study coach (cert-prep)