FAQ
What is Syn_OS?
Section titled “What is Syn_OS?”The Synaptic Operating System — an Arch Linux derivative built almost entirely in Rust, with an AI-aware kernel (17 custom syscalls), a 160-crate workspace, post-quantum crypto, gamified cybersecurity training, and a distributed mesh layer for federated inference. The OS itself is the security product, not a tool collection on top of one.
Why the underscore?
Section titled “Why the underscore?”The underscore in Syn_OS is the synaptic gap — the cleft where electrical signal becomes chemical meaning. The OS is the gap. Always written with the underscore. Never SynOS, never synos in prose (lowercase only in filenames and crate names).
Is this real or is it vapourware?
Section titled “Is this real or is it vapourware?”It’s real. v60.0.0 “Sun & Salt” is on main. 160 Rust crates, 0 compile errors. 17 custom syscalls wired with full handlers and host tests. Three ISO profiles building from the same codebase. Public release of GRIMOIRE Public and GoodLife is gated on counsel review and cyber-liability binding, not on engineering.
Where can I download it?
Section titled “Where can I download it?”Public ISOs are not yet shipping; they are code-complete but blocked on:
- Domain registration (
lumossolutions.io) - Counsel review of EULA / ToS / MSA + the MIT vs LicenseRef-Proprietary licence split
- Cyber liability binding ($1M / $3M Tech E&O)
- Stripe production account (depends on LLC + EIN)
Star the GitHub repo and join Discord for build-day announcements.
How is GRIMOIRE Public different from Master?
Section titled “How is GRIMOIRE Public different from Master?”GRIMOIRE Public is the talent funnel: progressive-unlock training that produces operators. Master is the product LumOs sells to customers who need the actual weapon for actual work. They are built from the same codebase, audited together, and shipped by the same supply chain — but Curtain v3 makes the boundary between them mechanical, signed, and externally auditable.
GRIMOIRE Public cannot become Master no matter how far a player progresses:
- Syscalls 470–474 return
ENOSYSon GRIMOIRE - LLM federation is tier-isolated to GRIMOIRE peers
- Audit chain HMAC roots are separated
- Fragment Field IDS kernel-side detection is Master-only
- C2 framework binaries are scrubbed at build time
Is ALFRED an LLM wrapper?
Section titled “Is ALFRED an LLM wrapper?”No. ALFRED is a fusion engine that routes every event through four parallel processing paths and combines their outputs into a single decision vector. Path 1: traditional AI (decision trees, signature matching). Path 2: neuromorphic spiking neural networks. Path 3: quantum coherence collapse theory (Penrose-Hameroff Orch-OR). Path 4: TNGS / Edelman’s neural Darwinism. Plus a v53 MPS cortex.
LLMs (Ollama, Claude, OpenAI, Gemini, DeepSeek, llama-cpp) are backends the Python user-facing layer can use. They are not ALFRED.
What hardware do I need?
Section titled “What hardware do I need?”Minimum: x86_64 (Haswell+), 4 GB RAM, 32 GB storage, UEFI firmware. Recommended: 4+ cores with AVX2, 8+ GB RAM (16 GB for AI workloads), 64 GB SSD, UEFI + TPM 2.0 (for Curtain v3 attest), and a Tailscale-capable network.
The Salvage Yard quest in GRIMOIRE assumes you can reclaim 3-4 discarded laptops to build a personal mesh — the hardware floor is “can find a working laptop”, not “can buy a $2,000 GPU.”
Is the source open?
Section titled “Is the source open?”Mixed. The plan (pending counsel review) is a tiered licence model:
- Apache 2.0 for the kernel, brain crates, GRIMOIRE engine, ALFRED Rust daemon, Bevy plugins
- LicenseRef-Proprietary for the Master ISO, RaaS engine, Curtain admin tokens, FedRAMP/CMMC/SOC2 control evidence, and the federation root-signing infrastructure
The Lum0s-Solutions/Syn_OS GitHub repo is currently private; it goes public alongside the first GRIMOIRE Public ISO release.
Why post-quantum crypto already?
Section titled “Why post-quantum crypto already?”Because the migration window is now. Adversaries record encrypted traffic today and decrypt it later — “harvest now, decrypt later.” Anything sensitive enough to need encryption in 2026 is sensitive enough to need quantum-safe encryption in 2026.
Syn_OS uses ML-KEM (FIPS 203) for transport, ML-DSA (FIPS 204) for high-frequency signing, and SLH-DSA (FIPS 205) for long-lived release signatures. Hybrid mode pairs each PQC primitive with a classical one so neither alone is load-bearing.
What’s the deal with the consciousness language?
Section titled “What’s the deal with the consciousness language?”It is not metaphorical decoration. The kernel actually exposes a consciousness_state struct via syscall 469 (coherence, activity, mode, decision latency); ALFRED’s nine brain crates are wired into a real signal-processing loop by the brainstem; the Default Mode Network actually runs 30-second consolidation cycles when CPU load drops below 10%.
The vocabulary is borrowed from neuroscience because the architecture is borrowed from neuroscience. If you find the vocabulary off-putting, ignore it and read the Rust — the code is unambiguous.
How do I report a security issue?
Section titled “How do I report a security issue?”security@lumossolutions.io (PGP key in growth/development/docs/internal/eyesonly/governance/).
Public security policy lives at SECURITY.md in the GitHub repo (added in v41 Wave 9, replacing the earlier internal symlink).
What does the v60 status table actually mean?
Section titled “What does the v60 status table actually mean?”| Field | Means |
|---|---|
| 17/17 syscalls wired | All 17 custom syscalls have full handlers, copy-to/from-user paths, host tests. Not stubs. |
| 160 crates, 0 compile errors | cargo check --workspace clean across 160 active crates. |
| 8 Bevy plugins | All 8 plugins (Cutscene, Mindmap, RetroFilter, Cyberspace, SkillTree, FactionHQ, Rehoboam, Twin) are integrated into synos-bevy. |
| SLSA-3 reproducible | Cross-oracle build verification works today; SLSA-4 (two-witness) is queued behind provisioning the second build oracle. |
| FedRAMP / CMMC / SOC2 | Control maps are written and the daily ConMon collector runs. The audits themselves are gated on Big-4 kickoff (deferred until ≥$1M ARR). |
Who is building this?
Section titled “Who is building this?”Lumos Solutions, LLC — founded by Ty Limoges. SBIR / Defense track. Cybersecurity-focused, sovereign-AI-aligned, e-waste-conscious. The full LumOs Virtual Enterprise is an agent-orchestrated dev pod (CADevO + 20-agent society across 6 pods); the human work is structured around the agent society.
I have a question that’s not here.
Section titled “I have a question that’s not here.”Open an issue, drop it in Discord, or email info@lumossolutions.io.