# Galaxy Project Dashboard 0.1.0 ## Public source edition An offline-first Electron desktop prototype for organizing projects and local files through a Three.js galaxy, list views and searchable metadata. **This download is source code, not a Windows executable or installer.** Windows 10/11 on x64 hardware is the intended desktop target. The ready-to-run Windows ZIP was not supplied for this website listing and is not included. It does not run by opening index.html or inside the Getting Oriented website. ## Build and run Install Node.js 24 or newer. Extract the ZIP, open a terminal in the extracted `galaxy-dashboard` folder, then run: ```text npm ci npm run build npm start ``` The first installation requires internet access and downloads dependencies, including Electron. After installation and a successful build, the application runs locally. No API key, account, subscription or AI credits are required. The application blocks HTTP, HTTPS and WebSocket requests in this version. If PowerShell blocks npm.ps1, use `npm.cmd` in these commands or use Command Prompt. Do not change system security policies just to launch this prototype. Developer commands: ```text npm test npm run test:smoke npm run package:win ``` `package:win` builds an unpacked, unsigned Windows distribution under `release`; it may download the pinned Electron runtime. It does not create an installer or a ZIP. No macOS or Linux release is offered. Linux was used for earlier development checks, but Windows-specific integration still needs acceptance testing on Windows. Do not bypass operating-system warnings on our assurance. ## What to try 1. Explore Build & explore, then Getting Oriented Arcade, then CENTURY. 2. Press Ctrl+K, search for `Maze demo`, and open its inspector. 3. Create a project, add a state, tags and a next action. Leave progress blank when a percentage would not be meaningful. 4. Link a small disposable folder. The app indexes names, paths and metadata in place; it does not automatically import your computer's files. 5. Visit Media observatory for bundled synthetic image and video examples. 6. Export a metadata backup from Settings before experimenting with restore. The public examples contain no personal project history or internal business notes. Arcade entries describe public projects; the games themselves are not bundled. All example regions are editable. Related objects starts blank for each new object. To add a relationship, search for an object in your workspace and choose Add. Only deliberately added links are saved; existing links remain visible when you edit an object. Use Remove to unlink an object. ## Feature boundaries - UUID-based hierarchy, editable domains, project metadata, tags, related objects, nine states and optional progress. - SQLite persistence and FTS5 search over names and metadata, not document contents. Matching is token-prefix based, not typo-tolerant; results cap at 60. - Folder linking and manual rescanning, directory creation, OS open/reveal, and separate confirmed disk rename, same-volume move and recycling actions. - Recoverable workspace bin: removing workspace metadata does not delete its linked file. Disk recycling is a separate operation on the actual file. - Local media previews, muted hover autoplay, pinned controls and preferences. Codec support varies; some HEVC/MOV media may not play. - Imports cap at 5,000 items and 12 directory levels. Hidden directories, dependency folders and symbolic links are skipped. No filesystem watcher. - Galaxy detail caps at 60 nearby objects. Larger lists use 200-row increments. Dense real-workspace layouts need more testing. - External PowerShell/CMD launch on Windows, not an embedded terminal. The renderer cannot supply arbitrary shell command text. - AI connectors are disabled placeholders. No model calls, credential entry or autonomous AI file operations are implemented. - No installer, code signing, automatic updater, cloud sync, filesystem undo stack, configurable shortcuts or alternate theme. ## Protect your files This is an experimental file-management application, not a production-ready replacement for your normal file manager. Start with a disposable folder. Back up originals independently. Confirmed disk actions can rename, move or recycle actual files; metadata backups cannot undo those actions. On Windows, local data is stored under: ```text %APPDATA%\Galaxy Project Dashboard\ workspace.sqlite Managed workspace\ Backups\startup.json Backups\pre-restore.json ``` Settings shows the precise paths. Metadata exports include local file paths, not linked file contents. Treat exported backups as private. Only restore backups you trust; restore replaces current metadata after confirmation and saves a pre-restore snapshot. Startup snapshots are overwritten at startup, so export named backups for longer-term retention. A backup moved to another computer does not transfer or remap its linked files. For an isolated test workspace, set `GALAXY_DATA_DIR` to an absolute temporary directory before launch. Do not point two running versions at the same data. ## Verification and changes in this edition The original supplied README reports six core tests and sixteen Electron workflow checks passing on Linux, plus a cross-built Windows package. These are prior development reports, not independent validation or Windows results. This public edition replaces personal starter context with public/generic examples and revises documentation. It excludes the original compiled output, source maps and QA captures, which could retain the old context. It retains source, the dependency lockfile, test scripts, synthetic sample media and third-party notices. Build locally to produce matching application files. The website's packaging script verifies the download contents and checksum. The six supplied core tests were rerun for this edition. Electron UI checks, a fresh full desktop build and native Windows execution have not been rerun for this website addition. No independent security audit has been performed. ## Architecture - `src/core`, `src/data`: typed hierarchy, SQLite, search, settings and backups. - `src/filesystem`: local indexing and controlled disk operations. - `src/galaxy`, `src/app`: Three.js navigation and React interface. - `src/search`, `src/settings`, `src/media`: search, preferences and previews. - `src/terminal`: fixed native terminal launchers. - `src/connectors`, `src/security`: disabled AI contracts and input validation. - `electron`: isolated renderer, narrow preload API, validated IPC and dialogs. The renderer uses context isolation and sandboxing with Node integration off. These are implementation choices, not a guarantee that the application is free of vulnerabilities. See THIRD-PARTY-NOTICES.txt for dependency notices.