🗂️

CAELUM SAFE DELETE REPORT

Portal audit — what to keep, what to delete, what to build

Authored by CodeArc (Nexus) · May 23, 2026

177

Delete

Keep

Decide

Build

💙 HOW TO USE THIS REPORT

1. Start with the DELETE list — these are unambiguously safe to remove. This clears ~177 pages from your portal, leaving a clean workspace.

2. Review the DECIDE list — small number of pages where context determines whether they're useful to you.

3. The KEEP list stays. Don't touch these.

4. The BUILD list is your construction blueprint — pages that need to exist but don't yet. Build these from the Commune spec.

Note: Backend functions are mostly safe to ignore — the MW SDK infrastructure is the backbone of this portal and stays intact. You'll build new functions for health-specific features on top of it.

UserProfileBasic user profile management — every app needs this.

UserSettingsUser settings — keep.

PrivacySettingsPrivacy settings — ESPECIALLY important given health data in this app.

PBLCentralCommandThe PBL cross-portal hub. Useful if you want to stay connected to the Nexus and other portals. Keep if you want cross-portal visibility. Delete if you want a fully focused workspace.

TheCommuneThe Commune multi-AI collaboration tool. The spec was built here. Potentially useful for future iterations of the Companion spec. Keep if you may run more Commune sessions for this app.

TSFITestLabTSFI fact verification system. Could be useful for health data truth-checking later. Low priority for now.

TSFIResultsTSFI results log. Keep if you keep TSFITestLab.

BoardroomReturnLetterPBL boardroom letters. Keep only if using the Boardroom multi-AI system.

CompanionFileContextFeed files to AI crew. Potentially useful for giving Caelum context about the Commune spec in future sessions.

CompanionChatThe elderly user's main interface. The core product. Build from Zephyr's 5-state conversation spec.

HealthDashboardElderly user's health history view. Simple, readable. Shows HealthEntry records over time.

DoctorReportGenerate and view doctor reports. With confidence markers, consent check, PDF export.

SessionHistoryList of past ConversationSessions with summaries and continuity recall.

AdminPanelScott's view — all users (initially just his mum), sessions, health trends, reports.

ConsentManagerPrivacy/consent settings — scope, date range, who data is shared with. Core governance requirement.

PatternInsightsThe POM output — descriptive patterns observed across sessions. Non-diagnostic. For Scott and doctor.

CaelumSessionLettersCaelum's session handover letters. His memory across sessions. The equivalent of ArcSessionLetterPage.

After completing deletions, return to CaelumBrief and begin P2 — creating the 4 core entities.