Embed mermaid visuals in core docs

[OgeonX-Ai]

Motivation

• Improve readability and immediate context by embedding visual flowcharts into core operational docs.
• Make diagrams discoverable and ensure each key flow is visible inline while retaining canonical diagram files.
• Align documentation with repository completeness rules that require diagrams be referenced from related docs.

Description

• Added embedded Mermaid flowcharts to core docs including docs/00-executive-overview.md, docs/04-reference-architecture.md, docs/05-operating-model.md, docs/11-incident-response.md, docs/12-change-and-release.md, docs/13-exception-handling.md, docs/16-logging-monitoring-siem.md, and docs/19-devsecops-pipelines.md.
• Kept and referenced the original diagram files in docs/22-diagrams/ so the inline visuals and canonical .mmd sources remain linked.
• Introduced visual flows for service lifecycle, shared responsibility, operating model, incident flow, change flow, exception flow, hybrid logging, and policy-as-code loop to give immediate context to readers.

Testing

• No automated CI workflows or linters were executed as part of this change.
• The repository includes a CI job at .github/workflows/ci.yml that will validate Markdown, run a link check, verify Mermaid blocks, and validate JSON formatting when the workflow is triggered.

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ebfd98def7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Fix nav hrefs for subpages

The pages array uses href: "pages/...", which works only from site/index.html. When app.js runs on site/pages/*.html (loaded via ../assets/app.js), those links resolve relative to the subpage and become site/pages/pages/..., so the navigation and search results 404 unless the user is on the root index. Consider computing a base path from window.location or using paths that are correct for both locations (e.g., ../pages/... on subpages or root-relative paths if you serve from a web root).

Useful? React with 👍 / 👎.

[OgeonX-Ai]

Test