# Mode Profile Enrichment Answer Evidence Proof V01

Issue: #432

Parent: #428

Prerequisites: #429, #430, #431

## Purpose

This proof records deterministic evidence that backend-managed mode/profile enrichment changes answer-side evidence when eligible enrichment evidence is available.

Selected or routed source metadata is not enough. A source ID can be eligible, selected, or visible in telemetry while contributing no supported answer claim. This proof therefore checks final answer lanes, final citations, citation classes, compact telemetry that reports evidence use, and authority separation.

This is field guidance and implementation evidence, not policy, not package authority, and not source-set approval.

## Deterministic Fixture Approach

The machine-readable proof is `docs/product-architecture/mode_profile_enrichment_answer_evidence_proof_v01.json`.

The validation fixture is `validation/fixtures/source_grounded_chat/mode_profile_enrichment_answer_evidence_v01.json`.

The fixtures compare package-only and package-plus-enrichment lanes. Each fixture records prompt, mode, selected profile, source scope, backend routing mode, package evidence, enrichment evidence, final answer lanes, final citations, citation classes, compact telemetry, expected behavior, refusal or qualification behavior, and authority boundary.

The fixtures do not perform live retrieval. Repo-local deterministic evidence is used where a profile has eligible seeded registry metadata but no live runtime fixture is being added in this ticket.

## Package-Only Baseline

The package-only fixture proves the default lane still works with approved package citations only.

Expected behavior:

- `source_scope` is `package_only`.
- The answer cites package evidence.
- No current/public citation is counted as answer support.
- Compact telemetry reports `package-only`.
- Package authority remains unchanged.

## Package Plus NIST-First Enrichment

The NIST fixture uses the canonical governance comparison prompt from the existing usefulness proof:

`Compare what the approved package says about operational AI governance with what NIST AI RMF says about governance expectations. Keep package and current/public source lanes separate.`

Expected behavior:

- Mode is `Answer`.
- Selected profile is `general_ai_capability`.
- Source scope is `package_plus_enrichment`.
- Routing mode is `backend_managed`.
- Package evidence is present.
- NIST current/public evidence is present.
- Final answer lanes separate package evidence from current/public evidence.
- Final citations include both a package citation and a current/public citation.
- Compact telemetry reports enrichment evidence used, not merely selected.
- NIST evidence is not package authority.

This lane reuses the existing NIST usefulness proof posture from #409, but #432 proves the answer-evidence change under the later backend-managed routing model from #431.

## Security Profile Enrichment

The security fixture proves that a non-default profile can change answer evidence when eligible security enrichment evidence is available.

The fixture uses deterministic repo-local evidence for an `ai_security` profile route. It cites package evidence and current/public security evidence separately. The answer may use security enrichment only when the final answer evidence and final citations include the security source as current/public enrichment.

## GxP And Life Sciences Profile

The GxP fixture proves profile-sensitive routing for `gxp_regulated_life_sciences`.

The seeded registry contains GxP profile metadata. This proof does not add live retrieval. The fixture therefore uses deterministic repo-local fixture evidence and qualifies the result. It does not claim regulatory approval, legal advice, validation, compliance, or package authority mutation.

## Unsupported Prompt Refusal

The unsupported prompt fixture proves enrichment is not a hallucination rescue path.

Expected behavior:

- Package support is absent or insufficient.
- Enrichment retrieval or use is blocked or not attempted.
- The final answer refuses.
- No current/public citation is treated as answer support.

## Selected But Insufficient Enrichment

The insufficient fixture proves that selected or routed enrichment metadata is not evidence.

Expected behavior:

- Backend routing may resolve eligible metadata.
- The final answer does not claim enrichment support unless cited enrichment evidence exists.
- The final answer qualifies or refuses.
- The validator fails any selected-only proof that treats `enrichment_selected_source_ids` as used answer evidence.

## Citation Class Separation

Package citations support the package lane. Current/public citations support the current/public source lane. Current/public enrichment may inform synthesis only as enrichment. It is never promoted to package authority.

The validator checks these citation classes directly:

- `package citation`
- `current/public citation`

## Package Authority Boundary

This proof does not mutate package authority. The enrichment source registry remains unchanged. Current/public evidence is not promoted into the approved package corpus or package citation class.

## Relationship To Parent And Prerequisites

| Issue | Relationship |
|---|---|
| #428 | Parent issue for simplifying the source-grounded assistant UX and backend-managed enrichment. |
| #429 | Prerequisite mode-first default UX work. |
| #430 | Prerequisite advanced/operator enrichment mechanics work. |
| #431 | Prerequisite backend-managed routing model. |
| #432 | This answer-evidence proof. |

## Explicit Non-Goals

This proof does not add:

- arbitrary web search
- broad live retrieval
- browser-side source fetching
- browser-side provider calls
- user-entered URL fetching
- enrichment source registry mutation
- package authority mutation
- persistent session-only pasted source text
- durable memory
- vector DB, graph DB, Supabase, hosted retrieval, crawler, worker, webhook, queue, or polling
- Cloudflare configuration changes
- provider or model configuration changes
- #433 answer layout changes

## What This Proof Still Does Not Prove

This proof does not prove broad enrichment usefulness across all prompts, profiles, sources, or production environments. It does not prove source freshness beyond the deterministic fixture posture. It does not authorize new source registration, source-set mutation, production activation, package update, regulatory reliance, or enterprise approval.

## Boundary Confirmations

- #78 is not mutated.
- #271 is not reopened or mutated.
- #428 is not closed.
- #433 is not started.
- The enrichment source registry is not mutated.
- Package authority is not mutated.
- No `codex-automerge` label is applied.