> ## Documentation Index
> Fetch the complete documentation index at: https://docs.super-intelligent.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# New Claims Route Back to Admin Verify

> The ongoing habit that says new evidence found after go-live is not silently trusted — it re-enters through the same Admin Verify door as everything else.

## Surface

Checklist milestone only — no dedicated route of its own; the step's `link` re-points at the Admin Verify entity route. Step definition: `src/lib/checklist/steps.ts:72` — `{ step_key: 'new_claims_admin_verify', label: 'New Claims Route Back to Admin Verify', link: '/entities/[id]/admin-verify', type: 'infinite', section: 'ongoing_monitoring' }`.

`type: 'infinite'` — never completes; renders as an ongoing habit indicator on the entity checklist, not a one-time checkbox.

Full Admin Verify behaviour, endpoints, and traps live in [/lifecycle/admin-verify](/lifecycle/admin-verify). Do not duplicate them here.

## Section anchor

This is the last step in the `ongoing_monitoring` section (`steps.ts:68–72`):

1. `monitoring_active` (`:68`, `type: 'finite'`)
2. `identity_drift_monitoring` (`:69`, `type: 'finite'`)
3. `health_recheck_cadence` (`:70`, `type: 'finite'`)
4. `provider_freshness_review` (`:71`, `type: 'finite'`) — Layer 2 / provider chain, out of scope for docs
5. `new_claims_admin_verify` (`:72`, `type: 'infinite'`) — this step

## State

Pure checklist state. `type: 'infinite'` means the step never resolves to `complete`; the render layer treats it as an ongoing habit rather than a boolean gate. Nothing reads `new_claims_admin_verify` as a precondition.

New-claim discovery is not driven from this step — it comes from the Harvest Evidence pipeline (`src/app/api/harvest-assets/route.ts`) and manual evidence writes. This step only says the operator knows the route back into Admin Verify.

## Data contract touchpoints

None specific to this step. Admin Verify's own data contract (evidence state transitions, resolve-claim endpoint, decision persistence) is documented on [/lifecycle/admin-verify](/lifecycle/admin-verify).

## Authorization

Same as Admin Verify (see [/lifecycle/admin-verify](/lifecycle/admin-verify)). Marking the ongoing habit as acknowledged requires standard tenant session; there is no separate role gate on this step.

## Traps

* Do not describe `new_claims_admin_verify` as "the step that runs when new claims arrive." Nothing is triggered. It's a habit indicator.
* Do not add Admin Verify mechanics to this page. Route, endpoints, keyboard shortcuts, queue filters, and decision persistence all live on [/lifecycle/admin-verify](/lifecycle/admin-verify). Duplication creates drift when Admin Verify changes.
* Do not treat `type: 'infinite'` as a bug or a placeholder. It is deliberate — the step is meant to stay open.
* Do not conflate with `provider_freshness_review` (`steps.ts:71`) — that step is Layer 2 / provider chain and out of scope for docs.

## Proof chain

* `src/lib/checklist/steps.ts:72` — step definition (`link: '/entities/[id]/admin-verify'`, `type: 'infinite'`, `section: 'ongoing_monitoring'`).
* `/lifecycle/admin-verify` — the surface this step re-points at.

## Related

* Overview: [/index](/index)
* Surface this step routes to: [/lifecycle/admin-verify](/lifecycle/admin-verify)
* Upstream (monitoring group): [/lifecycle/monitoring-active](/lifecycle/monitoring-active), [/lifecycle/identity-drift](/lifecycle/identity-drift), [/lifecycle/health-recheck-cadence](/lifecycle/health-recheck-cadence)
* Related discovery paths: [/lifecycle/harvest-evidence](/lifecycle/harvest-evidence), [/lifecycle/evidence-locker](/lifecycle/evidence-locker)

***

**Status:** Verified · **Layer:** 1 (ongoing monitoring) — habit indicator, `type: 'infinite'`; all mechanics live on [/lifecycle/admin-verify](/lifecycle/admin-verify).