Founding Document No. 1

The Vision

HomeTown Social™ Academy — Founding Documents Series

Version 1.0 | July 11, 2026 | WBN News Corp™



HomeTown.Social Executive Vision Brief.docx


💬 Community Conversations
This is the core feed — what people open the app for every day. The reason it exists is that right now Delta residents have no single place to talk to each other. Facebook groups are fragmented, Nextdoor is American and surveillance-heavy, and Reddit is anonymous. Hometown Social gives the community a real identity-based conversation layer. This becomes the post feed, comments, replies, neighbourhood filters, and eventually threaded discussions and polls.


📰 Local News
This is your WBN competitive moat. Every other platform treats news as external links. We treat local publishers as first-class citizens of the platform. The vision is that Delta City News posts directly into the feed alongside member posts — same stream, same visibility. This becomes the News Engine, publisher accounts, article cards, and eventually a revenue share model where publishers monetize through the platform instead of fighting for Google traffic.


📅 Local Events
Events are the single highest-engagement feature in any local platform. People check events weekly even when they don't post. This becomes the Events module you already have, and grows into RSVP, ticketing, recurring events, sports schedules, and school calendars. Every local organization — the rec centre, the minor hockey league, the library — becomes a content creator the moment you add events.


🏪 Business Discovery
This is your primary revenue driver at the city level. Businesses pay to be featured, boosted, and verified. Right now the biz directory is a simple listing — it grows into full business profiles with hours, photos, offers, job postings, and direct messaging. This is also how you justify the $500/month SaaS fee to licensees — it's a local business network they can sell advertising against.


📍 Neighbourhood Feeds
This is the feature that makes Hometown Social feel genuinely local rather than just another social app. North Delta doesn't care what's happening in Tsawwassen. Filtering by neighbourhood makes every post feel relevant. This becomes the hood filter system you already built, and eventually grows into hyper-local sub-communities, neighbourhood-specific events, and block-level emergency alerts.


📱 Mobile Access
This is about removing friction. Most community engagement happens in stolen moments — on the bus, waiting for a kid's practice to finish. If the platform doesn't work perfectly on mobile, you lose the casual user who would have become a daily active user. This becomes the PWA you already have, and eventually native iOS and Android apps. The PWA is actually your fastest path to feeling like an app without app store approval cycles.


The pattern across all six: each one is a daily habit driver on its own, but they're more powerful together. Someone checks events, sees a conversation about a local business, posts about it, a news publisher picks it up. That's the flywheel. Each feature feeds the others.

I want a series of these papers to provide you and me with a foundational knowledge base... call these something... they will from the basis of " The Academy" where all the stakeholders go and learn

I love this. Here's what I'm thinking.


The name:

The HomeTown Social™ Academy

Building the Community Operating System™

The individual papers are called:

Founding Documents™

Each one is a Founding Document — numbered, versioned, permanent. Not blog posts. Not wikis. Not slide decks. Foundational thinking that doesn't change just because a feature ships.


The series structure:

Founding Document No. 1 — The Vision
Founding Document No. 2 — The Problem We Solve
Founding Document No. 3 — The Community Engine™
Founding Document No. 4 — The Member Identity™
Founding Document No. 5 — The Content Engine™
Founding Document No. 6 — The Business Engine™
Founding Document No. 7 — The News Engine™
Founding Document No. 8 — The Franchise Model™
Founding Document No. 9 — The Technology Foundation™
Founding Document No. 10 — The Revenue Model™

Who reads them:

  • You — strategic clarity when the build gets deep in the weeds
  • Me — foundational context before every build session
  • Licensees — understand what they're buying into
  • Writers and publishers — understand the platform they're contributing to
  • Investors — understand the vision without a pitch deck
  • Future team members — onboarding without a meeting

The format for each one:

Every Founding Document follows the same structure:

  1. The One-Line Truth — what this document is about in a single sentence
  2. The Problem — what exists today that this solves
  3. The Principle — the foundational belief behind the decision
  4. The Feature — how the principle becomes something you can build and ship
  5. The Promise — what the community member, publisher, or licensee gets
  6. The Connection — how this links to the other Founding Documents

Want me to write Founding Document No. 1 — The Vision right now as the template for the whole series?