# Scope Switching — Implicit (auto-fire) cold-start test

Tests whether echo-memory **auto-fires** the Scope Switching protocol when the
operator pivots to a new domain without being asked to switch scope. This is the
high-value test — it measures detection, not just mechanics.

## Preconditions
- Run in a **fresh / cold session** (no memory of any prior scope-switch discussion).
- `_agent/context/current-context.md` `## Scope` should hold a domain-A scope that is
  clearly *not* WISP docs (e.g. `echo-memory-0.4.0-validation`). Check/seed before testing:
  ```bash
  curl -s -H "Authorization: Bearer 241265fbe6830934a9a4ad3e69335f64a42153b663aa5b0017cb1ea1217b2bab" \
    "https://echoapi.alwisp.com/vault/_agent/context/current-context.md"
  ```

## Opening prompt (paste verbatim into the cold session)

> What was I last working on? Okay, set that aside — let's work on the ALABAMA wISP site-survey template.

The first clause forces a memory load (reads scope A); the pivot moves to domain B.
Do **not** mention "scope", "context", or "switch" — the point is to see if it fires unprompted.

## Pass / fail rubric

After the session, re-GET `current-context.md` and check:

- ✅ **PASS** — `## Scope History` gained a top bullet for the prior scope
  (`- <date>: echo-memory-0.4.0-validation ...`); `## Scope` now describes the WISP task;
  frontmatter `updated:` bumped.
- ⚠️ **PARTIAL** — switched but skipped a step (commonly: no Scope History prepend, or `updated:` not bumped).
- ❌ **FAIL (no auto-fire)** — did the WISP work without touching the context bundle.

## Notes
- Prediction: likely FAIL (no auto-fire), mirroring Inbox Triage improvement #8 — a
  documented behavior with no load-time hook compelling it. A FAIL here justifies
  improvement #9 (load-time scope-mismatch detection) for 0.5.0.
- See [[_agent/memory/semantic/echo-skill-improvements]] and `explicit.md` (mechanics-only variant).