Four phasesCurrently: Phase 1

Roadmap

Where ITISYOU is going, in order. Deliberately date-free: a milestone ships when it has implementation, tests, and verification — not when a quarter ends. The progress page shows exactly where Phase 1 stands today.

Phase 1 In progress — current

Foundation / Browser Core

Make ITISYOU a real browser: engine integration, Tab Mode shell, workspace foundation, session recovery, local history, command palette, internal itisyou:// pages, deny-by-default permissions, and an AI runtime that exists only as disabled interfaces.

Intended outcomes
  • Browser launches and renders real HTTPS pages with the sandbox intact
  • Tab Mode with omnibox and navigation
  • Workspace, session, and history foundations (all local)
  • Permission policy boundary: deny by default
  • AI present but disabled — zero provider calls
  • This website deployed on Cloudflare
Phase 2 Planned

Browser Services / Workspaces / Data Systems

Grow the foundation into daily-driver browser services: full Workspace Mode, bookmarks, downloads, richer data systems — and the groundwork for alternative network modes.

Intended outcomes
  • Persistent Workspace Mode on top of the Phase 1 foundation
  • Bookmark and download management
  • Data systems with per-dataset boundaries
  • Network-mode groundwork toward proxy/Tor (with Phase 3)
  • Early extension-runtime exploration
Phase 3 Planned

AI / Privacy / Security / Advanced Platform

The trust phase: opt-in AI under explicit per-action grants, privacy and security hardening, and advanced platform capabilities — including Tor/proxy modes once they can be verified.

Intended outcomes
  • Opt-in AI with explicit, auditable, per-action access — never silent
  • Tor / proxy network modes (no anonymity claims until verified)
  • Privacy and security hardening passes
  • Advanced platform capabilities
Phase 4 Planned

Production Hardening / Cross-Platform Release / Installers

Ship it: production hardening, cross-platform verification on Linux and macOS, signed installers, and update infrastructure. This is when the downloads page becomes real.

Intended outcomes
  • Security review and performance hardening
  • Linux and macOS builds verified (not just architecture-ready)
  • Signed installers with real, published checksums
  • First public release
Why no dates?

Roadmap dates on pre-1.0 projects are usually fiction, and stale fiction is worse: a "Scheduled: Q3" badge that slides past its quarter quietly becomes a broken promise. We publish order and scope, and we publish verifiable progress instead of deadlines.