The basic create + own a page primitive — political-category first, no ecommerce. Anyone can create a page for a party · figure · org; the real owner claims & verifies. Phase 1 = create → follow → post → tag → see-it's-active. Mockup for design sign-off.
One entry tile opens the picker. Political is first & emphasized — the wedge we lead with. Adapted from the b1 wizard's KIND step (giant tappable rows, tap advances, no Next), but the categories are now page TYPES, not Shop/Service/Food. Anyone can create — ownership is sorted later via claim (PP3).
A party page is scoped to a place AND a level. Search the place (reuses the vector location search), then pick the level the page covers — for a party: State / District / Block / Vidhan Sabha (AC) / Lok Sabha (PC) / Village. The identity forms live at the bottom: BJP · Amnour · Vidhan Sabha. This level grid replaces b1's category/service-area steps.
Name & handle are auto-suggested from party + place; logo initials + brand colour pre-filled; short about. "Create page" is the primary — anyone can create. Success keeps the b1 reward beat (the live page IS the prize) and then explains the claim/verify path: community-built now, the official owner can claim & get the verified badge. This reuses the b1 success+proxy idea (create-not-claim, handover) without OTP-product machinery.
The same identity step, but showing the honest edge-states so create never dead-ends. (a) the auto-suggested @bjp.amnour is already taken → we flag it and offer free suggestions (@bjp.amnour.2, @bjp.amnour.bihar); (b) an empty page-name disables the CTA with a quiet hint; (c) the not-the-owner path is made explicit — "you're building this for the community" with the claim handoff stated up front. Adapts b1's handle-check + proxy idea, de-commerced.
As the identity forms, we match it against existing pages. BJP · Amnour · Vidhan Sabha already exists → instead of letting a duplicate be created, we surface the real page and offer two honest exits: Follow it (most people) or Request to manage (if you're the owner, route into the claim flow). This is the single most important anti-duplication guard for a place-graph — one page per party-per-place-per-level.
Header = party logo + brand colour, BJP · Amnour, the Vidhan Sabha level chip, Follow, ⋯, and a claim-state badge (community-built vs ✓ verified). A slim activity strip (followers · posts this week · engagement) so it reads as alive. Tabs are Posts · About ONLY — no products/reviews. Posts feed reuses .tlp; owner gets a Create post affordance. The "page IS the surface" idea from b2, de-commerced.
Three things stacked: (a) a normal composer @-tagging a page — type @BJP and the page autocompletes (handle from PP3); (b) a "Pages here" section on a place page (Amnour) — every page anchored to it; (c) a Pages result group in global search. Tagging + these two surfaces are how a page gets discovered and how its activity flows into the network.
The national-root BJP (Bihar) page rolls up its child pages ranked by engagement — Amnour ↑, Saran rising, etc. — so a party HQ can see which area unit is most active. Shown as the concept, with a subtle PRO lock: the top rows are visible to tease it; the full ranked board is a future paid tier. Phase 1 builds none of this — it just makes the upgrade path legible.
The community editor's view of the page they created. Same surface, owner powers: the page IS the editor — tap a pencil and the line edits in place (name shown mid-edit here), logo + brand-colour swatch, one-line about. The claim/verify status card is front-and-centre: this page is community-built (amber), with the explicit "Claim this page" path for the official party office. Adapts b2's pencils-in-place + owner chip; strips products/services/hours/inbox entirely. No commerce.
Once the owner has claimed & verified, the status card flips green ✓ verified and the full owner controls show. Still one surface, no settings maze (b2 principle): post an update right here, a "Who can post" choice (owner-only vs followers-can-contribute), notifications toggle, and a quiet danger zone — transfer ownership / delete page. The basic insights teaser repeats. Everything commerce in b2 (products, rates, hours, inbox) is stripped.