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

Knowledge source reference

Engineering Task Routing

First route for using the Valdris skill on any engineering task in this repo or a commissioned repo.

Canonical pathknowledge/playbooks/engineering-task-routing.mdRevision69bab1cInspect source

Start

Use one skill as the entrypoint. The skill should read this vault index first, then open only the playbook or concept needed for the current task.

Route

  1. If the request changes code, architecture, debugging, refactoring, or cross-file behavior, use GitNexus Code Intelligence.
  2. If the request could affect user-facing or production behavior, use Production Readiness 13 Layers.
  3. If the request is about event emission, live telemetry, Red Zone, self-heal, or completion, read Connector Event Runtime.
  4. If the request is docs-only, still update this vault when the docs change stable routing knowledge.

Proof

Prefer commands from docs/Validation Commands.md, project-adapter.json, or package.json. For this harness repo, the normal proof stack is:

npm run knowledge:gate
npm run typecheck
npm run dependency:audit
npm run build
npm run verify:release-privacy
npm run privacy:release
npm run code-intelligence:scan
npm run code-intelligence:gate
npm run verify:harness

This routing playbook names the lane-focused subset. Root AGENTS.md remains the canonical release sequence and must also pass before a repository completion claim.

Handoff

Final answers should name the lane, proof commands, artifact paths, skipped nodes with reasons, and open risks. Use Proof-First Harness as the final-answer standard.