The maintainer applied the platform layer, World0 admission policy and projects; verify-isolation.sh passed every guardrail, RBAC-negative, admission dry-run and cleanup check. Its three project failures were a script defect (destinations and the empty cluster whitelist were printed together as "[]"); check them separately. Ignore local result files, add docs/BACKLOG.md with break-glass membership and the storage re-probe, and record leaving Argo's default project unrestricted as an accepted risk. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.5 KiB
1.5 KiB
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 |
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. |