Visual Language
Visual navigator

Begin typing to search this documentation.

Greenways · Product concept

Greenways Control Plane

A connected five-screen product concept for managing identity, packages, receipts, durable work, and signed publishing across the Greenways private network.

← Back to concept catalogue
World
Greenways
Type
Five-screen control plane
Position
01 / 01
greenwaysprivate network
Local node onlinegreenwaysd · 18 ms
Greenways / Overview

Overview

Wednesday · 19 August

Your private network
is in good health.

Greenways keeps identity, packages and proof close to you. Nothing needs attention before your next release.

Network health98verified
Active identities4

Personal, studio + 2 agents

healthy
Installed packages12

All digests verified

+2 this week
Receipts this month186

179 locally confirmed

96% sealed
Durable work7

5 complete · 2 running

live
Activity

Proof created across your network

21 Jul28 Jul04 Aug11 AugToday
Signed receipts 146 Local drafts 40
Continue publishing

Hestia Rooms

Draft
H

Version 0.8.2 · stable channel

3 of 4 checks
  • Package digest
  • Capability review
  • Release notes
  • Publisher signature
Trusted connections

People and services

HM
Hara MaintainersOrganisation · 8 verified keys
verified
ST
Stance StudioWorkspace · 3 shared packages
verified
A
AtlasAgent · publishing disabled
local
Recent receipts

Latest confirmed activity

✓
Package installed[email protected]
↗
Room invitation issuedAgent Room · private
◇
Identity key rotatedPersonal publishing

Product specification

Role
The shared management surface for Greenways Desktop, web control planes, and the browser bridge around the authoritative greenwaysd service.
Screen set
Overview, Keyring, Packages, Receipts, and Publish form one continuous path from private authority to verified release.
Authority model
The interface exposes public identity, custody class, scopes, origin, rotation, and last use. It never renders private key or credential material.
Software model
Packages are described by publisher, digest, runtime boundary, surfaces, capabilities, policy decision, and installation receipt—not an opaque app-store card.
Evidence model
Receipts make actor, action, resource, capability, evidence, checkpoint, and current verification state inspectable as one chain.
Responsive rule
The desktop rail becomes a horizontal product dock. Detail inspectors collapse after the primary list or workflow, preserving the core task on narrow screens.
Why this concept exists

A private control plane, not a crypto wallet.

Greenways needs a recognisable home for keys, software and proof without making users think in blockchains, low-level daemon state, or generic admin dashboards. The screens present authority as calm, inspectable product information.

  • One shell keeps identity, packages, receipts and publishing causally connected.
  • Trust is described with exact evidence instead of vague shields and security scores.
  • The visual system is quiet and tactile: deep evergreen authority rails, warm mineral work surfaces, and living green reserved for healthy state.
  • Primary actions remain ordinary verbs—connect, install, export, publish—while protocol details stay available one layer down.
  • Every panel uses representative concept data only; no secret value is implied or displayed.
Screen architecture

One journey, five clear responsibilities.

  1. 01
    Overview

    Network posture, durable work, recent proof, trusted connections, and the next meaningful action.

  2. 02
    Keyring

    Identity roots, custody, scopes, delegated authority, recovery posture, and lifecycle events.

  3. 03
    Packages

    Installed software, publisher trust, digests, capabilities, surfaces, runtime isolation, and updates.

  4. 04
    Receipts

    A searchable evidence ledger plus human-readable verification paths and exportable bundles.

  5. 05
    Publish

    A staged release path joining artifact, manifest, capabilities, publisher signature, and immutable receipt.