Triage: Eliminate / Automate / Delegate

Purpose

Decide eliminate vs automate vs delegate for ranked impact constraints, in that order, in writing. Tag cause layers (dE / dK / dI) and route each tag.

Inputs

• streamlit/data/cost_of_delay.yaml and ai_opportunities.yaml.
• Skill Eliminate/Automate/Delegate Triage → Cause tags / Routes.
• Template streamlit/data/action_register.yaml.

Steps

1. Open streamlit/data/action_register.yaml. One row per ranked constraint, impact order. Fill eliminate first; automate only if eliminate is written no; delegate only if automate cannot encode the judgment.
2. The AI matrix may inform where automate or delegate could apply. It does not skip eliminate and it is not an agent backlog.
3. Automate shape: one Lambda + one Guardrail (policy / allow-list / human approval — name the check, not a product).
4. Tag cause layers on each row (multi-tag allowed). Skill → Cause tags:
   - dE environment (tool, process, incentive, data, time, authority)
   - dK knowledge/skill (trainable / selectable)
   - dI individual (selection, capacity, motivation)
   "Knows the right move, environment punishes it" stays dE, not dK.
5. Route per tag (skill → Routes): dE+eliminate → drop; dE+process/tooling → process/tooling (not AI SDLC); dE+automate/delegate → AI SDLC candidate; dK → Team Upskill Engine input (stage, clock, unit, n, role); dI → staffing. Do not author TUE modules.
6. Escalate #1 if neither eliminate nor automate works — flow redesign. Do not implement the Lambda in this activity.

Done when

• action_register.yaml has decision, cause tags, route, and evidence (clock, unit, n, role) for #1 and every ranked row you touched.
• No dK row claims a finished curriculum. No dE process/tooling row is labeled AI SDLC unless automate or delegate was chosen.

Feeds

Tell the Data Story (publish this register — do not re-classify).