docs: design incremental delivery of verified answer content

[BigSimmo]

Motivation

• Reduce perceived answer latency by progressively disclosing already-verified, owner-scoped evidence and independently verified answer sections instead of delivering the whole verified answer only in one buffered SSE final frame.
• Preserve clinical safety and existing verification gates by explicitly forbidding raw token/provisional-prose streaming and keeping all section-level emission behind the same citation/numeric/claim-support/verifier boundary.
• Keep retrieval/ranking behaviour unchanged and treat any provider-backed generation experiments as approval-gated (canary + clinical governance required).

Description

• Added a new design doc docs/verified-answer-incremental-delivery-design.md that defines the staged SSE contract (progress + optional verifiedUnit), the VerifiedUnit schema (evidence previews and answer sections), strict sequence/reconciliation rules, the verification boundary to reuse existing production gates, phased delivery plan (Phase 0 contract proof, Phase 1 evidence preview, Phase 2 verified sections), and rollout/rollback/telemetry requirements.
• Updated docs/README.md to include the new design and updated docs/outstanding-issues.md (ledger item docs: record phase 6 re-audit #100) to mark the design complete while recording that runtime implementation is provider-gated.
• This change is documentation-only: no runtime, retrieval, ranking, prompt, or model code was altered and no new SSE event names were introduced.

Testing

• Ran formatting and docs checks: npm run format / prettier --check ., npm run docs:check-links, and npm run docs:check-scripts, all passed.
• Ran offline RAG/contract validation: npm run eval:rag:offline (offline RAG fixture and manifest validation) — passed (36 golden cases / 22 suites).
• Ran repository verification gates: npm run verify:pr-local (files scoped to docs change) and the full test suites used by the gate; unit/test suites ran successfully with the repo test run reporting the large suite pass (Vitest: 4578 tests run with skips as expected; offline suites and focused tests green).
• Ran npm run check:production-readiness (local check) which passed runtime/runtime-guard checks but reported expected missing server env vars (NEXT_PUBLIC_SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY) for provider-backed gates in this environment.
• Provider-backed work (live canary(s) and any Phase 2 generation experiments) and verify:ui (Chromium UI verification for visible client rollout) were intentionally not run because they require explicit approval and provider access; the design records the required canary and governance gates.

---

Codex Task

[supabase]

This pull request has been ignored for the connected project sjrfecxgysukkwxsowpy because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.

---

Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in:12 minutes

Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3550b33f-2265-4756-978b-147d1c6c0ef6

📥 Commits

Reviewing files that changed from the base of the PR and between f6ae0e7 and 4491b56.

📒 Files selected for processing (4)

• docs/README.md
• docs/branch-review-ledger.md
• docs/outstanding-issues.md
• docs/verified-answer-incremental-delivery-design.md

---

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit:0061b4391c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".