DegradedGenerated Jan 13, 2026, 07:12 PM UTC

Evidence

Receipts for build, deploy, and system checks.

evidence.jsonevidence.md

Receipts

This ties the bundle to a specific commit, CI run, and deployment.

Commit
a9ded2b
Branch: main
CI Run
20969264108
Open run →
Deploy
https://executive-intent.web.app
Channel: live
Generated At
Jan 13, 2026, 07:12 PM UTC
Builder: Claude Code

Pipeline Health

Rollup status across all subsystems, plus concrete processing counts.

Overall

Why: Pipeline degraded: supabase, embeddings needs attention [DOC_CHUNK_MISMATCH, DOC_VECTOR_MISMATCH]

Degraded
Documents
11
Fully Processed
22/11 (18%)
Retrieval
2/2Pass ≥ 2/2
supabaseDegraded
inngestConfigured
nightfallVerified
google oauthConfigured
embeddingsDegraded

Integrations

Each card shows a status, a rationale, key metrics, and what would make it “Verified”.

Google OAuth

No OAuth-scoped active connection found (ignoring IMAP test connections) [NO_TOKEN, NO_DATA_OBSERVED_YET]

Configured
Token Valid
No
Scopes
4configured
Last Connect
Never
Checked
Jan 13, 2026, 07:12 PM UTC
What would make this Verified?
  • •OAuth credentials configured
  • •Token exists and is valid
  • •API call succeeds (not 401/403)

Inngest

Inngest configured; no observable workflow activity yet (no audit_events) [NO_DATA_OBSERVED_YET]

Configured
Env
production
Recent Runs
0
Failures
0
Last Success
Never
What would make this Verified?
  • •Event key and signing key configured
  • •Recent successful run exists (within 24h)
  • •No recent failures

Nightfall DLP

DLP verified: 11 allowed, 0 redacted, 0 quarantined [ALL_CHECKS_PASSED, DATA_FLOWING]

Verified
Policy
executive-intent-dlp
Allowed
11
Redacted
0
Quarantined
0
What would make this Verified?
  • ✓API key configured and valid
  • ✓At least one scan observed (counts > 0)
  • ✓OR seeded test dataset has been processed

Supabase

Coverage mismatch (eligible: 11, chunked: 2, embedded: 2) [DOC_CHUNK_MISMATCH, DOC_VECTOR_MISMATCH]

Degraded
Documents
11
Vectors
2
Schema
003
RLS
Verified
What would make this Verified?
  • •Database connection works
  • •Tables exist with expected schema
  • •Document/chunk/vector counts reconcile (no mismatch)

Embeddings

Retrieval works with existing vectors, but OPENAI_API_KEY is missing so new embeddings cannot be generated [MISSING_CREDENTIALS, THRESHOLD_MET]

Degraded
Vectors
2
Last Index
Jan 12, 2026, 07:32 AM UTC
Retrieval
2/2Pass ≥ 2/2
Top‑K
10
What would make this Verified?
  • •Embedding provider configured
  • •Vector count > 0
  • •Retrieval test passes (≥8/10 queries return results)

Retrieval Test

Proves semantic retrieval returns real results with provenance.

Result

Pass criteria: ≥ 2/2 queries return results

Degraded
2/2
Failures: 0 no results, 0 errors
Querydoc_idchunk_idscore
probe:chunk:c3e708fb19aea2e5-6f72-4fb6-9470-e2ea5709d63662fc0977-1409-45c6-bb38-6b4805022fc01.000
probe:chunk:c3e708fb87378f8a-ac84-4feb-b164-6c86c6345628c3e708fb-7aab-4f91-bb72-227e7aa9e1e51.000
probe:chunk:62fc097719aea2e5-6f72-4fb6-9470-e2ea5709d63662fc0977-1409-45c6-bb38-6b4805022fc01.000
probe:chunk:62fc097787378f8a-ac84-4feb-b164-6c86c6345628c3e708fb-7aab-4f91-bb72-227e7aa9e1e51.000

Data Consistency

A small reconciliation view across documents, chunks, vectors, and last indexed.

documentschunksvectorslast_indexed_at
1122 (emb) / 2 (db)Jan 12, 2026, 07:32 AM UTC