diff --git a/projects.md b/projects.md
index fa392e7..bd6ab16 100644
--- a/projects.md
+++ b/projects.md
@@ -34,23 +34,3 @@ Linux distributions like Bluefin and more broadly the Universal Blue project are
 There are proposals in Fedora to implement bootable container images as an image mode for the operating system.
 
  * [Fedora change proposal](https://fedoraproject.org/wiki/Changes/OstreeNativeContainerStable)
-
-## What needs work?
-
-Broadly there are several areas where we haven’t yet reached our [goals](mission.md), and where you can help:
-
- * At present, bootable container images must be built from a specific base image despite it being a goal to use standard base images.
-
- * At present, we can only update a bootc enabled system with a bootable container image. It is not yet possible to use “bootc update” on a stock Linux system.
-
- * When using “bootc install” to update a non-bootc Linux system, it is not possible to roll back to that previous behavior.
-
- * The cryptographic trust chain is possible based on composefs, overlayfs, fsverity and UKI use to mount both application containers and the operating system bootable container images. However a working complete trust chain from hardware through to the app containers is not yet implemented.
-
- * When rebooting these image based Linux systems, all transient changes made to the optional overlay are lost.
-This would be confusing to a developer or someone trying to adopt these images.
-The behavior is different from the behavior of containers, where you can make changes to a running container, stop and  start that container without losing those local changes.
-
- * Currently when we deploy a bootable container image to a stock Linux system, without bootc already present, it is not possible to rollback. We should fix this.
-
- * Currently the tooling and the base images are limited to using RPM components in the container images. (bootc #468)