DegradedView Evidence →

Proof Walkthrough

A step-by-step verification path. Each step tells you what to do, what you should see, and links directly to the corresponding receipt in the evidence bundle.

1

Receipts (Build Provenance)

Degraded
What you do
  • •Open the Evidence page and inspect the receipts row.
  • •Confirm the commit hash and CI run link match the deployed site.
What you should see
  • •Commit: a9ded2b (main)
  • •Deploy URL: https://executive-intent.web.app
View evidence →Open receipts dashboard
2

Google OAuth (Source Access)

Configured
What you do
  • •Check configured scopes and the last connection timestamp.
  • •Confirm the status is not green unless a live API call is proven.
What you should see
  • •Scopes listed and last connection time present (or “Never” if not connected).
  • •A clear rationale explaining why it is connected/verified vs only configured.
View evidence →Open receipts dashboard
3

Inngest (Orchestration)

Configured
What you do
  • •Review recent run IDs and the last successful run timestamp.
  • •If there are failures, confirm they are reported explicitly.
What you should see
  • •Recent run IDs (or “None” when not yet running).
  • •A status that is blue/neutral while processing, not greenwashed.
View evidence →Open receipts dashboard
4

Nightfall DLP (Content Enforcement)

Verified
What you do
  • •Verify the DLP policy name and decision counts (allowed/redacted/quarantined).
  • •Confirm scans are observed before indexing claims are made.
What you should see
  • •Policy name plus non-zero scan counts when data is flowing.
  • •Clear status: configured vs verified based on observed scans.
View evidence →Open receipts dashboard
5

Supabase + pgvector (Storage)

Degraded
What you do
  • •Confirm schema version, pgvector enabled, and RLS verification.
  • •Review document/chunk/vector counts for basic consistency.
What you should see
  • •Schema version and pgvector/RLS signals present.
  • •Counts displayed without rounding or “success” coloring when unknown.
View evidence →Open receipts dashboard
6

Retrieval Verification (Proven Search)

Degraded
What you do
  • •Inspect the retrieval test: success_count/query_count and pass criteria.
  • •Review sample queries and the returned (doc_id, chunk_id, score) rows.
What you should see
  • •Retrieval result: 2/2 (pass criteria is explicit).
  • •If failing, top failure reasons are listed and linked to the relevant integration.
View evidence →Open receipts dashboard