Report, sharing and automation

1. The consolidated report

Report (press 9) puts the deck on one page: the gate verdict with every rule, the open findings, key metrics per evidence item (with scenario B next to A), the batches, the actions with due dates and the review meeting. Print / save as PDF prints only the report; Markdown downloads it as .md for a wiki or ticket; Findings (CSV) exports the full list with status, details and fixes. The Export menu also has the actions, the timeline and the deck as JSON.

2. Share and keep

• File → Copy share link puts the deck into the link itself (#project=…). The link contains the evidence text as you pasted it — masking only applies when sending to a tool — and no results; the receiver presses Run all. Very large decks need a file instead.
• File → Save writes a .opsdeck.json file; File → Open file… opens it again. Results and history are kept in the file, so it opens with everything readable offline.
• File → Open recent… lists the decks saved in this browser.
• With Google Drive connected in the top bar, Save to Drive and Auto-save keep the deck in your Drive.

3. Hand over to other apps

With the App Bridge, Export → Open findings in another app… sends the findings as a table, Open report in another app… sends the report as text, and Open results (JSON) in another app… sends a digest with findings, metrics, the gate and actions. The dialog lists only apps that accept that type. Opsdeck accepts text, JSON and tables in return: text and JSON open Add evidence pre-filled with the detected kind, tables open an import preview where you choose a batch or Lambda data. Nothing runs until you press Run.

4. Scripts and AI agents

Everything in Opsdeck is built on public usefulweb tools. On the Opsdeck host:

• GET /api/v1/tools lists the eighteen tools; POST /api/v1/tools/<id>/calculate runs one with JSON input, for example cicd-failure-explorer with {"logs": "…"}.
• /mcp exposes the same tools to AI agents; /openapi.json and /llms.txt describe them.
• /project.schema.json documents the deck format: evidence[] with kind (ci, cron, lineage, trace, k8s, openapi, plan, lambda, terraform, error, decode, unicode, perm, lookup, format), text, textB and options; batches[], gate.rules[], actions[] and meeting.

A script can collect logs from your pipeline, write a deck, encode it as base64url and open /app#project=<deck> — the person on call sees the same deck and presses Run all.