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.
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.
Wordmark
The formal display mark. Use in headers, covers, and titles.
Product lockup
Use when the relationship to Inflection Systems needs context.
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.
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.
#0B1220Primary dark surface
#1E293BRaised dark surface
#00D4FFSignature and action
#39FF6EHealthy state on dark surfaces
#087A3EHealthy-state text on light surfaces
#007287Accent text on light surfaces
#FFB000Attention and waiting
#FFFFFFPrimary light surface
#F1F5F9Secondary light surface
#111827Primary light text
05 / TYPOGRAPHY
Operations should feel inevitable.
Mainframe uses Inter for calm, readable product and marketing copy. It is neutral enough to disappear and precise enough for a serious operational surface.
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.
Attention before inventory
Lead with what needs a decision, what is working, and what was delivered. The full inventory remains one step away.
Outcomes before telemetry
Show the job and its result before engines, sessions, tokens, process IDs, or raw transcripts.
One grammar everywhere
The same hierarchy, status language, spacing, and actions must carry across every product area.
Details on demand
Progressive disclosure keeps the default view calm while preserving logs, configuration, and full operational depth.
Live state and direct access to agents
Group by attention and outcome, not a wall of live terminal cards
Tree and document preview as the shared working memory
Reduce system-folder noise and make recency, search, and ownership clearer
Every run is logged as a job
Make cadence, next run, last result, and health readable in one scan
Nothing external happens silently
Explain impact, destination, changed fields, and exact consequence before approval
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.
Direction, information hierarchy, component behavior, and semantic colors are intentional. Example names and data are illustrative.
OVERVIEW / LIVE SYSTEM
Good morning.
Everything working, waiting, and recently delivered across your Mainframe.WORKFORCE /
Your agents
See what is working, what finished, and what needs you.One agent needs your decisionProposal studio has prepared a draft for review.
Active and recent
FILES /
Working memory
Knowledge / Market research / Product brief.md
PRODUCT / MAINFRAME
A private AI command centre that keeps working.
Mainframe gives one person an always-on place for agents, files, routines, connections, and decisions.
Current priorities
- 01 Make active work visible at a glance.
- 02 Put every external action through Approvals.
- 03 Keep context available to every authorized agent.
ROUTINES /
Work that happens again
Standing instructions run every interval or at specific times.Schedule
See the agent, inputs, output, duration, and full log. If it is not logged, it did not happen.
APPROVALS /
Your decision queue
Understand what will happen before anything leaves the system.Send proposal v2 to Acme Europe?
The agent updated the implementation timeline and commercial terms after your call. This will email two external recipients.
CONNECTIONS /
Your system’s reach
Connect once. Authorized agents can use the same tools and data.3 connections healthyCredentials checked 4 minutes ago
Need something else?Ask Mainframe to build a private connection for any API or MCP.
Reach Mainframe beyond this browser.
The same context, agents, files, and connections are available from every paired channel.
Anthropic · Mainframe AI Credits
Launch an agent with the system and its API documentation. It can build and test the connection, then request credentials securely.
API keys and credentials.
Values are stored by reference and never appear in conversations, API responses, or logs.
Create a routine
Add a connection
Authentication opens in the provider’s secure window. Mainframe never asks for your password.
Add an API key
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.
The page reflows. It is never covered by the dock rail.
Comparing 8 category leaders
Waiting for approval
Preparing the next follow-up batch
42 companies mapped. I am validating the strongest entry points.
Proposal v2 is ready. I need your decision on the pricing page.
18 new leads are scored and grouped by buying signal.
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.
Proposal follow-up
Reviewing meeting context and drafting the next version for approval.
Send proposal v2?
Draft is ready. Two changes are highlighted for your review.
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.
- 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.
- 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.
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.