📁 Big Upgrade: Project Documents, Reimagined

We’ve just shipped a solid round of updates across Project Documents, focusing on the Explorer, the Document Register, and how files move between the two. The goal here was simple: make document control faster, clearer, and way less painful on real projects. 💪 ⸻ Explorer: Now a Proper CDE Explorer is no longer just a place to dump files. It’s now the working CDE, where documents live, change, and get prepared for issue: • Cleaner, tighter UI (less noise, easier scanning) • Clear status indicators so you can instantly see what’s: • Unregistered • Registered • Updated and ready for a new revision • Better bulk selection so real-world uploads actually work • Clear separation between “this exists” and “this is controlled” Explorer is now where the work happens. ⸻ Document Register: Clean, Controlled, Trustworthy The Document Register is now exactly what it should be: a simple register of what’s current and controlled. • Only shows the latest revision • No clutter from old versions • Clear flags when a newer version exists in the CDE • One clear action to push updates when you’re ready Older revisions still exist — they’re just where they belong (in context, not in the table). ⸻ Promote to Register (Powered by KAI 🧠) This is the big change. You can now Promote files to the Document Register directly from Explorer, using KAI to extract metadata from drawings automatically. What this means in practice: • Upload files first (no forced admin upfront) • Select one file or many • Let KAI read the title block and pre-fill: • Document number • Title • Discipline • Revision • Status • Set • Review, tweak if needed, then promote The same flow applies when a new version arrives — you’re prompted to Push New Revision, not forced into it. No accidental overwrites. No silent changes. ⸻ Revisions That Make Sense A key principle behind this update: Versions live in the CDE. Revisions live in the Register. • Uploading a new version does not automatically change the Register • You’re clearly shown when an update is available • You decide when that update becomes the new issued revision • Bulk revision pushes are supported This keeps control with the project team, where it belongs. ⸻ Why this matters This brings Deep Space much closer to how projects actually work: • Consultants can upload and prepare files • Builders control what’s issued • Everyone can see what exists vs what’s current • Registers stay clean • Admin time drops dramatically More refinements coming, but this update lays the foundations properly. As always — feedback welcome.