Read a review's history
Open a design review in the dashboard to see its requirements, related checks and findings. Calls bound to the same design_review_id stay connected, making it possible to follow a blocked proposal and the evidence from a later correction.
Keep uncertainty visible
A passing write is not the same as a resolved review. Some requirements can remain not established when the relevant code or service behavior is unavailable. Read the requirement's evidence as well as the overall check result.
Use the terminal
Ask Claude to use flowrail-lineage for the active review, or provide a specific review id. The skill retrieves the recorded trace through flowrail_get_lineage. The dashboard provides the richer visual view.
Unbound checks and CI
A hook call without an active review cannot establish evidence under that review. CI gate runs are project-scoped. Keep those scopes in mind when interpreting gaps in a review's history.
Stored information
FlowRail records metadata, verdicts and derived evidence rather than the original source or specification body. Findings and summaries can still contain design information. See the privacy page for the data handling details.