The documentation
automation pipeline.

A complete picture of how Syscribe goes from PR merge to deployed documentation — and why every step matters.

01

Every PR merge is a documentation event.

Your CI/CD webhook fires immediately when a PR merges. Syscribe ingests the diff — not just which files changed, but what the changes mean semantically.

If the PR references a Linear or Jira ticket, Syscribe fetches the issue description, acceptance criteria, and context. The generation prompt knows why the code changed, not just what changed. That's what makes the documentation accurate.

{
  "event": "pull_request.merged",
  "repo": "syscribe/api",
  "pr": 412,
  "title": "feat: streaming /events",
  "files_changed": 3,
  "diff_preview":
    + export async function streamEvents(
    + req: Request, res: Response
    + ) { ... }
    - // streaming not yet implemented
}
02

The knowledge graph knows where to look.

Before generating anything, Syscribe consults the knowledge graph — a per-customer map of your documentation landscape built during onboarding and updated on every PR.

The graph knows which sections map to which code paths, your confirmed structure, which sections are human-owned and must not be touched, and which doc types are relevant to which repos. This is what allows surgical section-level targeting — not full-page rewrites.

API Ref
User Docs
Internal
README
Changelog
OpenAPI
3 sections matched ↑
03

Drafts for every surface, simultaneously.

For each affected section, Syscribe generates a draft calibrated to the doc type and audience. Internal docs, user-facing guides, and API references require different tone and depth — each draft reflects that.

Edit learning from previous approvals shapes each draft. After Month 3, Syscribe drafts in your team's voice — not generic AI prose.

NOTION ✓ Ready ## Streaming Endpoints · Updated
MINTLIFY ✓ Ready + server-sent events via /events/stream
README ✓ Ready EventSource-compatible stream
04

One review task. Every doc type.

Reviewer receives an email with a direct link. The review screen shows all doc types for this PR in a tabbed view. Each tab shows a what-changed summary, the proposed update within its section context, and a side-by-side diff against the previous deployed version.

Edit inline. Instruct the agent to revise. Or approve as-is. Each tab has its own approve/reject action. Nothing deploys until approved.

✓ NOTION
● MINTLIFY
○ README
## Streaming Endpoints
+ Supports server-sent events via /events/stream
+ Returns: EventSource-compatible stream
  Authentication required via Bearer token
  Max 1 concurrent connection per API key
05

Deployed simultaneously. Surgically.

On approval, Syscribe deploys to every configured target at once. Only the specific section affected by this PR is updated — the rest of the page is untouched. Your editorial sections, how-to guides, and manually written content are never overwritten.

Full-page rewrite
Surgical editing (Syscribe)
Overwrites manually written sections
Updates only the affected section
Deletes nested sub-pages
Leaves all other content intact
No audit trail per section
Full history per section + PR
06

Every approval trains the next draft.

When a reviewer edits a draft before approving, Syscribe captures the diff. When a reviewer instructs the AI to revise, that interaction is stored too. Both become training signal for future drafts on the same customer, target, and doc type.

Month 1 Baseline generation from your existing docs and codebase structure.
Month 3 Drafts in your team's voice. Recognizes your preferred structure and terminology.
Month 6 Catches your codebase's specific drift patterns before they compound.
Month 12 Switching means starting that learning from zero. That's the moat.

Stop writing docs after the fact.

Syscribe is in private beta. Join the waitlist and we'll reach out when your spot is ready.

No credit card required. We'll confirm by email.