ServicedogTrainingDFW — Status: ON HOLD

Recorded: 2026-09-17 Status: ⏸ ON HOLD (per Tony, 2026-09-17) Client ID: veripath-002-servicedogtrainingdfw

What exists (preserved, not committed to main)

Stashed CBR rewrite — the ServicedogTrainingDFW canonical business record (instance record replacing the schema doc) is preserved in the veripath repo as stash@{0}: wip: servicedog CBR instance record (pre-core3 integration 2026-09-17). Recoverable anytime with git stash apply / git stash pop.
Untracked repo files (left in place, not committed):
- SKILL.md (repo root — VeriPath Canonical Business Record System)
- docs/decisions/2026-08-28-servicedogtrainingdfw-audit.md
- veripath-audit/ (SKILL.md)

Do not commit or delete the service-dog work while on hold.
The Core 3 field-map integration (committed f3bae05 + 3f9234f) is independent and already on main — it does not depend on the service-dog record.
When service dog resumes: recover the stash, commit the three untracked files as a coherent unit (decision doc + CBR instance + audit skill), then continue the audit/verification flow.

CBR instance record is in a stash, not in the repo — treat as draft until committed.
The CBR architecture doc on main remains the schema (correct behavior).