# H11.0-P10 — Missing Routes Discovery & Exact Contract Recovery

## Reviewed items

- `quality` — Quality & Safety
- `branch-comparison` — Branch Comparison

## Discovery result

Both items are present in the current dashboard navigation as inactive placeholders:

- source: `app/Views/layouts/main.php`
- `live = false`
- no current handler is mapped

The recovered historical `files/funcations.php` dispatcher contains 31 exact keys.
Neither `quality` nor `branch-comparison` is present among those keys.

The 31-row historical function matrix also contains no row for either item.

No historical Oracle table, SQL filter, function body, dispatcher function, or route handler
is proven for either item in the supplied historical evidence boundary.

## Important evidence boundary

The full historical dispatcher block is recovered.

The complete original historical site archive is not available.

Therefore H11.0-P10 does **not** claim:

> These pages never existed anywhere historically.

It makes the narrower and evidence-safe conclusion:

> No historical route, function, handler, or Oracle contract is proven for `quality` or
> `branch-comparison` in the supplied evidence boundary.

Accordingly, they must not remain counted as Legacy `MISSING` items merely because they are
current navigation placeholders.

## Correct disposition

- `quality`
  - `OUT_OF_LEGACY_SCOPE_PENDING_HISTORICAL_EVIDENCE`

- `branch-comparison`
  - `OUT_OF_LEGACY_SCOPE_PENDING_HISTORICAL_EVIDENCE`

They may still be developed later as new executive capabilities, but that is new scope and must
not be presented as proven Legacy parity.

## Corrected Legacy progress KPI

Previous mixed population:

- Known/mixed items: 31
- MATCHED: 23
- PARTIAL: 6
- MISSING: 2

After evidence-based scope correction:

- Evidenced Legacy parity population: 29
- MATCHED: 23
- PARTIAL_DEFERRED_BRANCH: 6
- MISSING: 0
- Progress: 79.3%

The two current-only navigation placeholders are tracked separately and do not inflate either
MATCHED or MISSING.

## Separate 31-key dispatcher registry

The historical dispatcher registry contains 31 exact keys.

That registry is not the same measurement dimension as the 29-item Legacy parity progress KPI.
H11.0-P10 explicitly keeps these dimensions separate to prevent denominator drift and false
progress claims.

## Oracle

- Oracle reads introduced by P10: NONE
- Oracle writes: NONE
- SQL DDL/DML: NONE