Settings → About
The last regular entry of the rail. The rail entry is About; unlike the other pages it has no header and no subtitle, only a centred brand card around the animated ∞ orb, titled Mnemosyne OS, with the eyebrow Infinity Edition and the tagline A spatial cognitive OS. Every thought has a place.
Nothing on this page is a setting, with one exception: the hidden gesture that unlocks the Developer page, described at the end.
Version and Core Engine
Two cards. Version shows the app version with its edition suffix, for
example 1.4.4-infinity. Core Engine shows the version of the memory
engine the app runs on. Both read … until the app has answered; the
numbers come from the running app, never from a hardcoded value.
These are the two numbers to quote when you ask for help on the community channels.
Runtime
Once loaded, three cards name the runtime: Electron, Node.js and Chrome, with their versions. The labels are shown in English in every language.
Architecture
A list numbered with prime numbers (2, 3, 5, 7):
- Prime-stride cognitive sampling
- Multi-vault semantic dream synthesis
- Spatial widget canvas
- Encrypted local-first storage
The last item describes the direction of the storage design. Whether your vaults are actually encrypted on disk depends on the state of the Encryption at rest card under Backup & Restore, which on most shipped builds is not open yet. Check that card, not this list.
Under the list, a monospace line names your platform and architecture, for
example win32 · x64.
Community links
Five links, opened in your system browser: Reddit, Discord, X, YouTube and LinkedIn. The names are shown in English in every language.
Footer
Private — All rights reserved and Crafted with prime numbers and dark voids.
Unlocking developer mode
The Version card hides the switch. The pattern is the one Android uses for its build number.
- Tap the Version card 8 times
Click the Version card repeatedly. Pause more than 2.5 seconds between two taps and the count starts over.
- Watch the countdown
From the fourth tap onward, a monospace line under the card counts the taps left: 4 taps to developer mode…, then 3, 2, 1.
- Land on the Developer page
On the eighth tap the line reads 🛠️ Developer mode unlocked for four seconds, and the Settings window jumps to the Developer page. A new rail entry, Developer, appears at the end of the rail.
Tapping the card again once the mode is on says Developer mode is already on. While it is on, a wrench line on the About page reminds you: Developer mode on — see the Developer tab. The state is saved on your machine and survives a restart.
Developer
The Developer page exists in the rail only while developer mode is on. Its subtitle sets the contract: Demo & testing toggles. Off by default; these never affect real data, on-chain state, or other users. Every switch is a display or test aid; each is saved on your machine and every open window reacts to it live. All of them start off.
Simulate an unlicensed wallet (switch): Show the wallet as if it held no Engramm license — display only, to preview the license-request flow. Your real license, token and entitlements are untouched. Useful to see what a newcomer sees in the Wallet.
Keep the beta quest on screen (switch): Force the first-steps panel visible whatever its state. It normally retires at 5/5 — and silently on an install that was already finished, which is every dev machine. Display only; nothing is written.
Simulate a machine with no intelligence (switch): Draws the chat's first-run gate — no API key, no credits, no local model — on this already-configured install. It normally shows once and latches off forever, so no dev machine can ever see it. Display only; the real latch, keys and balance are untouched, and the local-model door still reports this machine's actual memory.
Show the feedback panel (switch): Keeps the small "how is it going?" panel on screen. It normally appears once, after three launches and two days, never to a licence holder, and retires the moment it is sent or closed, so no dev machine can see it. Display only: nothing is written, and closing it or sending brings it back on the next toggle.
Open a bug report (button Open): Opens the same panel the bug button in every window header opens, on this machine's real diagnostics. Its send button really sends.
Unlike the switches, the bug-report panel is the production one. Pressing send in it sends a report. In a window where nothing can answer, the button is disabled and the row reads Nothing is mounted to answer here, so no report can be opened from this window.
Show a gift celebration (three buttons): Raises the real panel that appears when a licence is airdropped or credits are granted. It normally needs something to actually arrive, so no dev machine sees it. Nothing is written and no balance changes. The buttons are Licence (an airdropped licence), Licence (bought) and Credits, the last one previewing a stated example amount rather than a reading of your balance.
Simulate a large backlog: Feeds the work card a pretend queue so it can be looked at without writing thousands of files. Every row it produces is marked as simulated. A number field (1 to 1,000,000, default 4000) followed by the word documents, and a Start button that becomes Stop. The simulation advances at about 0.6 s per file, with an index pass, and stops by itself when you leave the page.
Turn off developer mode, separated by a hairline: Hide these toggles again. Re-unlock by tapping the version in About 8×. The button Turn off developer mode hides the page and its rail entry at once; if you were on it, the window falls back to About.
Turning developer mode off hides the switches without resetting them. A simulation left on stays on, only out of reach. Turn each switch off before leaving developer mode if you want the app back to its real state.