Screens are composed, not rebuilt.
All capabilities · In build
Interfaces are the part of a system people judge and the part most likely to be rebuilt from scratch every few years. Unifyhub treats an interface as composed rather than authored: a screen is an arrangement of shared parts, described in a form the system can read, and rendered by a runtime nobody has to fork.
view · workshop-overview
- shellworkspace
- sectionschedule
- sectiontask-list
- primitiveaction
A screen written down
Tue 18Repair session
Thu 20Tool maintenance
02Prepare the space
Add a sessionprimitive · action
The tiers
Primitives
The smallest shared vocabulary of an interface: fields, actions, items, headings, panels, layout, theme. They carry the visual and behavioral rules once, so consistency is inherited rather than remembered.
Sections
Self-contained working areas with real behavior: tables, calendars, charts, forms, boards, timelines, maps, conversations, graphs. A section owns a job, not a page, which is what lets the same one appear in many products without being reinvented.
Views
A composed screen: which sections appear, what they are bound to, what they may do, and how they talk to each other. Views are declared as documents rather than written as code, so a screen can be inspected, versioned, diffed, and generated.
Shells
The frame around the work: navigation, identity state, permissions, notifications, command surfaces, workspace context. The shell is where the environment feels like one place even though it is many services.
Applications
A product surface assembled from the tiers above plus its own facts, copy, policy, and routes. An application declares what it is; the runtime supplies how it runs.
One event bus
Everything a screen does travels as a typed event on one dispatch runtime: a person clicking, a delegated agent acting, a service pushing an update, a keyboard shortcut, a voice command. Modules register the effects they can perform, and the bus records who asked for what.
This is why a delegated action and a human action can be held to the same standard. They arrive the same way, carry the same provenance, and pass the same checks.
What this buys a community
Consistency without central control
Independent teams build in the same vocabulary, so their work composes without a coordinating committee.
Screens as records
Because a view is a document, the interface a community used on a given day can be preserved, reviewed, and reproduced.
Surfaces stay replaceable
A new front end can honor the same declarations and the same event contracts, which is what keeps interface fashion from becoming lock-in.
Accessibility and localization by default
Language, keyboard, screen reader, export, and theme behavior live in the shared tiers, so every screen inherits them instead of each one negotiating them separately.
The boundary
Composition applies to the interface, not to judgment. Layout, wording, and workflow remain product decisions, and a domain that needs an unusual surface for real work builds one. The contract is that the unusual surface still speaks the shared events and still declares itself.