Preview Deployment Activation Proof

This document collects the evidence required by the Preview Deployment Ownership and Cleanup Contract (architecture/decisions/0005-preview-deployment-ownership-and-cleanup-contract.md) for the activation of authenticated preview resources.

Status: Preparation - This document outlines the evidence to be collected. Actual evidence gathering requires deployment capabilities that are currently blocked by Milestone 14 activation gates.

TASK-0301 now has a secret-free ownership package at publication/approvals/TASK-0301-preview-deployment-ownership.md. It records the current repository and MIT-vault facts for review, but does not activate preview deployment or approve real RWS content exposure.

Contract Evidence Requirements

1. DNS and TLS Ownership

• Main host: rws-arch-wb.moeken.eu
• Preview host pattern: pr-<number>.rws-arch-wb.moeken.eu
• Required evidence:
• Authoritative DNS owner identification for both host patterns
• Record owner labels or TXT markers when automation is used
• DNS rollback path for removing main and preview records
• TLS issuer/secret owner identification
• Certificate renewal process and lifetime
• TLS failure alerting mechanism
• TLS rollback or removal path

2. Authentication and Secret Delivery

• Required evidence:
• Approved access model naming the reviewer audience
• Credential issuance path description
• Revocation trigger specification
• Audit owner designation
• Denied-access evidence for main host and at least one PR preview host
• Allowed-access evidence for main host and at least one PR preview host
• Confirmation that credentials, Basic Auth hashes, private keys, kubeconfigs, and sealed secret material are not committed to this repository
• Reviewed platform secret delivery path (approved external secret or sealed-secret workflow)
• Credential scope limitation to portal and preview namespaces

3. ArgoCD, Labels, and Quotas

• Required evidence:
• Named ArgoCD applications or application sets owning main and preview resources
• Labels on every managed resource identifying:
• Service
• Environment
• Owner
• Source repository
• Pull request number for previews
• Cleanup policy
• Preview resources running inside reviewed namespace boundary or equivalent quota boundary
• Explicit pruning or TTL behavior specification
• CPU, memory, storage, object-count, and ingress limits definition

4. Cleanup Evidence and Orphan Reconciliation

• Required evidence:
• Cleanup evidence identifying:
• PR event
• Commit
• Preview host
• ArgoCD app or app-set entry
• Resources removed
• DNS state
• TLS state
• Credential state
• Evidence that closed and merged PRs have preview resources absent or intentionally retained under approved exception
• Orphan reconciliation output comparing live preview resources against Forgejo PR state and expected host labels
• Follow-up for failed cleanup with sufficient context to remove resources without exposing secrets

5. Rollback and Removal

• Required evidence:
• Ability to disable preview ingress while leaving static CI evidence artifact path intact
• Credential revocation proof
• DNS removal or route disablement evidence
• TLS cleanup verification
• ArgoCD sync suspension or app removal proof
• Confirmation that no preview host remains externally reachable after removal
• Emergency removal capability without editing mirrored Confluence source or committing credentials

Activation Proof Items to Collect

Before live authenticated preview activation, collect review evidence for:

1. [ ] DNS and TLS ownership for main and preview hosts
2. [ ] Denied and allowed authentication checks for the expected audience
3. [ ] Secret delivery and credential lifecycle review without repository secrets
4. [ ] ArgoCD ownership, labels, quota boundaries, prune or TTL behavior, and orphan reconciliation output
5. [ ] PR-close or PR-merge cleanup evidence for at least one representative preview
6. [ ] Rollback proof that removes or disables preview exposure safely

Reference Materials

• Contract definition: architecture/decisions/0005-preview-deployment-ownership-and-cleanup-contract.md
• Deployment examples: deployment/openshift/ (intentionally example-only, no live resources)
• TASK-028 completion: Deployment ownership and cleanup contract decision
• TASK-032: Confluence staging dry-run proof (fixture-only validation)
• TASK-039: Scoped Confluence sync activation plan

Next Steps

Upon preview access and Confluence staging gates being unblocked by human review:

1. Deploy preview resources using reviewed platform mechanisms
2. Collect evidence for each contract point listed above
3. Update this document with actual evidence and proof artifacts
4. Submit for review before real RWS content exposure or live preview sharing