MAINFRAME/1 · BRAND SYSTEM · RELEASE 26.07

Built like a system.
Visible at 16 pixels.

A calm, operational identity for an always-on machine. This page is the source for marks, tokens, interface patterns, and exports.

PRIMARY MICRO-MARK /
ASSETS ONLINELIGHT + DARKSVG + PNGAPP-READY TOKENS
PREVIEW ENVIRONMENT /Dark mode

01 / IDENTITY

Keep the wordmark.
Make the system complete.

MAINFRAME/1 is the formal mark. The slash-number grammar carries the mainframe lineage and is not a version counter. Use plain “Mainframe” in running copy.

The identity should feel like serious infrastructure, not terminal cosplay. Large surfaces are calm. Operational signals are precise. Cyan appears when the system has something to say.

02 / LOGO FAMILY

One name. Three useful forms.

Use the full mark by default, the company lockup when provenance matters, and the micro-mark only where the wordmark cannot fit.

PRIMARY WORDMARK /
ON LIGHT /
ON DARK /

Product lockup

Use when the relationship to Inflection Systems needs context.

SVG · DARKSVG · LIGHT

03 / MICRO-MARK

The favicon should not be a tiny wordmark.

The previous M-plus-slash mark became visual noise at browser-tab size. The new micro-mark isolates the most ownable part of the identity: /1. It stays legible at 16 pixels and reads naturally inside the future app launcher.

SVG · SYMBOL
TAB VISIBILITY TEST
Mainframe favicon at 16 pixels16 PX
Mainframe favicon at 32 pixels32 PX
Mainframe app icon at 64 pixels64 PX
Mainframe app icon at 128 pixels128 PX

04 / COLOR TOKENS

Calm surfaces.
Precise signals.

The same semantic roles work in marketing and product UI. Status colors communicate state; they are not decoration. Luminous cyan and phosphor belong on dark surfaces. Light surfaces use their deeper, accessible counterparts for text.

Console#0B1220

Primary dark surface

Panel#1E293B

Raised dark surface

Signal Cyan#00D4FF

Signature and action

Phosphor#39FF6E

Healthy state on dark surfaces

Operational Green#087A3E

Healthy-state text on light surfaces

Deep Cyan#007287

Accent text on light surfaces

Operator Amber#FFB000

Attention and waiting

Paper#FFFFFF

Primary light surface

Mist#F1F5F9

Secondary light surface

Ink#111827

Primary light text

05 / TYPOGRAPHY

Operations should feel inevitable.

OUTFIT / 700 / DISPLAY

Mainframe uses Inter for calm, readable product and marketing copy. It is neutral enough to disappear and precise enough for a serious operational surface.

INTER / 400–600 / BODY + UI

JOB inbox-triage · 10:00COMPLETED · 43 ITEMS · 9 DRAFTS

IBM PLEX MONO / 400–500 / SYSTEM FACTS

06 / PRODUCT DIRECTION

A command centre, not a process monitor.

The current product has strong operational depth. The next interface should translate that depth into a calm, self-explanatory system for one operator. It must answer three questions immediately: what is working, what needs me, and what changed.

01

Attention before inventory

Lead with what needs a decision, what is working, and what was delivered. The full inventory remains one step away.

02

Outcomes before telemetry

Show the job and its result before engines, sessions, tokens, process IDs, or raw transcripts.

03

One grammar everywhere

The same hierarchy, status language, spacing, and actions must carry across every product area.

04

Details on demand

Progressive disclosure keeps the default view calm while preserving logs, configuration, and full operational depth.

AREAKEEPIMPROVE
Workforce

Live state and direct access to agents

Group by attention and outcome, not a wall of live terminal cards

Files

Tree and document preview as the shared working memory

Reduce system-folder noise and make recency, search, and ownership clearer

Routines

Every run is logged as a job

Make cadence, next run, last result, and health readable in one scan

Approvals

Nothing external happens silently

Explain impact, destination, changed fields, and exact consequence before approval

Connections

Large pre-built catalog plus custom connections

Separate connected health from discovery, and keep secrets as secondary administration

07 / PRODUCT INTERFACE

One coherent operating surface.

This interactive reference defines the target hierarchy for the app. Use the navigation to inspect each core area, then switch the page theme above to verify the same system in light and dark mode.

IMPLEMENTATION REFERENCE /

Direction, information hierarchy, component behavior, and semantic colors are intentional. Example names and data are illustrative.

MainframeYour private system
System onlineMK

OVERVIEW / LIVE SYSTEM

Good morning.

Everything working, waiting, and recently delivered across your Mainframe.
WORKFORCE4working now
ROUTINES1414 completed today
APPROVALS3need you
FILES8updated in the last hour
LIVE WORK /What is moving now
YOUR MAINFRAME /One system, six operating layers
Online
AGTAgents4 working
RTNRoutines14 today
APPApps3 healthy
CONConnections24 ready
APRApprovals3 waiting
FILFiles8 recent
ACTIVITY / TODAYA system-wide operating log
JOBmorning-briefDelivered
AGTinbox-triage9 drafts → Approvals
APPlead-inboundRunning
FILProduct brief.mdUpdated by Market research
SESSION WORKSPACES /

One session. Any surface. Several at once.

Dock agents beside the current page, then expand the same live sessions into a chrome-less multi-agent workspace.

WORKFORCE /Your agents
4 working1 needs you12 total
Market researchMapping the European property software market
Working
Proposal studioProposal v2 is ready for your approval
Needs you
Inbox operatorMorning triage completed
Delivered
CONTENT FLOOR / 30REM

The page reflows. It is never covered by the dock rail.

WorkingMarket researchCodex · GPT-5.2 Codex
18:22

42 companies mapped. I am validating the strongest entry points.

Comparing 8 category leaders

market-map.pngReady · 1.8 MBMDProduct brief.mdKnowledge / Market research

Images visible to this model

Codex · GPT-5.2 Codex
Needs youProposal studioClaude Code · Claude Sonnet 4
18:25

Proposal v2 is ready. I need your decision on the pricing page.

Waiting for approval

This model cannot see images.

Claude Code · Claude Sonnet 4

08 / PRODUCT PRIMITIVES

State should explain itself.

These primitives use semantic tokens in either theme. Status color reinforces a written label and never carries meaning alone.

AGENT WORKINGCOD

Proposal follow-up

Reviewing meeting context and drafting the next version for approval.

08:42RUNNING
APPROVAL / 04HIGH IMPACT

Send proposal v2?

Draft is ready. Two changes are highlighted for your review.

ROUTINE / HEALTHYDAILY

Inbox triage

NEXT RUN
10:00
LAST RUN
COMPLETED
LOG
JOB-1042

09 / THEME CONTRACT

Light is paper.
Dark is the machine.

The two themes share hierarchy and semantic meaning, but they are not simple inversions. Dark mode is focused and infrastructural. Light mode is warm, quiet, and document-led. Neither uses low contrast accent text for small labels.

DARK / DEFAULTFocused operations
Canvas
#08111D
Panel
#0D1928
Raised
#132238
Text
#F8FBFF
Action
#00D4FF

Use tonal depth and hairlines to structure the interface. Avoid excessive glow, pure black panels, and decorative status color.

LIGHT / DOCUMENTWarm working surface
Canvas
#F3F0E9
Panel
#FCFBF7
Raised
#FFFFFF
Text
#142033
Action
#007B91

Use a warm neutral canvas with crisp white working surfaces. Avoid blue-grey washes that make the product feel administrative.

CyanPrimary action, selection, active work
GreenHealthy, completed, connected
AmberWaiting, attention, consequential review
RedFailure, destructive action, blocked state

10 / DO

Premium calm control room.

  • Use MAINFRAME/1 in display contexts.
  • Use Mainframe in prose and product UI.
  • Keep generous space around the mark.
  • Use monospace for facts, states, IDs, and time.
  • Let cyan carry action and identity.
  • Show outcomes before implementation detail.
  • Make the next useful action obvious.

11 / DO NOT

Never turn it into terminal cosplay.

  • Do not write MAINFRAME1 in customer copy.
  • Do not treat /1 as a release number.
  • Do not fill entire screens with terminal green.
  • Do not use novelty fonts for body copy.
  • Do not invent another standalone icon for launch.
  • Do not make every live session equally prominent.
  • Do not expose technical plumbing as primary navigation.