Skip to content

ci(policy): make docs-privacy a required + decisional gate#2

Merged
David-BS merged 1 commit into
mainfrom
t4a-docs-privacy-policy
Jul 8, 2026
Merged

ci(policy): make docs-privacy a required + decisional gate#2
David-BS merged 1 commit into
mainfrom
t4a-docs-privacy-policy

Conversation

@David-BS

@David-BS David-BS commented Jul 8, 2026

Copy link
Copy Markdown
Owner

Adds docs-privacy to required-checks.json (required + decisional) and realigns the required-checks prose in CI_CD.md, CONTRIBUTING.md, ARCHITECTURE.md. Repo-specific gate, not propagated to templates/PROJECT_INIT. Layer-A policy tranche T4-a of the public-flip cap.

Add the docs-privacy gate (merged in the docs-privacy workflow) to the
CI-verdict policy so it becomes a decisional, required check:

- required-checks.json: docs-privacy joins both `required` (future Layer-B
  ruleset reads this to build required_status_checks) and `decisional`
  (read_ci_verdict now requires its SUCCESS to authorise a merge).
- CI_CD.md: flowchart node + edge, workflow table row, the drift:gate:required
  marker, and the defense-in-depth table.
- CONTRIBUTING.md / ARCHITECTURE.md: required-checks prose kept honest
  (fourth check -> fifth; docs-privacy listed among the decisional gates).

Repo-specific gate: docs-privacy scans docs/** for private piloting markers,
so it is deliberately NOT propagated to the adopter-facing templates or
PROJECT_INIT.
@David-BS David-BS merged commit 94ca9b7 into main Jul 8, 2026
4 of 5 checks passed
@David-BS David-BS deleted the t4a-docs-privacy-policy branch July 8, 2026 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant