Files
freno-dev/marketing/positioning.md
Paperclip Agent c1c498e37f site: remove the unproven remote claim from the Nook landing page
FRE-323. The one-click remote install is app-UI-only and needs hand-edited ~/.ssh/config plus a one-time ssh-copy-id (FRE-320); FRE-315 and FRE-322 hold the claim unverified and demo-gated.

- drop the Remote tile and its mock from the feature collage
- drop the "Any SSH box, one click away" breakdown, its demo and bullets
- drop "Works across every hooked agent, local or remote"
- drop the "One-click SSH setup" chip
- move the copy to marketing/drafts/remote-ssh/ and mark remote held in marketing/positioning.md

No replacement claim was added. Deploy waits on a push credential for the GitHub repo Vercel builds.
2026-10-29 05:55:26 +00:00

4.9 KiB
Raw Blame History

The Nook — Positioning (source of truth)

Every drafted asset draws its voice, claims, and constraints from this file. If an artifact invents its own framing, fix the artifact or fix this file — never both silently diverging.

Primary source: ~/Code/the-nook/docs/marketing-strategy.md.

The sentence

Your Mac and your agents, under control. The Nook puts your whole coding-agent fleet in the notch — thirteen agents — so you see what is running, unblock it in one tap, and keep the machine from overheating while it works.

The wedge

The thing to say over and over, in every channel, in slightly different words:

An agent blocked on a permission prompt is the most expensive kind of idle. You pay for the model, you pay for the wait, and you get neither.

It is acute, quantifiable, and true — and it is the demo: a card appears, you tap Allow, work resumes. Ten seconds, no explanation needed.

The bundling reframe

Three audiences (agent herders, hardware tinkerers, glanceable-widget users) in one $10 app reads like a grab bag. Reframe as consolidation, which is the honest story:

One $10 app instead of a notch toy, a fan utility, a battery limiter, a menu-bar stats strip, and a notification hack. Same one-time purchase, no subscription.

Price rises to $15 at 1.0 — dated and honest, not a permanent beta.

Hard rules

1. Category nouns, never product nouns

freno-dev/AGENTS.md forbids naming any competitor in user-facing copy — landing pages, marketing copy, comparison tables, meta descriptions, emails, FAQs, all of it.

  • Use category nouns: "notch app", "menu-bar monitor", "fan control utility", "battery charge limiter", "agent notification hack". These carry the same search intent and are fully compliant.
  • Compare against the status quo, not a competitor: "vs. a terminal bell you don't hear", "vs. four utilities in your menu bar", "vs. finding out an hour later."
  • The rule does not reach App Store–external review replies, direct email, and community replies written by a human, where quoting what a user said about another tool is normal conversation.

2. A claim requires a test to exist

Copy that says "13 agents" or "no data leaves the device" must have a test backing it. If a claim cannot be pointed at code or a test, it does not go in copy.

3. Honest privacy scoping

Telemetry and the trial email do leave the device. The defensible claim is:

No prompt or code content leaves the device.

Never "no data leaves the device".

4. Sell what works today

Phone approvals are deferred until a shipped iOS app exists — no "(coming soon)" parentheticals. The launch story is the approval card: an agent blocked on a permission prompt, unblocked from the Mac's notch, and work resumes.

Remote SSH is held, not approved. The one-click install has not shipped and has not been recorded (FRE-320, FRE-205), and the current path needs hand-edited ~/.ssh/config and a one-time ssh-copy-id (FRE-320). Its copy is parked in marketing/drafts/remote-ssh/ until the CTO verifies the shipping flow and a demo exists.

5. Humans hold every account

No agent authenticates, posts, upvotes, or DMs. No sock puppets, no self-mention without disclosure. approved/ is the only thing a human ever publishes from — nothing posts itself.

Approved claims (each backed by code)

Claim Backing
Thirteen hooked agents, one glance AgentSpec.all — claude, codex, opencode, pi, omp, muse, hermes, openclaw, zai, gemini, cline, qwen, deepseek
Permission gate answered from a card awaitPolicyTable + bridge directive path (hook/normalize.go, serialize.go)
Fan / thermal / charge control helper/ (privileged helper, SMC, no kext)
One-time purchase, no subscription $10 → $15 at 1.0; Stripe checkout
macOS 14+ 27 source files use the @Observable framework
No prompt or code content leaves the device envelope carries session/event/terminal metadata only (see docs/agent-interface.md)

Held claims (not publishable)

Claim Why it is held What has to be true first
Remote agents over SSH, one click to install The one-click path is app-UI-only and needs hand-edited ~/.ssh/config plus a one-time ssh-copy-id; no demo exists (FRE-320). FRE-315 and FRE-322 hold it unverified and demo-gated. FRE-320/FRE-205 ship a genuinely one-click install, the CTO verifies it, and a recording shows a remote agent joining the island. Copy parked in marketing/drafts/remote-ssh/.

Voice

  • Short, concrete, no hype adjectives. Numbers over adjectives ("thirteen agents", "one tap", "$10 once").
  • The notch/island is the product's home; agents are the product's point.
  • Never apologize for being a utility. The utility is the point.
  • Banned phrasings: competitor names (see rule 1), "AI-powered", "revolutionary", "game-changer", "seamlessly". Unverifiable superlatives generally.