# Scope, methodology, and evidence rules

## Review snapshot

Inventory date: **July 19, 2026**.

| Source | Branch | Commit reviewed |
|---|---|---|
| kinship-shared | main | `60f7b2251f6ca7abe20f96bfea27e7ec94d0d46d` |
| kinship-shared | dev | `58b0cde1bd8e83d8541fb4f2059b2888e14201c1` |
| kinship-agent-be | main | `67f7d76bd8dba6b7db2a924ac83e8b58c5511e62` |
| kinship-agent-be | dev | `acf2a073a6e079dc1b04392f7b4039b5333f676f` |
| kinship-knowledge | main | `afa5b1de2e562cef81880eda4856fce7fa1c7e65` |
| kinship-knowledge | dev | `b5ed45c68e2949b1f858badd47c25f4988a75db7` |
| kinship-assets | main | `9e2d8a02e85a6da0b0be33765223abc29c9a2490` |
| kinship-assets | dev | `fc3c6cbb7d2f46b7f811d4170ae35284acb7ad98` |

The live review directory exposed 209 routes: 6 onboarding, 14 active, 36 public, 105 Studio, 35 market, and 13 standalone screens. The canonical list is in `resources/review-v1-screen-inventory.md`.

## Method

1. Read the live Review Library v1 directory and validated representative embedded screens.
2. Enumerated every review route and mapped it to its source application route.
3. Inspected all UI page files and extracted visible controls, links, placeholders, and action labels.
4. Inspected every API route declaration on `main` and `dev` in all four repositories.
5. Inspected data models, migrations, schemas, agent graphs, validators, tools, and services.
6. Normalized those findings into user-facing capabilities and atomic actions.
7. Compared the normalized capabilities to the current screen catalog to identify missing, partial, hidden, legacy, or admin-only UI coverage.

## Evidence levels

- **Explicit UI** — a dedicated v1 screen or visible control represents the capability.
- **Partial UI** — a related screen exists, but one or more lifecycle, configuration, status, error, or audit actions are not explicit.
- **Backend only** — API/model/service evidence exists with no clear dedicated v1 surface.
- **Legacy/prototype** — the route exists but is named deprecated, legacy, sample, or otherwise not a reliable production commitment.
- **Dev only** — evidence exists on `dev` but not on the reviewed `main` snapshot.
- **External dependency** — the implementation delegates to a login service, blockchain wallet, Google Drive, MCP/OAuth provider, cloud storage, LLM, vector database, notification service, or other external system.

## Completeness interpretation

“Complete” here means all statically discoverable product capabilities were captured at the reviewed commits. It does not mean every endpoint is production-ready or reachable without environment configuration. Dynamic provider catalogs, external login-service endpoints, blockchain program behavior, and environment-only feature flags may add more runtime behavior. The raw endpoint and model inventories are included so future changes can be diffed without repeating the entire audit.

## UI design rule

Every capability must be intentionally assigned one of these design outcomes:

1. dedicated user-facing screen;
2. action within a parent screen;
3. guided flow or wizard;
4. contextual modal/drawer;
5. admin/operator-only surface;
6. API/automation-only with visible status and audit trail; or
7. explicitly retired.

