Skip to harness content

Public mechanism reference / v0.9 release candidate

Valdris SDLC Harness

repository-level SDLC assurance harness for AI coding agents

Valdris installs repository controls, routes work, records external coding-agent activity as evidence, checks required proof, and blocks unsupported completion.

Controlled technical English is an authoring target. Formal ASD-STE100 conformance is not verified. The published source is a release candidate, not a tagged stable release.

Foundation
Layer 0
Production assurance
13 domains
Lifecycle
7 skills
Work types
8 skills
Complete catalog
15 skills
01

What the harness actually does

The harness surrounds external coding agents with repository controls, durable state, typed evidence, and completion gates.

01

Commission the repository

Generate repository-specific controls, a project adapter, coding-agent entry points, commands, authority boundaries, and proof obligations.

02

Capture and classify the request

Bind the authorized request, operator, environment, scope, exclusions, workload class, risk, and assurance requirement.

03

Freeze the route and durable goal

Select one primary work type, required supporting work, checkpoints, stop rules, and the source revision. Later evidence cannot weaken the route.

04

Resolve Layer 0

Check the foundation: intended workload, required capabilities, selected profile, acceptance rules, ownership, and proof contract.

05

Connect external coding work

Claude Code, Codex, or Hermes performs implementation. Runtime adapters normalize allowed events and watched artifacts into evidence.

06

Evaluate applicable assurance

Resolve the 13 production domains, active cross-cutting packs, gates, explicit skips, technical proof, and human-only Red Zone decisions.

07

Review, packet, and hand off

Freeze evidence for separated review, validate the run packet, state the supported assurance level, and preserve unresolved work instead of claiming unsupported completion.

02

Source setup

Valdris is source-installed. No npm package, marketplace listing, or stable tagged release is claimed.

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.

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.

Read the complete commissioning and first-route procedure →
03

Seven lifecycle skills

Lifecycle skills select the harness system that owns the current operation. Their order is deterministic.

Lifecycle 01valdris-commission

Commission

Install repository-specific controls, adapters, and coding-agent entry points.

Open reference
Lifecycle 02valdris-route-goal

Route and Control the Goal

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

Open reference
Lifecycle 03valdris-assure

Assure

Evaluate Layer 0 and the applicable production-domain obligations.

Open reference
Lifecycle 04valdris-connect-runtime

Connect the Runtime

Normalize runtime events and artifacts from an external coding agent.

Open reference
Lifecycle 05valdris-execute-workflow

Execute the Work

Run the selected work-type skill against the immutable route.

Open reference
Lifecycle 06valdris-prove-govern

Prove and Govern

Validate evidence, approvals, review separation, and the run packet.

Open reference
Lifecycle 07valdris-trust-improve

Trust and Improve

Preserve trusted learning and approve controlled improvements.

Open reference
04

Eight work-type skills

Work-type skills select the engineering procedure after classification and routing. They are not lifecycle stages.

Work typevaldris-intake-route

Intake and Route

Classify an authorized request and select the smallest valid route.

Open reference
Work typevaldris-bug-rca

Bug Root Cause Analysis

Reproduce a defect, establish its root cause, fix it, and prove non-regression.

Open reference
Work typevaldris-feature-delivery

Feature Delivery

Deliver a feature or integration through implementation and proof.

Open reference
Work typevaldris-architecture-refactor

Architecture and Refactor

Change architecture or module boundaries while preserving required behavior.

Open reference
Work typevaldris-security-audit

Security Audit

Test security, privacy, authorization, and tenant-isolation claims.

Open reference
Work typevaldris-platform-release

Cloud Infrastructure and Release

Govern cloud infrastructure, deployment, rollback, recovery, and release work.

Open reference
Work typevaldris-genai-assurance

Generative AI Assurance

Evaluate models, prompts, retrieval, agents, tools, memory, and AI telemetry.

Open reference
Work typevaldris-proof-handoff

Proof and Handoff

Validate required evidence and hand off a supported result.

Open reference
05

Layer 0 and 13 production domains

Layer 0 commissions the foundation. The production domains then evaluate applicable operational obligations.

Layer 0

Foundation / Good Looks Like

Layer 0 binds the authorized request, workload classification, required capabilities, assurance tier, selected profiles, and proof contract before non-documentation delivery begins.

7 capabilities / 14 controls
Inspect every capability, control, profile, and proof level →
06

Three assurance levels

The level names the strength of the supported claim. It does not describe visual polish or agent confidence.

01

Structural

Required artifacts, schemas, bindings, and coverage are valid.

02

Semantic

Commissioned adapters and thresholds prove the intended behavior.

03

Authoritative

An independent trusted runner, provider, signer, or authority attests the result with rollback-resistant state.

07

External runtime boundary

Claude Code, Codex, Hermes, and other coding agents perform implementation. Valdris records allowed activity and checks proof.

Blueprint

Explains topology and expected flow with static descriptive data.

It does not claim that execution occurred.

Live Run

Shows events from an application programming interface, command-line tool, Model Context Protocol server, connector, or watched artifact.

It can support runtime claims only when the source identity and artifacts verify.

Replay

Reconstructs a recorded run from stored events and artifacts.

It must identify the original run and cannot present replay data as live data.
08

Operating rules

These boundaries prevent route weakening, self-approval, fake runtime claims, and unsupported completion.

  1. Artifacts support claims; an assertion alone is not proof.
  2. Every applicable domain resolves to evidence, a failure, or an explicit reason for non-applicability.
  3. A stronger finding can add controls but cannot silently weaken the frozen route.
  4. External coding agents implement work; the harness commissions, routes, records, checks, and blocks.
  5. Human approval permits a decision but does not replace missing technical proof.
  6. Authoritative assurance requires trust outside the delivery agent and repository-local evidence.
09

Search the complete reference

Search all 15 skills, 13 production domains, and every approved Markdown source document in the pinned public snapshot.