06-reference

squarely current state review

Fri Apr 24 2026 20:00:00 GMT-0400 (Eastern Daylight Time) ·reference ·source: internal-review ·by Ray ·⚠ medium
squarelycurrent-state-reviewtrademarkamazon-aplusios-appbrand-coherence

Squarely current-state review (4 surfaces)

Why this is in the vault

Baseline state-of-the-bet snapshot for Squarely commissioned the night Sanity Check v9 shipped, as the founder pivots next major work from SC to Squarely. Captures the exact 4-surface drift (web stuck on Book 1, 2023-stale; iOS app pre-launch with YOUR_APP_ID placeholder; 3 Amazon books with empty A+ Content skeletons; no trademark filed) so the post-pivot rebuild can be measured against a real “before” line. Filed in 06-reference/ because it informs RDCO design-system, MAC/positioning, and brand-architecture work — not just Squarely tactics. Cross-filed against the Squarely project hub.

Mapping against Ray Data Co

Strong — directly load-bearing for the next 30-60 days of execution.

  1. Squarely is a live test of the RDCO design-system inheritance pattern. RDCO has the umbrella system (~/.claude/skills/ray-data-co-design/) plus per-bet sub-systems (sanity-check-design just shipped v9; squarely-design does not yet exist). The 4-surface coherence score of 3/10 here is the RDCO-design-system-inheritance test case: do we extend the umbrella into a ~/.claude/skills/squarely-design/ brand-spec, or honor the iOS wood/glass aesthetic and treat Squarely as its own sovereign system? Recommendation in the doc (latter) is the founder’s call but the question is generalizable to every future RDCO sub-bet.

  2. Trademark-first sequencing maps to MAC’s “verify the gating prerequisite before everything downstream” pattern. USPTO TEAS Plus filing (~$250) is the gate that unlocks Brand Registry → A+ Content → defensible brand surface. Same shape as the MAC framework’s insistence that the verification layer goes in before the model — skip it and every downstream investment is operating without the protective layer underneath.

  3. The web/iOS author-identity split (John H. Wilson on books + web vs. Ben Wilson on iOS) is the canonical “RDCO bet without a stated narrative” failure mode. Same anti-pattern Sanity Check fixed in v9 (founder’s voice + named operator). Squarely needs a customer-facing answer for “is this John’s puzzle book brand or Ben’s puzzle product company or both?” before the next surface ships. Generalizes: every RDCO sub-bet needs its operator-author story explicit before launch.

  4. Domain mismatch (squarelypuzzle.com vs. squarelypuzzles.com) is a Teton-class operational drift. Single-character difference between the live web domain and the iOS app’s hardcoded URL is the kind of silent failure that compounds the moment users start moving between surfaces — fix before App Store launch or the entire web→iOS funnel breaks day one.

  5. A+ Content patterns (how-it-works module, series comparison chart, brand-story header) are reusable for any RDCO product that ships through Amazon or Stripe-storefront-style surfaces. File the 3 patterns as Squarely-specific now; lift to the RDCO design library when MAC Pack or Data Dots reach commerce surfaces.

Surface 1: squarelypuzzle.com

Single-page Cloudflare-hosted marketing site. Source repo NOT on this machine — likely separate private GitHub OR a no-code tool (Webflow/Framer). Framework unidentifiable from DOM (renders client-side, suggests SPA or no-code build).

Content is entirely Book 1 (“Squarely Up To You” by John H. Wilson, 2023). Books 2 and 3 are invisible. No App Store placeholder, no iOS game mention, no multi-book comparison. Footer copyright ”© 2023 John H. Wilson” — not updated since launch. Author byline is John H. Wilson (the founder’s father) — Ben Wilson nowhere on the web surface.

CTAs: “Get sample puzzles / Buy book” → single Amazon affiliate link. Email capture for 10-puzzle PDF giveaway.

No ~/.claude/skills/squarely-design/ brand-spec exists. Squarely has no formalized design system at all.

Surface 2: Squarely iOS app

Codebase: /Users/ray/Projects/squarely-ios. SwiftUI, iOS 17+, Firebase-backed. GitHub: bwilson668/squarely-ios.

NOT yet on App Store. About view has hardcoded YOUR_APP_ID placeholder + stub itms-apps:// URL. Internal website URL hardcoded as squarelypuzzles.com (with s) — domain mismatch with actual squarelypuzzle.com (no s).

Implemented: Play, Daily Puzzle, Stats, Options, Help, About screens. Analytics + Daily Puzzle live. Stubs: GameCenter, Challenge Friend, IAP (remove-ads), Ads. Freemium model planned.

Brand palette (iOS): warm earthy browns + warm creams (wooden frame metaphor) + 9-tile colorful glass gradient palette (one hue per number). Distinctive and internally consistent.

Surface 3: 3 Amazon product pages

#ASINTitleAuthorDateReviewsA+ Content
1B0CD91ZLCYSquarely Up To You (Squarely Puzzles)John H. WilsonJul 20235.0★ × 13Skeleton present, 0 modules populated
2B0DJ5SZRYNSquarely Up To You: Volume 2John H. WilsonSep 20244.0★ × 1Skeleton present, 0 modules
3B0FYNPYM1ZSquarely Up To You: Volume 3John H. WilsonOct 20255.0★ × 2Skeleton present, 0 modules

All three: $10.95 paperback, near-identical boilerplate descriptions (“new logic puzzle, 5×5 grid, two rules”, 100 puzzles, hints, full solutions). No bundling, no Kindle edition surfaced. Series-link “Part of: Squarely Puzzles (3 books)” auto-generated by Amazon. Volume 2 has only 1 review — extremely thin social proof.

The #aplusBrandStory_feature_div skeleton being present on all three suggests partial Brand Registry enrollment via KDP (KDP authors sometimes get Brand Registry without a trademark). But zero modules populated means the unlock has not been used.

Surface 4: A+ Content + Brand Registry + Trademark

Trademark status (USPTO search verified): NO trademark filed for “Squarely,” “Squarely Puzzles,” or “Squarely Up To You” as a puzzle brand. USPTO returns 2 unrelated marks (SQUARELY STYLISH for glassware—DEAD; SQUARELY NATURAL for pet food—LIVE but different owner).

This is the gating prerequisite for full Brand Registry → full A+ Content access. USPTO TEAS Plus filing: ~$250/class, 8-12 months to register. Brand Registry eligibility CAN sometimes start with a pending application serial number.

A+ Content patterns worth borrowing from top-selling puzzle books:

  1. “How it works” 3-step module — image+text combo: blank grid → partial solve → completed grid. Demystifies novel puzzle types. High-conversion for first-time buyers.
  2. Series comparison chart — “Which book is right for you?” table comparing the 3 volumes on difficulty, puzzle count, ideal-for. Surfaces all 3 SKUs on each page; converts unsure browsers.
  3. Brand story header with author photo + origin story — “invented by a mathematician father” hook is a strong differentiator vs generic puzzle books. Personality-driven brand stories outperform “we make great puzzles” copy.

Cross-surface coherence score: 3/10

3 biggest drift points

  1. Visual identity is not a shared system. iOS = warm wood + colorful glass tiles. Web = dark editorial. Neither references the other. No brand-spec, no shared color tokens, no shared typography.

  2. Author identity split. Web + Amazon = “John H. Wilson” (the dad / puzzle designer). iOS = “Ben Wilson” (designer + developer). No customer-facing story explaining the family-brand relationship. Web doesn’t mention iOS app. iOS app doesn’t mention books by name.

  3. Web is Book-1-only and 2023-stale. A customer arriving from Google search finds a single-book site that’s 2-3 years out of date relative to the actual product portfolio (3 books + upcoming app + maybe web game).

What’s well-positioned

Ranked recommendation

1. Trademark filing FIRST (gating prerequisite)

$250 USPTO TEAS Plus, 1-time action, 8-12mo to register. Unlocks full Brand Registry → A+ Content. Protects brand as iOS app launches. Everything else is downstream.

2. Web landing page rework (half-day edit, not rebuild)

Add Books 2 + 3 with covers + Amazon links. Add App Store coming-soon section (placeholder with email capture). Fix 2023 copyright. Founder needs to locate the source repo (not on this machine — Webflow / Framer / separate private GitHub).

3. Amazon A+ Content (after trademark filing in progress)

Brand Registry skeleton already present. If Seller Central access confirmed, A+ Content can be created even with pending trademark. Three patterns above: how-it-works visual, series comparison chart, author brand story. Revenue lift on existing traffic measurable within 30 days.

4. iOS App Store launch (after web is updated)

Pre-flight blockers: hardcoded YOUR_APP_ID + domain mismatch (squarelypuzzles.com vs squarelypuzzle.com) need fixing. App is functionally complete. Should NOT launch before web is updated — otherwise web → iOS funnel breaks on day one (web wouldn’t link to App Store).

Open questions for founder

  1. Trademark scope: file under puzzle-book class only, or include digital game (iOS app) class too? (Multi-class adds ~$250/class)
  2. Source repo for squarelypuzzle.com: where does it live? Webflow? Framer? Private GitHub? (sub-agent couldn’t find it)
  3. Author identity story: how should the customer understand John (dad/designer) vs Ben (operator/developer)? Family brand framing? Co-author? Studio under both names?
  4. Brand-system inheritance: should Squarely share RDCO v9 design system, OR keep its distinctive iOS wood/glass aesthetic and extend that to web? Recommend the latter — Squarely’s personality is genuinely its own.
  5. Domain canonical: squarelypuzzle.com (web) vs squarelypuzzles.com (iOS hardcoded) — which is canonical? Fix the wrong one.