Skip to harness content
Valdris V markValdris.ai
Open navigation
Secure intake
Deploy first, Build when scoped
Request a delivery review
Open technical reference map

Lifecycle skill 02

Route and Control the Goal

Create the durable goal, classify the request, and freeze the authorized route.

valdris-route-goalOwning system: Routing And Goal Control

Skill orientation

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

Purpose
Create the durable goal, classify the request, and freeze the authorized route.
Category and sequence
Lifecycle; sequence 2
Primary use
Create Deterministic Intake And Route, Create Or Inspect A Durable Goal, Resolve Lifecycle Ambiguity
Required gates
Intake, Classification, Route, Goal, Skill Registry
Conditional gates
No additional conditional gates are declared
Red Zone triggers
No skill-specific triggers are declared
Next route
Assure
Source identifier
skills/valdris-route-goal/SKILL.md
Canonical pathskills/valdris-route-goal/SKILL.mdRevision69bab1cInspect source

Valdris Route And Goal

This skill owns Routing and Goal Control. It decides what Valdris must do and what evidence will stop the loop. It never hand-writes a weaker route to avoid a gate.

Deterministic flow

  1. Run the lifecycle router and require its commissioning decision to report commissioned: true with commissioningReason: adapter-current. The router treats .valdris-harness/project-adapter.json as authoritative when present and otherwise accepts a current root project-adapter.json for a directly opened pack root. If the reason is adapter-trust-unready, stop and require the operator to configure or correct protected UASH_REVIEW_TRUST_SHA256; the pack itself must not be refreshed. If the selected adapter or its bound skill registry and routing projection are absent, invalid, incomplete, or stale, stop and hand off to $valdris-commission.

  2. Capture the exact requested outcome, exclusions, affected users, environment, operator, authority boundary, and measurable stopping condition. Ask only when an answer changes scope, architecture, authority, or proof.

  3. Run the deterministic router from the target root. Use .valdris-harness/scripts/route-request.mjs when commissionedAdapter is .valdris-harness/project-adapter.json; use scripts/route-request.mjs when it is the root project-adapter.json:

    node <discovered-pack-path>/scripts/route-request.mjs --repo . --profile <profile> --actor "<owner>" --request "<request>"

  4. Validate run/intake.json, run/workload-classification.json, run/route.json, and goal/goal.json with the intake, classification, route, goal, and skill-registry gates.

  5. Confirm the route contains exactly three work phases: intake-route, delivery, and proof-handoff. Confirm it selects one delivery primary from the eight work-type skills and no more than four supporting skills.

  6. Confirm the route keeps Layer 0 plus the 13 production assurance domains authoritative. AI, async workflow, orchestration, and specialized products remain cross-cutting concerns or domain packs, never Layer 14.

  7. Review material unknowns, Red Zone actions, attempt/tool/token/cost/wall-clock budgets, forbidden sequences, checkpoints, and stopping conditions. Do not increase budgets or rewrite the initial route in place; a material scope change starts a new reviewed run.

Completion criterion

This stage is complete only when all four artifacts exist, their digests bind to one request/run/commit/environment, every gate above passes, the route's work-skill choice matches the deterministic classifier, and the operator can state what ends the goal loop.

If classification or authority is unresolved, stay here. If the route is valid, hand off to $valdris-assure.