🛰️ DEV LOG: MAY 9, 2026

PROJECT PHASE: 10.0 (Stability & Compliance)

STATUS: Deployed

VERSION: 0.1.15

🗃️ Stability & Compliance

This update finalizes the Sanctuary OS governance pipeline, bringing critical stability to the Compliance toolset and refining the UI/UX across the Mod Dossier and Architect Hubs. We’ve eliminated ambiguous badging, repaired layout crashes, and fully standardized the handling of Malware/Explicit flags.

🛡️ Governance & Security Updates

Feature / Optimization	Engineering Impact
Manual Threat Flag Upgrade	The SeniorArchitect Manual Flag modal now utilizes a fully integrated CustomComplianceSelect dropdown, completely replacing the outdated native HTML <select>. This provides a consistent, glass-morphism aesthetic aligned with the OS.
Malware Dashboard Relocation	The "Malware Reported" box has been removed from the standard Architect Hub dashboard. Malware and Explicit flags are now exclusively monitored via the Senior Architect Hub, reinforcing the separation of administrative privileges.
Global Compliance Search(Senior Architect Hub)	The Senior Architect "Compliance Oversight" tab now includes a "Global Registry Search" feature. This allows SA users to query the entire database and reassign compliance tiers to previously "Clean" (Tier 0) mods directly from the Command Hub.
Bidirectional Beta Bug Fixed	Resolved a critical logical flaw where establishing a "Beta" relationship in the Hubs incorrectly created a bidirectional link in the Supabase registry. The relationship is now strictly unidirectional (Parent = Core/Stable, Child = Beta).

👮 Security & Compliance Additions

Feature / Optimization	Engineering Impact
Guest Mode Restrictions	Unauthenticated (Guest) users are now restricted from initiating cloud uploads or global actions to ensure database integrity. Submitting metadata corrections and flag reports to the Architect Hub is now blocked. Uploading Blueprints to the cloud and Mass Ingestions are disabled. The ability to follow Masons is fully gated behind a login check. The submitLabReport protocol is completely disabled for Guests. Note: Local metadata overrides still function normally.
Malware Interception & Secure Shred	Integrated the compliance_tier tracking into the application's physical mod compilation cycle. Tier 3 (Malware) mods are now automatically intercepted upon Radar Sweep completion. Added an unclosable "Critical Danger" modal that prevents user operation until the threat is neutralized. Implemented the SECURE SHRED protocol directly within the Malware alert to perform multi-pass destructive overwrites of the malicious files via the rust backend, keeping Sanctuary OS safe.
Architect Hub Refinements	Standardized the compliance tier selector by removing the MALWARE classification option from the general Architect Hub, securing this high-level threat protocol exclusively for Senior Architects.

🔐 Sandbox Implementations

Feature / Optimization	Engineering Impact
Marketplace Filters	Explicit and NSFW (18+) mods are now strictly hidden from the Marketplace for all users, completely bypassing the mature toggle.
COMM-LINK (Global Feed)	Transmissions made by Masons flagged with Adult or Explicit content tiers are now scrubbed from the global COMM-LINK feed.
Command Center Scrubbing	Explicit/NSFW mods no longer count towards or display in the "Verified Safe" or "Broken" categories on the Command Center Dashboard. They only appear in "Your Collection" (Vault).
Upload Hard-Blocks	Cloud Blueprints: Any Blueprint synced to the cloud will automatically strip out references to NSFW and Explicit mods. Lab Reports & Bug Reports: The "Flag," "Submit Corrections," and "Send to Lab" buttons in the Mod Dossier are now disabled for Explicit/NSFW mods, preventing their metadata and logs from being pushed to the global servers.

🎨 UI & UX Polish

Feature / Optimization	Engineering Impact
Mod Dossier Header Overhaul	Completely restructured the Flexbox layout of the Mod Dossier header. The Mod Title will no longer aggressively wrap into a single vertical column when multiple admin action buttons are present. The header now dynamically adjusts and wraps elements elegantly on smaller viewports.
Lexicon Iconography Repairs	Fixed garbled artifact characters (e.g., dYsc, o) in the Mod Dossier action buttons by successfully migrating them to standardized text symbols and lexicon tags (+ MANUAL FLAG, 🚩 FLAG, ✕).
Badge Consistency (Stable vs Beta)	Integrated badge_stable and badge_beta into the global en-sanctuary and en-default lexicons. The Addon-Drawers will now properly identify the Core Mod as STABLE and the offshoot as BETA, rather than tagging both as Beta.

📖 Lexicon Updates

Feature / Optimization	Engineering Impact
status_broken_hover	"This Artifact is currently flagged as Broken." (en-sanctuary.json) "This Mod Is currently flagged as Broken." (en-default.json)
Badge Consistency (Stable vs Beta)	Integrated badge_stable and badge_beta into the global en-sanctuary and en-default lexicons.  The Addon-Drawers will now properly identify the Core Mod as STABLE and the offshoot as BETA, rather than tagging both as Beta.

🐛 UI/UX & Bug Fixes

Feature / Optimization	Engineering Impact
Broken Mod Hover States	Added new lexicon entries (status_broken_hover) for both generic Mod Cards and Sanctuary specific contexts. Mod badges on the Mod Card now feature an interactive cursor-help tooltip displaying the new broken lexicon strings whenever a Mod or Artifact is flagged as completely Broken.
Beta vs Stable Prioritization:	Radar Sweep compilation logic has been updated to automatically sort internal flavor lists. Mod versions with the beta relationship type are pushed to the end of the list. This guarantees that when users interact with the parent folder (e.g., clicking the add button on the card), they default to the Stable version instead of inadvertently equipping Beta/WIP artifacts.

🔧 Under-The-Hood Maintenance

Feature / Optimization	Engineering Impact
TypeScript Integrity	Added compliance_tier?: number; to the ModData interface within shared.tsx to prevent Vite development server crashes during hot-reloads.
Zustand State Access	Successfully imported userRole into the ModDossier to resolve compilation errors and ensure proper rendering of administrative buttons based on the active user's permissions.

🌐 Website Update

Feature / Optimization	Engineering Impact
Mason UUID Form	The Mason UUID Form has moved from the Discord to the website at https://www.sanctuaryos.co/mason-uuid-request Work is underway integrating the Forms into the OS.
Mason UUID Form	The Architect Intake Application has moved from the Discord to the website at https://www.sanctuaryos.co/architect-intake-form Work is underway integrating the Forms into the OS
User Guides	The User Guide has moved to the website at https://www.sanctuaryos.co/blueprints Work is underway integrating the Forms into the OS
Dev Logs	The Dev Logs has moved to the website at https://www.sanctuaryos.co/dev-logs Work is underway integrating the Forms into the OS
Support	Support will continue on the Discord Server. The backup support system on the website will be reserved for future Discord interruptions. Work is under way integrating a Support System into the OS.
Download Links	The Download Links have moved to the website at https://www.sanctuaryos.co/downloads
Fork Guide	The Fork Guide will be added to the website at a later date. The fork Guide is currently available at: https://github.com/Sanctuary-OS-Source-Code/SanctuaryOS

🚩 Compliance & Visibility Resolution

This section is to give the Citizen insight on the critical issue where "Explicit" mods were being improperly hidden from the Vault and aggressively quarantined by the system.

Fixed Explicit Mod Visibility (The "Hidden Collection" Issue)

Feature / Optimization	Engineering Impact
Root Cause Analysis	Previously, when a mod was flagged as Adult/NSFW, the system assigned it a database status of 'blacklisted'. The OS backend's sync_security_definitions protocol interpreted any mod with a 'blacklisted' status as Malware. Consequently, the OS physical backend would abruptly move the Explicit mod out of the active Vault directory and into the Quarantine folder. Because it was removed from the physical directory, App.tsx's scan_bunker could no longer see the file, resulting in it being completely "hidden" from the standard Collections view.
Resolution	Updated the malwareData query in App.tsx. The system now strictly relies on mods.compliance_tier === 3 to identify Malware, explicitly decoupling it from the legacy 'blacklisted' status. Explicit (Tier 2) and NSFW (Tier 1) mods will no longer be targeted by the sync_security_definitions purge, ensuring they remain visible in the local Collection. Note: Citizens will need to click "Restore" from the Quarantine zone to move their previously affected mods back into the Vault.

In addition the following have also been implemented to accommodate the new Mod Compliance table.

Feature / Optimization	Engineering Impact
Malware SECURE SHRED Protocol	Confirmed that the MalwareAlert modal triggers appropriately when a Tier 3 compliance_tier is detected. The system now successfully intercepts the user with an unclosable "Danger" modal, enforcing the SECURE SHRED action via the Rust backend's purge_quarantined_file routine.
Senior Architect Upgrades	Polished the UI formatting for the + MANUAL FLAG module added in the previous session, ensuring it displays properly at the bottom of the Compliance Oversight panel. Confirmed that the upsert mechanism for manual registry insertions appropriately maps DNA hashes to compliance tiers.