Governance

Governance

RWS Confluence is the official publication authority. This repository is a workbench for analysis, drafting, proposal review, and controlled authenticated preview of committed content.

Source
docs/governance.md
Mode
rendered markdown

Governance

Authority

RWS Confluence is the official publication authority. This repository is a workbench for analysis, drafting, proposal review, and controlled authenticated preview of committed content.

The top-level confluence/ directory is the immutable, synced mirror. RWS-ARCH/ is the repository-local authoring source and may intentionally contain both a Confluence wrapper and an analysis or architecture interpretation for the same page. These are separate representations: neither hand-edits the mirror and neither changes Confluence publication authority.

Decision architecture/decisions/0010-authenticated-preview-representation-boundary.md supersedes earlier active restrictions on rendering committed RWS content in the authenticated PR preview. The preview is limited to approved reviewers, uses deployment-time credentials, retains only minimized CI evidence for the configured short period, and can be rolled back by disabling preview access or the affected route. The top-level mirror, snapshot wrappers, and analysis representations have separate duplicate lifecycles and do not authorize publication or write-back.

Write permissions by capability

CapabilityInitial write model
Mirror syncDirect commit only after validation and sync-report generation.
Generated metadataReport-only until confidence improves.
Analysis updatesPull request.
Proposal updatesPull request.
Comment triagePull request.
Publishing or stagingManual workflow only; no autonomous live publish.

Security gates

  • No live Confluence publishing in the repository foundation or mirror foundation
  • milestones.

  • No credentials or Basic Auth hashes in Git.
  • No public preview of real RWS content. Authenticated PR preview of committed
  • content is authorized by decision 0010.

  • No live full-space mirror snapshot until credential handling, RWS content
  • classification, retention, attachment handling, and preview access are reviewed.

  • No live deployment activation until runner, DNS, certificate, authentication,
  • and ArgoCD ownership are verified.

  • No authenticated preview activation until the deployment contract proves DNS/TLS
  • ownership, approved access control, secret delivery, credential lifecycle, auditability, cleanup evidence, and orphan reconciliation.

  • No Confluence staging write until activation proof approves content
  • classification, approved hosting and retention, staging permissions, version-conflict handling, attachment policy, audit trail, and rollback.

  • Preview evidence may contain committed content only in the authenticated,
  • short-retention CI artifact boundary defined by decision 0010. It must not contain credentials, tokens, request headers, or runtime-only data.