Greenways visual language · executable atlas
One visual language.
Every surface in its proper form.
The catalogue is a place to experience the system, not a directory wrapped around it. Foundations, components and product laboratories share one vocabulary while each specimen keeps the scale, density and rhythm its host requires.
- Current applications
- Spaces · Flow
- Atlas entries
- 33 full-scale routes
- Contract
- Neutral structure · peacock signal
The specimen leads.
The catalogue recedes.
Route ownership, maturity and issue references remain available in the atlas index and folio. They no longer compete with the interface being studied. Each page opens as a composition first and documentation second.
Current application plane
Two applications.
One Fabric beneath them.
Spaces and Flow share identity, references and handoff laws. They do not collapse into the same dashboard, and the system layer does not present itself as another application.
Complete route family
Browse by visual layer,
not by file tree.
Every chapter has its own density and purpose. The same neutral grammar holds the family together; route status stays legible without becoming the dominant design motif.
foundations
Foundations
Protected identity, semantic tokens, material, typography, geometry, motion, accessibility, and responsive rules.library
Library
Reusable components and workflow-state studies, separated from application-owned behaviour.applications
Applications
Product-specific laboratories built on the shared package without becoming package exports.- 03.01Current Greenways suiteThe current Spaces and Flow shell across native desktop, browser workspace, bounded companion, CLI, and exact cross-application handoffs.In progress
- 03.02ForemanThe application at the fore: projects, buildouts, sessions, approvals, handoffs, execution, and activity.In progress
- 03.03Greenways FabricThe personal operating environment that keeps storage, identity, agents, and applications connected under the person’s control.In progress
1 related surfaces
- 03.04Greenways OS interface atlasHistorical host-surface studies retained as exploration, not the current Spaces and Flow product architecture.Exploration
- 03.05Earlier Greenways product screensThe superseded product taxonomy retained for historical review and migration evidence.Exploration
8 related surfaces
TodayExploration · Historical explorationWorkroomsExploration · Historical explorationStudioExploration · Historical explorationCampaignsExploration · Historical explorationPackagesExploration · Historical explorationKeyringExploration · Historical explorationReceiptsExploration · Historical explorationControl plane studyExploration · Historical exploration
Composition laws
Elegance comes from hierarchy,
not decoration.
One compact global bar
Navigation stays available, but route taxonomy moves into the atlas index instead of occupying every viewport.
Numbered editorial chapters
Large transitions establish pace and meaning before dense tables, editors or operational surfaces begin.
Full-scale product compositions
Desktop, browser, compact and public surfaces preserve their own proportions rather than inheriting a documentation card grid.
Continue through the system