grceng.academy
YAML lab 40 bonus XP

Encode decision rights and escalation

Start labRead the room

Objectives

Alder Quay's coordinator calls the annual review reminder an approval and sets the loss ceiling to the maximum the company could survive. Replace those assumptions with the mandatory charter requirements.

Fill the starter as a declarative governance record. Passing checks validates these fields, not actual committee behavior, independence, or delivery of notifications.

Mandatory charter and reporting requirements

policy approval: executive risk committee
policy review: every 12 months and after a material incident
access-change implementation RACI: responsible = access administrator; accountable = operations director
independent approval of privileged access: required
annual residual loss in loss units: appetite 100000; tolerance limit 120000; capacity 300000
forecast above appetite: notify board risk chair within 1 business day
board reporting: every 3 months; report KPI review completion and KRI unowned privileged accounts

Checks the server runs (5)

  • Use authorized approval and both review triggers
  • Separate performance, accountability, and independent approval
  • Keep the three annual loss boundaries distinct
  • Route an appetite breach within the required deadline
  • Report performance and exposure at the required cadence

Check names are all you see here: the expectations that decide pass or fail, and the reference solution, stay on the server.

Step-by-step hints

The guided walkthrough, in full. It is free: no XP cost, and it does not touch the paid hint ladder or the reveal gate.

  1. Step 1

    Authorize and refresh

    Find the delegated approval body, scheduled review period, and event that forces an earlier review. Keep the event requirement separate from the calendar field.

    Use authorized approval and both review triggers

  2. Step 2

    Map the work

    Identify the performer and the executive answerable for implementation. Then express the separate control preventing a requester from approving their own privilege.

    Separate performance, accountability, and independent approval

  3. Step 3

    Compare like with like

    Transfer the willingness, permitted variation, and maximum bearable exposure into separate numeric fields using the common annual measure.

    Keep the three annual loss boundaries distinct

  4. Step 4

    Build the exception route

    Identify which boundary triggers notification, who must receive it, and the deadline in the requested units. Do not wait for routine reporting.

    Route an appetite breach within the required deadline

  5. Step 5

    Make reporting decision-ready

    Use the recurring reporting cadence and classify the named delivery and exposure measures by purpose rather than percentage format.

    Report performance and exposure at the required cadence

Rules summary

  • XP on pass

    40 bonus XP the first time every check goes green.

  • Paid hints

    2 available. Each costs 25% of the lab XP (about 10 XP).

  • Reveal solution

    Scores 0 XP and unlocks only after 3 check runs.

  • Attempt cap

    60 check runs per learner. The runner warns you in the last 10.

  • Drafts

    Your editor content is saved in this browser, so a reload will not lose work.

  • Walkthrough

    Always free and never penalised: use it before spending a hint.