U01689 Human Approval Routing For Education Support Services

Metadata

• Skill ID: 1689
• Skill Name: u01689-human-approval-routing-for-education-support-services
• Domain: education support services
• Domain Slug: education-support-services
• Archetype: generalist-engine
• Core Method: human approval routing
• Primary Artifact: human-approval-routing-artifact-education-support-services
• Routing Tag: education-support-services:generalist-engine
• Feature Flag: skill_01689_human-approval-routing
• Release Cycles: 2

Allowed Tools

• read, write, edit for contract maintenance, runbook updates, and handoff documentation.
• exec, process for deterministic execution, validation suites, and regression checks.
• web_search, web_fetch only when fresh external evidence is required for claims/evidence inputs.
• Use messaging or publishing tools only after policy approval gates are satisfied.

Inputs (formatted)

Outputs (formatted)

Guidelines

1. Validate required inputs before execution and reject non-conforming payloads early.
2. Run human approval routing with deterministic settings and trace capture enabled.
3. Produce human-approval-routing-artifact-education-support-services outputs in machine-readable form for orchestrator/operator use.
4. Keep routing aligned with education-support-services:generalist-engine and include approval context.
5. Tune thresholds incrementally based on observed KPI drift and incident learnings.

Musts

• Enforce approval gates: policy-constraint-check, human-approval-router.
• Apply retry policy: maxAttempts=4, baseDelayMs=750, backoff=exponential.
• Run validation suites before release: unit, integration, simulation, regression-baseline.
• Fail closed when validation gates fail and execute rollback strategy rollback-to-last-stable-baseline.
• Preserve reproducible evidence artifacts for audits and downstream handoff.

Targets (day/week/month operating cadence)

• Day: Validate new upstream signals, execute deterministic run, and hand off outputs for active decisions.
• Week: Review KPI focus (cycle time reduction, throughput gain, automation leverage in education support services), failure trends, and approval/retry performance.
• Month: Re-baseline deterministic expectations, confirm policy alignment, and refresh feature-flag/rollout posture.

Common Actions

1. Intake Check: Confirm all required signals are present and schema-valid.
2. Core Execution: Run the capability pipeline and generate report + scorecard artifacts.
3. Gate Review: Evaluate validation and approval gates before publish-level handoff.
4. Recovery: Retry transient failures, then rollback to stable baseline on persistent errors.
5. Handoff: Send artifacts with risk/confidence metadata and downstream routing hints.

External Tool Calls Needed

• None required by default.
• If external systems are introduced for a run, record the dependency, timeout budget, and retry behavior in execution notes.

Validation & Handoff

Validation Gates

• (none declared)

Validation Suites

• unit
• integration
• simulation
• regression-baseline

Failure Handling

• (none declared)

Handoff Contract

• Produces: (none declared)
• Consumes: (none declared)
• Downstream Hint: (none declared)