The canonical methodology markdown — the firm's core IP and the S5 canon — exists as un-versioned files on Anton's laptop. A single device loss destroys the asset the entire suite operationalizes. Mitigation is trivial (private git repo + versioning discipline) and overdue; this is the cheapest-to-close highest-stakes risk on the register.

Roughly 10GB of client engagement audio recordings sit unencrypted, containing personal data of identifiable client staff. This is a live GDPR exposure (storage without adequate technical measures) that could poison the trust positioning of a firm selling governed AI transformation. Needs an immediate encrypt-or-delete pass plus a retention policy.

Suite direction is fragmented across stale vv-ops prose and a flat 72-row capability-ask registry with no sequencing, dependencies, or capacity model. For a 2-person firm this means prioritization happens implicitly in whoever's head is active — precisely the S3 failure the VSM analysis predicts. The fix and the S3 build-out are the same workstream: the roadmap should be the first artifact managed in the S3 tooling.

operate currently checks only for a valid session, not roles/permissions: 15 server actions execute without authorization checks. Acceptable for a single-operator playground, unacceptable the moment a client or second user touches a deployment. Must be closed before any client-facing deployment of Transform.