# Direction

### *what's shipped, where we're heading.*

---

## what's already in the platform

The current generation of Syn_OS — **v60 "Sun & Salt"** — is the product of a sustained, multi-year build. The system that exists today carries:

- A custom Linux kernel with deep Rust integration and a deliberate system-call surface for AI/observability.
- A local AI daemon — codename **ALFRED** — modeled after the structure of a biological brain.
- The **GRIMOIRE** gamified training platform with a hand-authored lab corpus, faction system, narrative quests, and a long arc from novice to sovereign operator.
- An integrated game engine surface for the parts of the user experience that benefit from one.
- A distributed mesh capability for those ready to extend the system across multiple machines.
- Post-quantum cryptography woven through the trust toolkit.
- A self-healing build pipeline producing signed releases with verifiable supply-chain provenance.

The work to get here was coordinated across many named campaigns, each adding a load-bearing piece to the platform. The compounding effect is what v60 represents.

---

## what's coming

Syn_OS is heading into a phase of **public release**. The platform has been validated internally for long enough; the next chapter is opening it to the practitioners we've been building it for.

Broad themes, in rough order of when they mature:

- **Public-facing ISO releases** — the GRIMOIRE training image and the AI-research variant, signed and verifiable, distributed through channels suited to a serious cybersecurity audience.
- **Cohort programs** — multi-tenant deployments for classes, clubs, security teams, and training programs that want a real platform under their curriculum.
- **Deeper AI augmentation** — the companion daemon does its job today; we have a long list of ways it could do more.
- **Continual GRIMOIRE content waves** — new labs, new boss contracts, new narrative arcs, new factions over time. The world deepens.
- **Easier mesh adoption** — the distributed parts of the platform have power; we're working on the parts that make them feel inevitable rather than effortful.

We don't ship a public roadmap with dates. Calendars lie, and we'd rather be honest. The directions above are real. The cadence at which they arrive is whatever the work requires.

---

## the long arc

The end-state we're moving toward is a platform where the operator owns their infrastructure, their intelligence, and their future — not in a slogan, but **mechanically, cryptographically, architecturally**. The pieces are there. The work is in fitting them together with the polish, the trust, and the longevity that an operating system deserves.

We are not building a product. We are building **infrastructure for sovereignty**, with the long-term operator community in mind.

The roadmap reflects that.

---

## what isn't on this roadmap

The internal Operator image's feature trajectory. It exists. It evolves alongside the public roadmap. It is not for public distribution and is not part of this document by design.

Specific dates. Specific version numbers for things that haven't shipped yet. Promises that read better in marketing than they do six months later. The work happens at the pace it happens.

---

## how to follow

Watch this repository. When the chapters change, the documents change with them. The work is the work. The story will keep updating as it unfolds.
