Bring the messy input with you.
Notes, transcripts and briefs enter one workspace without pretending they already agree.
Evidence → requirement → decision
Make the chain visible.
Requirements that can show where they came from—and who approved them.
The public demo uses deterministic synthetic data. No signup, private client material, or production service is involved.
01 — The risk
Polished output is not verified output.
Requra keeps source material, generated structure, quality signals, review, and export as explicit stages. A requirement only becomes credible when the path back to evidence stays intact.
React + TypeScriptNode.js + NestJSFastAPI + LangGraphPostgreSQL + RAG
Make each requirement atomic.
Generated requirements expose confidence, category, coverage, and the decisions that still need a person.
Trace the sentence back.
Citations remain inspectable beside the claim, turning review into verification instead of prompt archaeology.
Export only what survived review.
Approved work moves into delivery artifacts with its audit trail and ownership still attached.
Synthetic workspace / Civic service portal
02 — Orchestration
One workflow. Distinct responsibilities.
The product separates client interaction, tenant-safe APIs, extraction workers, storage, and review. The interface makes that separation understandable without exposing users to an “agent graph.”
Human review is a product state.Authentic synthetic demo