A product map for the artifact in front of you.

Each surface keeps rendered review as the primary experience, then exposes the right supporting tools for source, revisions, provider sync, or UI context.

SurfaceExample artifactComment anchorHandoff
Markdown ReviewAI-generated GitHub docs PRSection, paragraph, selected textProvider-pending comments before GitHub submission
HTML ReviewStatic docs page, generated report, or HTML briefHeadings, sections, rows, cards, figuresApp-native or conservative provider sync
Draft ReviewsLocal launch plan, MDX page, HTML brief, or pasted textRendered blocks across uploaded revisionsShare link, export latest draft, or send revision context
FormsReadiness checklist, signoff gate, beta feedback, or response linkEmbedded fields, standalone contracts, response links, and result collectionsResult ownership, API/MCP answers, and optional git result sync
Brainstorming ReviewsArchitecture plan, rollout proposal, or agent-authored specPlan sections with decision stateAccepted plan of record for people or agents
Knowledge BrainLLM wiki, research brain, project memory, or runbook baseWiki pages, source notes, outputs, health findingsBrain API, MCP, evaluations, or public reader
Live Preview ReviewsOpted-in preview app or localhost sessionSelected UI element with route and viewportSDK context packet for developers and agents
Shared review model

Different artifacts, one durable commenting loop.

Threads stay app-native and attach to meaningful blocks first. GitHub comments, draft exports, consensus state, and SDK packets are synchronized representations around that core review record.

Rendered document firstSemantic anchorsProvider-aware handoff

Start with the review surface you need.

Open a GitHub PR, create a draft, or explore developer tools for API and MCP workflows.