# Claims-Denial Case — Mission 10 Evidence

Reveal this fictional source only after recording the Mission 9 service decision.
It demonstrates a conditional transfer exercise, not completed production ownership.

## S10 — Transfer exercise for the constrained `rec-0.4.3` service

- The Aster support owner diagnosed a simulated stale-policy incident, disabled new
  recommendations, reconciled queued records, and returned cases to the existing
  specialist-only workflow. No older recommendation build was promoted.
- Claims security policy revision 9 changes required policy metadata and context
  retention from 30 to 21 days without changing the specialist-only submission
  boundary. Its fictional exercise digest is
  `sha256:98813fd0f2eb95e0a01954d72448218b71e12b57885663bc77d0290590c2df01`.
- The typed dependency register marks `nl-context-r7`, configuration v2, linked
  security tests, modifier-exception evaluations, and the S8 release record
  `review required` after the policy change.
- The team creates `nl-context-r8` and `northlake-recommend-v3`, binds them to policy
  revision 9, and reruns context expiry, retention, cross-tenant, stale-policy,
  modifier-exception, disable, and queue-reconciliation lanes. All named reruns pass
  under `change-2026-09-21-r1`; the Platform Lead records their restored currentness
  for the same bounded NorthLake route. The S8 configuration v2 release record is
  preserved as superseded.
- Billing operations completes a normal support scenario against the current
  configuration v3 bundle.
- Retirement authority is named, but the retirement and data-disposition exercise
  is tabletop only.
- Two delivery-team credentials remain active until 30 Sep for warranty support.

The transfer result remains conditional: the receiving team has exercised several
operating capabilities, but retirement/data disposition and credential removal still
require live evidence or an explicitly accepted residual support boundary.