SDAD v3.2.2

SDAD v3.2.2

Release date: 2026-07-15
Tag: v3.2.2

SDAD v3.2.2 strengthens owner-driven direction changes, long-running packet
coherence, handoff identity, and the Rule 5 feedback lifecycle. It does not
introduce a new state schema, report schema, Doctor check, or finding ID.

Current Owner Direction

A current applicable Owner instruction can interrupt an older plan, packet, or
handoff direction. A directed adoption or implementation request is reconciled
into the active SPEC and state before affected stateful work resumes. Review,
draft, question, hypothetical, quotation, negation, and reference-only intent
remain non-implementing.

Owner cancellation without a replacement defers the packet, records the reason,
and requires explicit Owner reactivation. Late results from work that could not
be preempted remain stale until rerouted and revalidated.

Rule 5 Feedback Lifecycle

Repeated pain, or one high-risk missing control, now follows a closed lifecycle:
finding and evidence, root cause, smallest durable control, enforcement and
regression evidence, field use, then Keep, Refine, Merge, or Retire. The compact
loop stays visible in the startup kernel; detailed promotion and optional
human-readable rule portability remain on-demand. No plugin, remote loader,
background synchronization, or automatic imported-code execution was added.

State v2 And Packet Identity

State schema v2 remains unchanged. Stateful Standard and Full installations
retain one executable leaf active_packet, exact execution_scope: unit | packet,
and validation_for equal to the active packet ID. A same-boundary unfinished
change can amend the current packet; a material or post-acceptance change uses a
new packet and fresh validation. State schema versions remain separate from
Doctor and report schema versions.

SDAD Doctor 3.2

The checkout-only, read-only Doctor reports version 3.2.2 and supports the exact
guard:

python <SDAD_CHECKOUT>/scripts/sdad.py doctor [PROJECT_ROOT] --require-version 3.2.2 [--json] [--strict]

Existing unguarded state-v1 JSON calls retain report schema 1; guarded or
state-v2 calls use report schema 2. The five-check order, v1 compatibility,
finding IDs, severity policy, state schema, and report schemas are unchanged.

Handoff, INDEX, And Ledger Consistency

New continuity checkpoints use YYYY-MM-DD-HNNNN-topic.md. HNNNN advances
only within its filename date and restarts at H0001 on a new date. The full
date-plus-ID path is the identity; neither the date nor greatest ID establishes
currentness. Only state current_handoff does. Existing unnumbered handoffs
remain valid, and parallel same-date collisions must be resolved before merge.

Doctor continues to check the state-declared handoff's path, readability, size,
and packet marker. It does not allocate IDs, scan all history, or decide
semantic SPEC authority.

Targeted Routing

The startup route remains adapter -> sdad-state.yaml -> docs/INDEX.md, then
current source/tests and only the path, heading, section, or match needed for the
current intent. routed_docs remains an eligible selection set rather than a
startup read-all order. Owner-named current input may be inspected even when a
stale route omits it, but adopted authority and routes must be reconciled before
stateful implementation.

Migration Preview And Upgrade Compatibility

The read-only preview and state-v1 compatibility contract are unchanged.
Existing installations are not modified automatically. Reinstall an adapter or
skill only when adopting the 3.2.2 contract. No-clone sources pin immutable
baseline adfd40afd4e1d3fcaba64cc3f5be936c5feb51fd; keep its revision, source
path, and SHA-256 together.

Verification Evidence

The local release gate covers all seven pinned Git-blob hashes, manifest and
installer parity, rendered agent surfaces, Copy-Paste Start Prompt parity,
repository validation, unittest discovery, and whitespace. The local Windows
gate ran 443 tests, with three environment-dependent skips.

The existing fresh-context task benchmark remains the bounded evidence for
adapter -> state -> INDEX context recovery; it is not a new comparative result.

Independent whole-branch review reported no Critical or Important findings.
This evidence establishes the tested repository contracts only; it is not a
controlled comparison and does not claim improved productivity or general
effectiveness.

Known Limitations

Doctor green proves structural consistency only; it does not prove correctness, productivity, or owner acceptance.
It also does not prove semantic sufficiency.
SDAD does not execute
declared validation, preempt every running tool or remote job, replace tests or
CI, enforce permissions, or act as an orchestrator. Tool policy, review, branch
protection, technical enforcement, and Owner judgment remain separate controls.