One shared foundation

Tools that fit the business.

Install service plugins, then make every screen feel like it belongs. The platform stays familiar while each workspace has its own voice.

01 / Foundation

Shared contract1

Semantic theme for every plugin

Example plugins2

Booking and work orders

Reference systems4

Translated into the same roles

Business workspace

See the system at work

ThemePaletteEdit theme

Northside Studio

Good morning, Alex.

Your services and operations are in one place.

NS

Reusable services

Plugin catalogue

Each plugin follows the same manifest, theme roles and component vocabulary.

02 / Plugins

Common boundary

One shell, many services.

Domain logic lives in the plugin module. Navigation, theme, shared controls and future billing stay in the platform.

Business identity

Theme studio

Choose layout and type separately from color. Adjust the palette and preview every installed plugin with the same semantic roles.

03 / Theme

01 / Starting pointTheme · type and shapePalette · colors and mode

Mix either axis. The platform shell keeps its own identity.

02 / Palette

Primary action

Accent

Canvas

Density

03 / Alignment job

Prepare a structured proposal from a reference. This local example shows the job output and validation boundary.

Target reference

Northside Studio

Services, in order.

All installed modules use this theme.

NS

Human reviewed changes

Agent jobs

A future agent will propose changes against the same theme and plugin contracts.

04 / Jobs

Input

A bounded request

Current revision, target reference, allowed keys, screenshots, installed views, budget and acceptance criteria.

Output

A reviewable patch

Structured theme values, rationale, affected views, contrast report and before/after previews.

Publish

Owner approval

Validation and visual review happen before the active business theme revision changes.

Open theme studio