MermaidCreator
Sign inOpen editor

Interactive sample— the real DiagramOps UI on a sample workspace. Nothing here is live; nothing needs a signup.

Get DiagramOps

Knowledge Integrity — Acme Platform

What changed across diagrams, docs, and runbooks. This is the cockpit a DiagramOps workspace opens to.

Open findings

5

Awaiting review

Stale knowledge

2

Evidence changed

Tracked knowledge

9

across 5 sources

Checks this month

27

of 250 included

Needs your attention

The most recent drift the audit and PR merges surfaced.

  • criticalCheckout API contract changed — diagram + reference are staleopen
  • highPayments flow diagram no longer matches the codeopen
  • mediumArchitecture overview references a removed serviceopen
  • highEvidence source for legacy gateway design disappearedneeds owner
  • mediumOnboarding SOP has no companion diagramopen

Recent activity

Drift checks, audits, and PR comments DiagramOps ran.

  • PR drift check ranacme/checkout-service #182 · 1 finding opened5h ago
  • Posted architecture impact on PRacme/checkout-service #1825h ago
  • Finding openedCheckout API contract changed — diagram + reference are stale2d ago
  • Weekly audit ran14 assets checked · 2 findings opened3d ago
  • Finding resolvedPayments flow diagram updated after review4d ago

Drift review

Every catch arrives as a review-first finding: the evidence, the impact, the proposed fix, and the decision — in one place.

  • criticalopen patch

    Checkout API contract changed — diagram + reference are stale

    Contract changed · acme/checkout-service

  • highopen

    Payments flow diagram no longer matches the code

    Diagram stale · acme/checkout-service

  • mediumopen

    Architecture overview references a removed service

    Doc stale · Architecture Overview (manual)

  • highneeds owner

    Evidence source for legacy gateway design disappeared

    Source deleted ·

criticalContract changedopen2d ago

Checkout API contract changed — diagram + reference are stale

POST /api/checkout now requires a `currency` field, but the checkout diagram and API reference still document the old contract.

What changed

1 endpoint and 1 schema changed since last verified.

Consumers integrating against the documented contract will omit the now-required `currency` field and get 400s.

POST /api/checkoutschema: CheckoutRequest
  1. Compare the new route handler against the documented contract
  2. Confirm `currency` is required and stable
  3. Apply the patch or dismiss

Proposed change

Copy accepted patch
--- a/docs/api/checkout.md
+++ b/docs/api/checkout.md
@@ CheckoutRequest
-  amount: number        // minor units
+  amount: number        // minor units
+  currency: string      // ISO 4217, now REQUIRED
   items: LineItem[]

Decision

Apply diagram update Confirm drift Not actionable Mark resolved

Review-first: the diagram and docs stay untouched until someone clicks. In the live product these buttons act — here they just pose for the photo.

Living diagrams

Generated from the repo, then watched. Drift flips the primary action from “Open” to “Review change”.

Checkout service architectureactive

acme/checkout-service · verified 2d ago

Open Diagram
Payments authorization flowstale

acme/checkout-service · verified 14d ago

Review change Diagram

Now imagine it watching your repo

Connect GitHub and your docs; the first architecture diagram is drawn in about a minute — and the first catch usually arrives with your next merge.

Get DiagramOpsSee the PR comment demo