HabitForge revival — the branded front-end play

Decision (2026-08-05): revive HabitForge as a branded front-end over HiveJournal's shared backend, SEO-led. Not a separate product/codebase — the Lodestone pattern (one engine, category-owning skin). Owner directed both calls explicitly.

Why now / the asset

The founder created the original HabitForge (250k+ users, category pioneer). Knockoffs took the .com and built thin streak-counters; "no one has done it right." The .com is for sale but overpriced. We hold habitforge.ai. You don't have to buy back the .com — you out-authority it: original-creator E-E-A-T is the one signal a clone can't fake, and .ai is no handicap for an AI-native tool.

Why it's not a distraction from hivejournal.com: HiveJournal is a generalist brand ("tools for writing, listening, and the spaces between") and will never rank for "habit tracker." That high-intent category sits unclaimed. A focused habitforge.ai captures a search space the generalist brand structurally can't — category capture, not cannibalization (cross-link, don't compete).

Resolving the doc contradiction

Two prior bets on the same heritage existed:

• variant-c / docs/archive/habitforge/ → revive HabitForge (habitforge.ai)
• HABITFORGE_PAGE_REACTIVATION.md → redirect the old habitforge.com Facebook audience (~2.7k, 2009–2015) toward Odessa

This plan supersedes the Odessa-redirect as the primary use of the heritage. The FB audience + origin story become fuel for the revival, not a redirect to a different brand. (An Odessa cross-sell can live inside HabitForge later — habit→story bridge — but the front door is HabitForge.)

Positioning: the honest habit tool, done right by the one who invented it

The clones are streak counters. Ours is the whole loop — including the honest half none of them have: it tells you when not to, in your own voice. That's the wedge, and the engagement-farming clones can't copy it without dismantling their business model.

• No dark patterns. No streak-as-guilt, no dopamine-slot-machine, no manipulation. Treats you like an adult. (Guardrail: this must be true — audit our own streak mechanics for guilt/manipulation before we claim it.)
• AI-native (the .ai earns itself): context nudges on glasses, your own cloned voice, Play It Forward consequence-forecasting — things no habit tracker has.
• Real behavioral science + normative data (citizen-science layer), not vibes.

What combines (all already live — compose, don't rebuild)

Already built brand shell: the /variant-c (/landing/c) "the forge is lit again" landing (defaults to habitforge.ai), the docs/archive/habitforge/ kit, and live heritage copy on / and /landing ("From the creator of HabitForge, trusted by 250,000+").

SEO strategy (the lead)

Mirror the proven journaling-compare cluster (lib/journaling-compare.ts + honesty-first comparison pages). The plan:

1. Cornerstone — the origin story. "I built HabitForge in 2009. It hit 250k users. I watched it get cloned badly. Here's the real one, rebuilt." The unique, un-fakeable authority asset and a link magnet (founder-origin posts get picked up). Only the founder can write this; it anchors the whole cluster.
2. Comparison cluster (honesty-first) — lib/habitforge-compare.ts + /compare/... pages: HabitForge vs Habitica, vs Streaks, vs [the knockoffs by name], vs the "Atomic Habits" app crowd. Honest about where each wins; converts the exact "which habit app" query where the clones currently rank.
3. Category cluster — "how to build a habit that actually sticks," "why streak apps make you quit," "the anti-habit-tracker," "habit stacking that works" — the informational queries that feed the funnel.
4. E-E-A-T signals everywhere — original-creator byline, 250k heritage (defensible number only), real product depth linked from every page.
5. Technical SEO — every new public page gets a scoped openGraph + twitter block (Next won't derive them; site-wide fallback otherwise — see CLAUDE.md), structured data naming the app HabitForge, and internal links into the HJ dashboard habit surfaces.
6. The AI-native wedge as content hooks — glasses nudge, own-voice, forecasting are what the .ai stories hang on.

The north star: one unified habit system

The eventual target is a single, coherent "your habit system" cockpit — the ~12 scattered features (streaks, Downstream, Play It Forward, Levers, routines, Mantras, accountability) experienced as one product, not a menu. That's the destination HabitForge is being built toward. SEO leads because authority + traffic have to exist before the unified product has anyone to serve — but every SEO decision should point at that destination (the comparison/category pages describe the whole loop, not one feature, so they pre-sell the unified thing).

Build sequence (SEO on-ramp → unified destination)

1. Retarget the landing — DONE (2026-08-05): /variant-c now leads with the whole-loop positioning (hero + a "Not a streak counter. The whole loop." features section showing the real differentiators — own-voice nudges, glasses context nudges, Play It Forward, intervention ROI, honest accountability), the origin story was already there, and the canonical/OG point at habitforge.ai (host-serving slice). Also fixed honesty bugs on the old landing (it claimed native iOS/Android apps that don't exist yet → "native mobile in progress"; dropped the "21 days to form a habit" myth). (The primary SEO surface; everything links to it.)
2. Origin-story cornerstone page.
3. Comparison cluster (lib/habitforge-compare.ts + pages).
4. Category content cluster — STARTED (2026-08-05): three science-grounded guides as content/blog/*.md (the 21-day-myth flagship, "how to build a habit that sticks" pillar, "why you keep quitting"), honest citations (Maltz/Lally, Duhigg, Gollwitzer, Fogg, Clear), each linking to the product + compare cluster; cross-linked from the /compare/habitforge hub. More queries to cover over time (habit stacking, breaking a bad habit, keystone habits).
5. The unified /dashboard/habits cockpit (the destination): composes the existing surfaces (streaks + Downstream + Play It Forward + Levers + routines + Mantras) into one "your habit system" view. Ships in stages — first as a composed dashboard that links the surfaces, evolving toward a genuinely single experience. No new engines; the work is integration + coherence, not more features. This is the target the earlier steps fund.

Open questions (decide before slice 1 ships)

• Domain serving — RESOLVED (2026-08-05). habitforge.ai serves via host-based routing on the same Next app: middleware.ts rewrites habitforge.ai/ → the HabitForge landing (200 at its own URL, NOT a 301 to hivejournal.com), and the landing's canonical is pinned to https://habitforge.ai/. The owner will buy back habitforge.com later; until then habitforge.ai is the home. Remaining is a console step (add the domain in Vercel + DNS) — see docs/setup-guides/HABITFORGE_AI_DOMAIN.md. Deferred (non-blocking): whether to re-canonical the /compare/habitforge SEO pages from hivejournal.com to habitforge.ai once the domain is live.
• Auth/account: shared HJ account (one login, two front doors) — confirm the signup flow from habitforge.ai lands in the same account system.
• Honesty audit: verify our own streak mechanics carry no guilt/manipulation before we claim "no dark patterns."
• Heritage numbers: confirm "250k+ users / since 2009" are defensible before headlining them (they're already in prod copy, so presumably yes).

Guardrails

• Category capture, not cannibalization — cross-link hivejournal.com, never compete with it.
• The "honest / no dark patterns" claim must be true of our own mechanics.
• Heritage claims accurate and defensible.
• Compose existing features; add no new habit engines in the SEO phase.