@@ -24,6 +24,7 @@ Tone: crisp, enterprise, practical. Avoid buzzword soup. Prefer clear boundaries
2424- Include runbooks, SLAs/SLOs, incident response playbooks, change management, exception handling, risk acceptance.
2525- Include a CI workflow that checks markdown, mermaid syntax, and link validity (best-effort).
2626- Everything must be public-safe: no secrets, no internal URLs, no real tenant IDs.
27+ - Every major document must be complete, non-placeholder, and cross-linked to related docs and diagrams.
2728
2829## 1) Output format requirements
2930- Use Markdown for documentation (` docs/ ` ).
@@ -32,6 +33,7 @@ Tone: crisp, enterprise, practical. Avoid buzzword soup. Prefer clear boundaries
3233- Use JSON for Azure Policy stubs.
3334- Use HTML/CSS for ` /site ` static docs with a simple nav and search (JS optional).
3435- Provide consistent naming, cross-links, and an index.
36+ - Avoid inline newline escapes like ` \n ` in Markdown lists.
3537
3638## 2) Repo name + branding
3739Repo title: ` cloud-security-service-model `
@@ -167,6 +169,23 @@ Tagline: “A pragmatic, enterprise Cloud Security service operating model (Azur
167169 okrs.md
168170 kpi-cadence.md
169171
172+ docs/
173+ site/
174+ README.md
175+ index.html
176+ assets/
177+ style.css
178+ app.js
179+ pages/
180+ overview.html
181+ service-definition.html
182+ operating-model.html
183+ architecture.html
184+ kpis.html
185+ roadmap.html
186+ runbooks.html
187+ templates.html
188+ hybrid.html
170189 site/
171190 README.md
172191 index.html
@@ -238,6 +257,7 @@ Tagline: “A pragmatic, enterprise Cloud Security service operating model (Azur
238257 - privileged access exposure (PIM activations, standing admins)
239258 - misconfiguration trend rate
240259 - backup restore test success rate
260+ - Add a brief SLA/SLO section with targets for core service capabilities.
241261- Include a sample dashboard mock (markdown table) and a “metrics anti-patterns” section
242262
243263### docs/08-roadmap-and-maturity.md
@@ -381,6 +401,7 @@ Keep it stable and not overcomplicated.
381401- docs index in README
382402- Each doc includes “Related docs” at bottom
383403- Diagrams referenced from relevant docs
404+ - Each diagram should be referenced by at least one doc and the related doc should mention the diagram.
384405
385406## 12) Quality bar
386407- No fluff. Every section must answer: “what is it, who owns it, how does it work, how is success measured, how does it improve”.
@@ -392,6 +413,7 @@ Keep it stable and not overcomplicated.
392413 - “Evidence” (audit artifacts)
393414- Prefer explicit tables (RACI, KPIs, cadences, responsibilities).
394415- Include “anti-patterns” sections to show maturity (e.g., security as blocker, PDF policies, hero culture).
416+ - Ensure Markdown content is lint-friendly and free of formatting artifacts.
395417
396418## 13) Execution steps (what you should do now)
3974191 ) Create all files and folders above.
0 commit comments