Makes the physical behavior of the local machine visible under bounded, per-session privilege.
Connected systems
Shares Slicewrite's preference for bounded access and evidence-first interfaces.
SYS.03.03 / Privacy navigation
GlassRoute
A privacy-aware iOS route planner comparing lawful driving routes by time and exposure to known fixed ALPR infrastructure—with uncertainty made explicit.
Get GlassRoute
Channel
iOS · in development
Status
No public build yet.
What it is for
Models privacy as a route property you can inspect and compare, with the gaps in coverage data marked as gaps.
Connected systems
Shares FernWX's concern with place, evidence, and explicit uncertainty.
Manual / orientation
How to read this place.
Slicewrite is not a corporate brochure. It is a public map of systems: what each one is, which problem it contains, where it belongs, and how it relates to the rest.
System atlas
Select a system to see its purpose, interface, release state, relationships, and how to install it.
Explain
Distribution
Release channels belong to individual systems. Downloads should identify platform, version, provenance, and support status.
Obtain
Support
Support begins with the system's evidence: documentation, known constraints, source, and a precise way to report a problem.
Maintain
Studio practice
Local-first operation, inspectable changes, explicit uncertainty, and software shaped by real use run through every system.
Principles
Distribution / release channels
Obtain a system.
Each system carries its own release channel. Open a system in the atlas for its build, checksum, and install path.
Native applications
Signed macOS and iOS builds, versioned per system with release notes and platform requirements.
Artifacts
Command-line tools
Pinned installers and replaceable runtimes for systems such as ProxyPilot and RepoGPS.
Install
Web systems
Live interfaces for FernWX, Slicebench, and this site.
Launch
Open corpus
Courses, protocols, and governance material published through Agent Campus.
Read
Support / system care
Keep it working.
Support should preserve context. Start from the affected system, its version, and the evidence you can observe; that routes the report to the right place.
Documentation
Operating guides, boundaries, and known limitations belong beside each system.
Read first
Release state
Confirm the installed version and channel before treating local, release, and production evidence as interchangeable.
Identify
Problem report
Name the system, expected behavior, observed behavior, and the smallest reproducible sequence.
Describe
Source and provenance
Where source is public, the system page will connect the release artifact to its repository and history.