I12 mockup · Diagram Blocks and Leak Guard

Checkout flow (v3)

Updated 18 Oct by Claude Code (agent) on behalf of Dana R. Diagram Blocks Runs on Atlassian

This page was drafted by a coding agent through the Atlassian MCP server. Agents write diagrams as Mermaid text. Without an app, Confluence shows them as plain code.

Diagram Blocks found 1 Mermaid block on this page. Render it as a diagram? The source stays editable.

mermaidCode block

flowchart LR
  UI[Checkout UI] --> API[Payments API]
  API --> FR{Fraud check}
  FR -- pass --> PSP[Card processor]
  FR -- review --> Q[Manual review queue]
  PSP --> L[(Ledger)]
  PSP --> WH[Webhook worker]
  WH --> N[Receipt email]

Card data never touches our servers: the processor tokenises it in the browser. The ledger write and the webhook happen after the processor confirms.

Agent activity on this page (customer's Rovo and MCP clients)

18 Oct 14:02 · Claude Code (via Atlassian MCP) wrote the page with one Mermaid block.
18 Oct 14:03 · Rovo agent "Docs helper" called render_mermaid_blocks → 1 converted. Confirmed by Dana R.
19 Oct 09:40 · Rovo agent called insert_diagram on "Ledger service" → syntax error on line 4 reported back, nothing changed.

Platform Ops / OPS-1287

Staging deploy fails after config change

In progress Assignee: Claude (coding agent)

Description

The deploy job on staging stopped at the migration step after Friday's config change. Repro steps and the env diff are below.

Env diff:
AWS_ACCESS_KEY_ID=AKIA••••••••EXAMPLE masked by Leak Guard
AWS_SECRET_ACCESS_KEY=••••••••••••••••EXAMPLEKEY

Customer list attached by mistake: ana@example.com, li@example.com, +12 more

Activity

Release Agent · agent · 2 hours ago

Pasted the failing step log for context:

step 4/7 migrate: connecting to db-staging…
using token wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
error: relation "payments_v3" does not exist

Dana R. · 1 hour ago

Looks like the migration ran against the old schema. Re-running with the new flag.

# A customer's coding agent checks text before posting (Leak Guard tool via rovo:mcp) > check_text_for_secrets(text: "deploy log, 214 lines") 1 finding: AWS secret key pattern on line 2, high → agent masked the value and posted the comment

Leak Guard

Runs on Atlassian

2Open on this item

1Masked

14Site, this week

AWS secret key in a commentHigh

Posted by Release Agent (agent) · detected 2 h ago

Email address list in descriptionMedium

Personal data · 14 addresses · detected 3 h ago

How it works

Scans: New and edited items, comments, pages
Detectors: Pattern rules, entropy, checksums (no AI model)
Data: Stays in Atlassian; findings store location only, never the secret
Agents: Pre-check tool for Rovo and MCP clients