ADR 0059: Add Explicit Orientation And Verification Workflows

Status: Accepted

Date: 2026-07-29

Context

STAGE packaged ordinary change delivery and optional project mapping, while fresh-task recovery and claim verification remained embedded guidance. This made two common owner intents hard to invoke:

• “recover the current project safely before I authorize work”; and
• “check this existing change without turning the check into another fix.”

The orientation questionnaire was too large to paste into every new task. Verification inside delivery was correct for work being built, but a separate audit request needed a stronger check-only boundary.

Decision

Package four workflows:

1. stage-deliver-change remains the implicit mutating route;
2. stage-orient is an explicit read-only context-recovery route;
3. stage-verify is an explicit check-only claim-verification route; and
4. stage-map-project remains explicit optional adoption, audit, and map maintenance.

Orientation and verification ship deterministic read-only helpers for Git coordinates, protected paths, change inventory, and source hygiene. Their output does not establish runtime or human-experience claims.

Both new workflows declare allow_implicit_invocation: false. They stop after their report. Mutation requires a separately authorized delivery outcome.

Consequences

• A fresh task can invoke one qualified skill instead of receiving a copied questionnaire.
• Verification failures remain evidence rather than being silently repaired.
• Plugin routing and package tests expand from two to four declared workflows.
• Orientation remains artifact-free; project mapping is still optional.
• The normative Safety Kernel and project-map schemas do not change.