Portable workspace · five interface surfaces
One workspace.
Five manifestations.
Greenways OS V2 is not a miniature window manager. It is one programmable environment of objects, buffers, panes, commands, grants and receipts, expressed at the scale and authority of each host.
The shell changes.
The work does not.
A captured page can begin in the side panel, become a source in a Workroom, open as a Studio buffer on desktop, receive an explicit publishing grant, and appear on the web with the same identity and receipt trace.
Product model
Five primary surfaces.
Fabric
Selected files, identity, devices and storage under the person's control.
- Abstraction
- Tahto semantic roots, identities, revisions and synchronisation over Hara filesystem contracts.
- Execution
- Hara local runtime · Hoplite service boundary
- Boundary
- OS custody, storage providers and explicit device grants
Search
Classify, relate and recontextualise material without rewriting its source.
- Abstraction
- Hestia sources, anchors, evidence and retrieval linked to Tahto roots.
- Execution
- Hara package · Hoplite service boundary · Hodos client projection
- Boundary
- Only user-approved Fabric and provider scopes are searchable
Timeline
Keep chats, decisions, project relationships and meaningful activity together.
- Abstraction
- Hestia archives and evidence with Tahto identity and relationship references.
- Execution
- Hara package · Hoplite service boundary · Hodos client projection
- Boundary
- Selected activity only; no ambient device surveillance
Cowork
Coordinate people and agents around bounded context, authority and outcomes.
- Abstraction
- Tahto authority and project values with Hestia context, evidence and approvals.
- Execution
- Hara package · Hoplite service boundary · Ignatius execution · Hodos client projection
- Boundary
- Scoped files, context packs, capabilities and human checkpoints
Spaces
Turn selected private work into reviewed public releases.
- Abstraction
- Tahto release roots and provenance with Hestia source evidence and Platform delivery.
- Execution
- Hara package · Hoplite serving · Ignatius release execution · Hodos client projection
- Boundary
- An immutable release is public; the source Fabric remains private
Install state 00 · lifecycle study
Before the workspace fills up.
A new Greenways OS installation contains a small, trustworthy core—not a fictional release, agent team or publishing room. Spaces and Flow arrive as explicit applications that can be reviewed and installed later. This is an empty state shared by the five hosts, not a sixth host surface.
Greenways OS core
Fabric storage · identity · application registry · health · grants and receipts
Applications
Spaces for sources and evidence · Flow for projects and managed work
First run
Start with the core.
A clean beginning
Greenways OS is ready.
Choose where the core keeps its state. Applications, identity and remote providers can wait.
No account, cloud workspace, demo data or provider grant has been created.
Native / browser desktop
An OS without invented work.
Greenways OS
Nothing is open.
Install an application, connect an existing Fabric, or leave the workspace exactly as it is.Application library
Add vocabularies deliberately.
Applications
Spaces
Collect, inspect, relate and promote material without turning candidates into facts.
Flow
Coordinate projects, agents, approvals, handoffs and evidence through explicit authority.
Installing an app requests named capabilities. It does not inherit keys, files or remote access.
Browser side panel
Useful before Spaces exists.
Extension popup
Health and invocation only.
Public web
A doorway, not an automatic tenant.
GREENWAYS ON THE WEB
Bring a place you already control.
Browse public work without signing in, or connect an existing Fabric when you are ready to work. Opening this site does not silently create a hosted workspace.Default-install laws
Empty means empty.
No release, room, project, source, publication or recent item is pre-created.
Spaces and Flow add domain vocabulary through an explicit install and capability review.
No identity, key, provider, agent or grant is implied by opening a host surface.
The populated atlas remains useful as a mature-workspace specimen, not the default product promise.
Populated reference atlas
Every surface, at its proper scale.
A portable core,
not a browser-shaped kernel.
Tahto and Hestia build the feature abstractions with Hara. Hoplite and Ignatius are the execution environments in which those features run; Hodos materialises approved client packages. Presentation shells adapt to the host, and privileged effects cross a named provider boundary with a receipt.