Governance

Authority

RWS Confluence is the official authority for published Confluence content. RWS-ARCH/ is the repository-local authoring and validation authority. The Confluence cache is operational state and owns neither source class.

Cache boundary

• Real Confluence bodies, page inventories, comments, attachment payloads, and

sync reports are not committed.

• Local cache content lives only under ignored .cache/confluence/.
• Deployment cache content lives on a PVC and is reconstructable from

Confluence; it is not a backup or source of truth.

• Cache refresh is GET-only, dynamically discovers INFRAARCH, fails closed at

its page cap, publishes atomically, and retains the last good generation after a failed refresh.

• Only sanitized public artifacts are served under /runtime/confluence/.

Private XHTML is never mounted into nginx's public root.

• Public cache import accepts only a complete, validated, inert snapshot from

one origin and never creates private XHTML. Preview and main caches remain independent operational state.

• Authored conclusions should cite stable Confluence page IDs and observed

versions when freshness matters.

Secrets

• Local credentials are delivered through the

rws-confluence-architecture profile.

• Deployment credentials are delivered through a Kubernetes Secret mounted only

into the sync worker.

• Tokens, credentials, headers, private cache contents, and environment-specific

values must not enter Git, browser responses, logs, screenshots, or CI artifacts.

• Portal cache controls are authenticated and authorized by the deployment. The

static application implements no OIDC logic and reports deployment 401 and 404 responses without disguising them.

• Confluence shell and artifact responses are private and no-store; a

content-addressed snapshot path does not bypass access checks.

Writes

The cache producer never writes to Confluence. Confluence staging or publication automation is outside the current system and requires a separate reviewed design covering authorization, version conflicts, audit, and rollback.