AI-Orchestrated Docs.
Human-Orchestrated Comments.

Highlight any text on this rendered page to leave inline feedback, discuss architectural specs, and test collaborative review committing directly to custom Git refs.

🔑 Instructions to Get Write Access to Leave Comments

Comments on this demo are public to view for everyone. However, to add or reply to comments, GitHub requires repository collaborator access. Complete this 1-click step to get write access, or explore the Instant Zero-Auth Mock Demo with simulated personas and zero GitHub setup:

👉 Request 1-Click Write Access (Join @md-comments/demo-commenters) → Instant automated bot approval • Or try Mock Demo →

Sample Technical Specification

This live document demonstrates how inline comments attach directly to rendered prose. Try highlighting any sentence or inspecting the pre-existing feedback from our reviewers.

Authentication Protocol

All client applications communicate with the backend via mutual TLS and JWT bearer tokens. Tokens expire after 60 minutes and must be refreshed using the /auth/refresh endpoint.

Discussion prompt: Should token lifetime be reduced from 60 minutes to 15 minutes for enhanced security?
Highlight the sentence above and leave your feedback!

Data Storage Architecture

Database replicas are distributed across three availability zones:

us-east-1a: Primary read/write node
us-east-1b: Synchronous standby node
us-east-1c: Read-only reporting replica

export interface ClusterConfig {
  primaryRegion: string;
  replicas: number;
  autoFailover: boolean;
}

Deployment Guidelines

All production deployments must follow blue/green rollout procedures. Canary traffic is routed to the new deployment group at 5% intervals before 100% promotion.

Decentralized Data Sovereignty

"Decentralized collaboration guarantees data sovereignty. By storing conversations directly in Git refs, technical teams retain permanent ownership of all review history and design decisions."