Skip to content
Hussh
Connect MCP

Apple frame — "What would Apple do?"

Hussh's standing default decision frame. Applied to every product, service, and agent decision — strategy, naming, launch sequencing, marketing, pricing, demos, keynotes, onboarding, category creation.

Concept

TL;DR: "What would Apple do?" is Hussh's standing default decision frame for every product / service / agent decision. Constitutional rule. Paired with the universal design rule: all Hussh deliverables follow Apple Summer 2026 design language — SF Pro, Liquid Glass, Apple color palette, iOS-first layout, Apple HIG spacing. Status as of 2026-05-04: Constitutional. Applied across One, Kai, Nav, iBrokerage, brand, and the wiki reader app itself.

Relations

  • Brand invariants - companion design rule set for Hussh surfaces.
  • One, Kai, Nav, iBrokerage - product pages that apply the frame.
  • Apple platform relationship - operating context for App Intents, iOS-first design, and WWDC-readiness work.
  • Personal Operating Layer - strategic positioning derived from the late-April / early-May 2026 Apple meeting.
  • Apple Frame - Visual Reference - visual reference artifact.
  • Alphabets fund-brand work - institutional wordmark context that reuses the same restraint principle.

What "Apple" means here

Not Apple's literal product roadmap. The frame is a posture with a small number of high-leverage commitments:

  • Restraint over feature breadth. Ship the smallest surface that delivers the Aha Moment. Cut, then cut again.
  • One number on screen. Consumer products earn attention with one legible result, not a dashboard.
  • Voice-first where it works, glanceable where it doesn't. Reading a chat log is a regression.
  • Hardware-software integration mindset — even when the "hardware" is iOS or the user's keyboard. Treat the whole stack as one product.
  • Pricing tells a story. Hussh's signature 69 ending — every consumer-visible number is a brand decision, not a finance decision.
  • Keynotes are the spec. Before shipping, write the keynote line. If the line is dishonest or boring, ship something else.

What "What would Apple do?" rules out

  • ❌ Generic-assistant voice ("As an AI, I think…"). Apple ships products, not models.
  • ❌ Settings panels in place of opinions. If Hussh has to ask the user how Hussh should behave, Hussh hasn't decided yet.
  • ❌ Vendor-co-marketing the model. Models are interchangeable plumbing under BYOA; they are not co-branded.
  • ❌ "AI" as a feature name. Capabilities are described in user terms.

Companion rule - Apple Summer 2026 design language

Universal across every Hussh surface:

  • Typography: SF Pro Display + SF Pro Text. HIG-compliant tracking and leading.
  • Material: Liquid Glass - translucent, blur-backed, light-aware.
  • Spacing: Apple HIG 4pt grid.
  • Color: Apple system palette, light + dark mode.
  • Layout: iOS-first; everything else (web, macOS, watch surfaces later) inherits.

The wiki reader app is itself an instance - see the wiki-as-app architecture page. The operational design tokens live in the reader implementation; public prose should describe the design contract rather than expose repo paths.

Sources