Workspace

Pulse Q&A

Ask anything about a project in plain English. Pulse answers from the indexed corpus — RFIs, meetings, daily logs, submittals, change orders — and cites every claim back to its exact source.

What you see

Pulse Q&A is the RAG-cited Q&A surface. Empty state shows a prompt + six suggested questions tuned to the project's open risks. Answer state has two columns: the answer on the left with inline [n] chips, and a source panel on the right listing every cited chunk with its kind label (RFI / Meeting / Spec / …) and a verbatim quote. Click any [n] in the answer to scroll the source panel to that source and flash it amber for 1.5 seconds.

The non-negotiable contract

Every claim Pulse makes points back to a source artifact + a span inside that artifact. No floating sentences. If the model can't find evidence, it says I don't have evidence for that on this project — never guesses. Refusal mode is better than a hallucination.

How retrieval works

Every project artifact (RFIs, meetings, daily logs, submittals, COs, emails, tasks, punch items) is chunked at the right granularity per source kind and indexed at upload — Gemini's text-embedding-001 produces 1536-dim vectors stored in pgvector. At query time, the question embeds into the same space; we run hybrid retrieval (semantic cosine + BM25 over description, fused by reciprocal-rank) via a single Postgres function. Then Claude Sonnet composes the answer with mandatory citation tokens.

Every control

Ask Pulse

Plain-English question. ⌘+Enter to send, Esc to clear.

Suggested questions

Six prompts the engine generates from the project's open risks.

[n] citation chip

Click any inline citation — scrolls the right rail to source [n] and flashes it amber.

Source card

Right-rail card per cited source: kind chip (RFI / Meeting / …), source label, verbatim quote, confidence %.

↻ Reindex project

Walks every artifact and rebuilds the chunk index. Run after large data imports or model upgrades. Rate-limited.

New thread

Clears the current conversation and returns to the empty state.

Time + permission awareness

Every chunk has a valid_at timestamp; if a question is time-sensitive ("what's the latest on RFI 042"), the retriever filters to current chunks. Owner / sub viewers see a filtered chunk set — chunks tagged with stricter visibility never surface to readers who don't have access. Every query + answer + citations is written to the audit log.