PR Markdown Review
A launch-readiness PR where product, support, and engineering review AI-assisted customer docs before merge.
Read the launch decision, inspect Changes, and find the acceptance criteria a reviewer must verify.
Start with a rendered pull request, then explore how people and agents review plans, previews, and structured answers. Public samples are readable without signing in; review actions keep their normal sign-in requirements.
Read the artifact, identify the decision, and see how precise feedback helps the next revision.
A launch-readiness PR where product, support, and engineering review AI-assisted customer docs before merge.
Read the launch decision, inspect Changes, and find the acceptance criteria a reviewer must verify.
An agent rollout plan with a pending ownership decision and clarifying feedback before implementation starts.
Inspect the pending rollout decision and its feedback. Consensus does not apply changes or grant human approval.
A real billing/settings preview where reviewers comment on selected UI elements with route and viewport context.
Inspect billing and checkout together; follow an element comment to the UI change it requests.
A launch team reviews the release plan and captures structured readiness answers beside the document discussion.
Review the launch plan, then inspect the structured readiness questions alongside the discussion.
Explore the same document-first approach before Git, on a branch, or in reports and knowledge bases.
A runbook branch for an incident-response handoff that needs direct document review before it becomes a PR.
Review a runbook directly on a branch without creating a pull request.
A partner migration readiness report with tables, callouts, and action sections that should be reviewed as a page.
Read the risk register in Preview, with Raw available for the exact generated HTML.
A Commentary support brain that tracks concepts, source notes, decisions, and evaluation questions in an OKF-style repo.
Follow a support claim to its source and inspect the knowledge navigation.
A customer-facing release memo that needs editorial and support review before anyone creates a branch.
Review customer copy before Git; inspect the comments that identify wording and handoff gaps.
Explore Forms authoring and results, response links, and presentation review when those fit your work.
A shared Draft Review contains uploaded form contracts plus Markdown, HTML, and MDX files before anything is pushed to Git.
Inspect uploaded form contracts beside the draft documents that use them.
A focused response page collects launch-readiness answers with clear respondent identity and submission behavior.
Explore the focused respondent experience and its required-field feedback.
A review document explains workspace result collections, canonical git result files, optional writeback, and sync diagnostics.
Inspect the documented result format and optional Git writeback workflow.
A board-ready launch narrative opened directly in Commentary presentation mode.
Read the same Markdown as a presentation while retaining review context.
A launch-readiness training deck reviewed as slides, with source and comments still available.
Inspect a rendered slide deck and its source.