Skill orientation

Use this panel to select and sequence the skill. The canonical source follows below.

Purpose: Classify an authorized request and select the smallest valid route.
Category and sequence: Work type; sequence 1
Primary use: Intake, Ambiguous, Audit, Greenfield
Required gates: Goal, Skill Registry, Classification
Conditional gates: code-intelligence, foundation, and production for every non-docs audit or routed delivery request; controlled assurance docs require the lightweight Foundation review path
Red Zone triggers: No skill-specific triggers are declared
Next route: Return to the active lifecycle route
Source identifier: skills/valdris-intake-route/SKILL.md

Canonical pathskills/valdris-intake-route/SKILL.mdRevision69bab1cInspect source

Valdris Intake And Route

Use the project adapter as the repo-specific source of truth. Prefer project-adapter.json, then .valdris-harness/project-adapter.json.

When the deterministic router is installed, start with node scripts/route-request.mjs --repo . --request "<request>" (or the .valdris-harness/scripts/ path for a nested pack), then review its conservative output rather than hand-authoring an unbound route.

Route

Capture the user outcome, affected users, constraints, exclusions, and verifiable stopping condition.
Classify the workload against controls/workload-taxonomy.v1.json, write run/workload-classification.json, and bind its digest to the authorized intake and route. The classification gate must pass before delivery relies on it.
Classify the work as bug, feature, architecture/refactor, security, platform/release, GenAI, audit, incident, or docs-only.
Select a stakes profile: prototype, production, enterprise, or regulated, then derive the minimum assurance tier and capability proof expected from the combined workload and stakes profiles instead of treating either profile as a label.
Decide whether Layer 0 foundation assurance is required. Every non-docs route requires it before implementation. Ordinary README/copy docs may skip it; controlled security, privacy, compliance, release, incident, AI-safety, or financial policy documents use the lightweight product/requirements/ownership-risk Foundation review path and accountable human review.
Classify the 13 canonical production assurance domains initially as required, potentially-affected, or not-applicable. They are the current shared baseline, not an exhaustive list of literal runtime layers. Resolve every potentially-affected domain before final proof; never omit one silently.
Detect GenAI impact: models, prompts, retrieval, agents, tools, memory, evals, or AI telemetry. Treat asynchronous orchestration as cross-cutting behavior whose effects must be assessed across applicable domains, not as a fourteenth domain.
Identify Red Zone actions before tools or edits are used.
Select one primary Valdris skill and only the supporting skills needed for proof and handoff.

Use phase transitions for large work: intake may be primary first, delivery becomes primary after the route and goal are accepted, and proof-handoff becomes primary at the finish line. Break ties by explicit outcome, highest consequential risk, artifact being changed, then the narrowest match.

Artifacts

Write or update:

run/intake.json
run/workload-classification.json
run/route.json
goal/goal.json for multi-checkpoint work

Advance checkpoints and conditions with goal-transition.mjs and the current expected revision so stale agents cannot silently overwrite newer goal state.

The goal pins the intake request and initial route digests. Do not rewrite intake/route to make gates disappear; open a reviewed new run when the authorized request or initial route must change.

The router assigns a conservative immutable execution budget from task type and effective tier. Do not increase that budget in place; a materially larger scope requires a new reviewed run.

Ask a question only when the answer changes scope, architecture, authority, or proof. Otherwise record a conservative assumption and continue.

Do not claim Live Run telemetry unless real connector events exist.