Files

SysAdmin 0a0075ce66 docs(naming): adopt OS / Enhanced product-line framing + align with existing repos

Two product lines, named to make scope obvious to buyers:
- 🔒 SilverMetal OS — we ship the operating system or ROM
  (Linux, Pixel, Samsung-unlocked, Motorola-unlocked)
- 🛡️ SilverMetal Enhanced — we harden the OS the device already runs
  (Windows, macOS, iOS, generic Android)

Repo alignment:
- SilverVPN already exists as a SilverLABS product (server + MAUI client +
  Linux client + tunnel service). stack/vpn/ is now an integration pointer
  rather than a re-scaffold; per-platform READMEs reference it.
- SilverApple is deprecated; SilverMetal Enhanced — iOS supersedes it.
  Migration step added as roadmap milestone 3I.1.
- SilverDROID name clash explicitly noted as unrelated (it's the SilverSHELL
  AppStore Android client, not an Android ROM).
- SilverChat may overlap with SilverVPN.Client.Chat; alignment decision
  added as roadmap milestone 1.1.1.

Roadmap restructured: phases now track the OS/Enhanced split.
Platform matrix re-sectioned and decision flowchart updated.
README rewritten around the two-product-line framing.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-04-25 03:30:45 +01:00

2.5 KiB

Raw Blame History

SilverMetal — Android

Status: Phase 2 (planning, post-Linux v1)

Android coverage spans both SilverMetal product lines:

🔒 SilverMetal OS for devices where we ship a custom ROM (Pixel, Samsung-unlocked, Motorola-unlocked)
🛡️ SilverMetal Enhanced for users keeping their existing Android (any vendor, no bootloader unlock required)

See ../docs/platform-matrix.md for honest per-tier pros/cons.

Sub-flavours

🔒 SilverMetal OS — Pixel (Tier B)

GrapheneOS-fork on Pixel hardware. Verified boot we control, hardened kernel, app sandboxing enforced. Full SilverLABS Stack preinstalled. Phase 2.1.

🔒 SilverMetal OS — Samsung (Tier C)

LineageOS / DivestOS-fork on Samsung models with unlockable bootloaders. Phase 2.2.

🔒 SilverMetal OS — Motorola (Tier C)

DivestOS / LineageOS-fork on supported Motorola models. Phase 2.3.

🛡️ SilverMetal Enhanced — Android (Tier D)

For users keeping their existing OEM Android (Samsung locked-bootloader, OnePlus, Xiaomi, hand-me-downs, etc.). Stack apps + work-profile-based hardening config; no bootloader changes, no warranty void. Phase 3A.

Directory layout

To be populated as each sub-flavour is built. Initial structure planned:

android/
├── os-pixel/        # 🔒 GrapheneOS-fork build config (Phase 2.1)
├── os-samsung/      # 🔒 Samsung ROM build configs (Phase 2.2)
├── os-motorola/     # 🔒 Motorola ROM build configs (Phase 2.3)
├── enhanced/        # 🛡️ Generic profile installer + work-profile config (Phase 3A)
└── shared/          # Common build infra, signing, OTA

Verification gates

OS tiers: verified boot rooted in our key (Pixel only); reproducible builds; OTA signed and rollback-tested
Enhanced tier: Stack apps installed and functional; work-profile isolation verified; no bootloader changes detected
All tiers: telemetry-leak test (no Google services contact unless explicitly opted in by user); SilverVPN integrated as default VPN

Upstream we depend on

GrapheneOS — Pixel OS base
LineageOS — Samsung / Motorola OS base
DivestOS — additional hardening patches
AOSP — root upstream
SilverLABS/SilverVPN — MAUI Android client (existing)

Note on naming

The existing repo SilverLABS/SilverDROID (SilverSHELL AppStore Android client) is unrelated to this Android flavour despite the similar name. They serve different products.

2.5 KiB Raw Blame History