You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Project Wharf is the strongest architectural core in this portfolio, but it should be judged by trusted-core rigor rather than by broad completion percentages.
7
+
8
+
* The offline-controller / online-runtime split is coherent and strategically strong.
9
+
* The database policy engine, integrity path, and mooring model are the highest-value differentiators.
10
+
* The release story still depends on deeper fail-closed verification and clearer crypto-release posture.
11
+
12
+
== P0 Release Blockers
13
+
14
+
* [ ] Prove and test fail-closed handling for unrecognized or administrative SQL statements across the DB policy path.
15
+
* [ ] Expand database-policy tests beyond smoke coverage so the trusted core is exercised more realistically.
16
+
* [ ] Resolve the Ed448 audit dependency or standardize deployment guidance around the audited ML-DSA-only path.
17
+
* [ ] Reconcile the 95%-complete style language with the thin current test surface.
18
+
19
+
== P1 Hardening Work
20
+
21
+
* [ ] Add load, fault-injection, and concurrency testing for mooring, integrity verification, and DB proxying.
22
+
* [ ] Add explicit release criteria for the trusted core.
23
+
* [ ] Publish a tighter operator guide for what is supported, experimental, or crypto-audit dependent.
24
+
25
+
== P2 Productization
26
+
27
+
* [ ] Treat Wharf as the backbone of the live stack once the trusted core is proven.
28
+
* [ ] Use WordPress deployments as real operational validation instead of broad architectural percentages.
29
+
* [ ] Keep the scope centered on runtime hardening rather than accumulating adjacent infrastructure features too early.
> NOTE (2026-03-30): Read this dashboard as an architectural tracking view, not as a release gate by itself. For current blockers and deployment posture, use `ROADMAP.adoc` as the authoritative readiness document.
0 commit comments