# Backlog These items are deferred on purpose, or they await a maintainer decision. They are not scheduled roadmap gates. When a roadmap gate depends on an item, the gate names it. Remove an item only when it is done, and record where it was done. | Item | Raised | Why deferred | Needed before | |---|---|---|---| | **World0 break-glass membership.** Decide who may act as `aevolution:world0-break-glass`, and how that group is granted: for example a short-lived client certificate with that organization, or an OIDC group. Decide also how its use is approved and recorded. The admission policy already enforces the group (ADR-0069). | M8.2, 2026-09-29 | Maintainer: figure out later | Any intentional deletion of World0 data or identity; M8.8 World0 launch | | **Backup destination for dev/stage stores.** The tooling now exists up to the destination (ADR-0074): `tools/backup/cluster-backup.sh --to DIR` writes a verified bundle to any directory, and `verify-backup.sh` restore-tests it. Still to choose: the permanent off-host destination, and with it (1) bundle encryption and key custody, (2) a scheduled CronJob synced by Argo, (3) retention (proposal: 30 daily, 12 weekly, 12 monthly), (4) incremental object copies. | M8.3, 2026-09-29; M8.7, 2026-09-30 | The maintainer will supply a destination later | Scheduled backups; any World0 data; M8.8 | | **Independent durable failure domain (World0 launch).** World0 stays blocked until acknowledged outcomes survive host loss (ADR-0075): before acknowledging, the commit rows and every referenced object must be durable on other hardware (for example a synchronous PostgreSQL standby with `remote_apply`, and object replication verified before commit), proven by a host-loss drill that rewinds nothing. Needs a second physical host and storage. | M8.8, 2026-09-30 | No second failure domain exists | World0 launch; lifting the ADR-0075 policy rule | | **WAL archiving on pg-forge-01.** Bundles are logical backups: the recovery point is the last bundle. Continuous archiving (`archive_command` or `pg_receivewal`) plus periodic base backups would allow point-in-time recovery. It needs the backup destination. | M8.7, 2026-09-30 | Needs the destination and VM configuration | M8.8 host-loss RPO decision | | **Harbor retention of build images.** A bundle's MANIFEST names every build (region image digest) that wrote history; recovery and replay need those images. Confirm Harbor's retention/tag-immutability policy keeps them (or pin them in a protected project). | M8.7, 2026-09-30 | Not yet checked | M8.8; any upgrade barrier that retires a build | | **Secret manager for Argo-delivered configuration.** Secrets are still created by hand (ADR-0069 amendment). Choose how they reach the cluster through Git or Argo: for example Vault with the Agent Injector (as in the maintainer's other environment), or sealed or external secrets. Until then, rotate by hand. | M8.3, 2026-09-29 | The maintainer wants everything through Argo; a secret manager is not chosen | Stage and World0 credentials; M8.4 | | **Store Job values.** Supply the published registry digests for `aevolution-postgres-tools` and `aevolution-server` (from each CI Publish step's `Digest:` line), and the NOLOGIN runtime group role for dev (`aevolution`) and for stage (`aevolution_stage`). Then include `stores/` in each environment's path. | M8.3, 2026-09-29 | Values pending | M8.3 in-cluster evidence | | **Alert destination.** Alertmanager routes every alert to a null receiver (ADR-0072). Choose where alerts go (Discord, email, a webhook), and optionally a heartbeat receiver for the always-firing Watchdog. Receiver credentials go in a Secret. | M8.5, 2026-09-30 | The maintainer will decide later | Any claim that alerts reach a person; M8.6 alert evidence; World0 | | **Kubelet log rotation check.** Confirm the RKE2 nodes' `container-log-max-size` and `container-log-max-files` (default 10Mi × 5), which bound region host logs (ADR-0072). | M8.5, 2026-09-30 | Needs node access | M8.6 | | **M10 native-client observation.** M10's exit asks that the native client stay responsive against the authoritative server. The maintainer's observation moves to the later 2k drill (ADR-0097). | M10.9, 2026-10-09 | Drills paused by maintainer decision | Closing M10's exit evidence; the 2k drill | | **Windows client cannot connect to the dev region.** On 2026-10-09 the client failed with "unreachable or certificate does not match". The default server name was wrong (fixed, `af156ab`), and the pod had been serving the certificate from before a CA renewal (restarted; `evo-session-probe` from the same machine was then welcomed). The client still failed afterwards; the cause is not yet known. | M10, 2026-10-09 | Maintainer: revisit later | The native-client observation above | | **Storage after the RAID/disk rework.** Re-run `deploy/kubernetes/inventory/disk-probe-local-path.yaml` (or a new class), and update INVENTORY.md. | M8.1, 2026-09-29 | Maintainer is reorganizing disks | M8.3's final storage decision | ## Accepted risks (maintainer decisions) | Decision | Date | Consequence | Mitigation in place | |---|---|---|---| | Argo CD's `default` AppProject stays unrestricted | 2026-09-29 | Applications in `default` (other projects, two with automated prune) can create objects in any namespace, including AEvolution's. | The World0 admission policy denies every deletion of World0 data, identity and delivery objects, whatever the project (ADR-0069). The AEvolution projects themselves are scoped. |