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

Source setup

Verify, commission, and route

The public package is a release candidate. Install from the canonical repository, verify the checkout, commission a target repository, review the generated pack, and then route work.

01

Verify the source

git clone https://github.com/nickcarmonadigital/valdris-sdlc-harness.git
cd valdris-sdlc-harness
git checkout --detach 69bab1c945a989cc821f4807d9ab02b62773698a
test "$(git rev-parse HEAD)" = "69bab1c945a989cc821f4807d9ab02b62773698a"
node -e 'const p=require("./package.json"); if (p.version !== "0.9.0-rc.1") throw new Error("Unexpected package version: " + p.version)'
npm ci
npm run typecheck
npm run build
npm run verify:harness

This verifies a development checkout. It is not authoritative release proof.

02

Commission a target repository

npm run commission -- \
  --repo /path/to/repo \
  --project-name "Example" \
  --out /path/to/repo/.valdris-harness \
  --yes

Review and commit the generated pack before routing work.

03

Route the first request

cd /path/to/repo
node .valdris-harness/scripts/route-request.mjs \
  --repo . \
  --profile enterprise \
  --actor "owner" \
  --request "Build a secure account settings page."

The router creates intake, classification, route, and goal artifacts. It does not run a coding agent or approve work.

Proof boundary

A local build and harness verification establish development evidence. Authoritative release remains blocked until a commissioned target supplies trusted provider keys, protected execution, signed receipts, and external state that cannot be silently rolled back.