Database tables and models for Champion Portal foundations.

Email-based signup, verification, login, and password reset.

Social login with Google OAuth.

Profile completion wizard and Champion directory search.

Admin verification tools in Lookup Portal for managing champion BUID linking.

Complete Staging MVP: champion dashboard, directory enhancements, activity tracking.

Champion-to-Champion direct messaging with smart email notifications.

Champions admin dashboard with engagement scoring for staff visibility into Champion activity.

Settings, Help/FAQ, visual refresh, and language audit before beta launch.

Admin-managed news/posts system with dashboard integration and regional targeting.

Staff-managed events system with district targeting and Champion Portal integration.

Database schema, models, and basic UI for emergent communities.

Champion-facing community browsing and enhanced landing pages.

Background detection and creation of emergent communities when 3+ champions share an attribute.

Community images, force creation, membership management, message link previews.

In-app notifications with bell icon, email digests, and user preferences.

Extract quiz/role logic from signup helper into reusable services.

Add Champion Role step to profile wizard with optional quiz.

Allow champions to change role and retake quiz from profile edit.

Update ClcAssignment to link to Community instead of Region.

Enable Lookup Portal admins to assign Champions as Community Leaders.

Granular permission flags for staff access control.

Bell icon with pending action items for staff.

Database structure for boards, posts, and comments.

Browse boards, create posts, and comment.

Emoji reactions and popularity sorting.

Champions can protect themselves from unwanted content.

Community Leader and staff moderation tools.

Global discussion space with auto-join for all verified Champions.

Discussion-specific notifications and email digests.

Staff dashboard for monitoring discussion board activity.

Public preview pages for shareable links and signup conversion.

Final v2 polish for confirmation UX and staff review detail surfaces.

Redesign dashboard with Google News-style content sections.

Review and fix all views for mobile-first compliance.

Apply DESIGN-GUIDELINES.md patterns consistently.

Final polish including image variant sizing.

Polish user experience for different verification states and anonymous visitors.

Almost Alumni and Faculty/Staff can become Champions with appropriate fields and verification workflows.

Save Champions as contacts for quick access and prioritized content.

Suggest similar Champions based on shared attributes.

Champions and events can have photo galleries.

Track and display key activity metrics.

Public Career Center page with resources, quick links, career events, and OCPD section.

PDF download functionality and admin CRUD for career resources.

Career event tagging in admin and career center analytics.

Unified notification preferences in Settings.

Notification triggers for discussion board activity.

Background jobs for digest generation and delivery.

Dedicated templates for time-sensitive notifications.

join_communities wizard step with community suggestions.

Staff-seeded discussion questions that rotate across community boards to spark engagement.

Lookup Portal admin interface for managing seeded discussion questions.

Analytics to measure onboarding effectiveness.

Auto-generated welcome content for community boards.

Allow community discovery pre-verification. Verification unlocks contribution, not belonging.

Core tables, champion connection preferences, settings UI.

Send, receive, accept, ignore, and cancel connection requests.

Transform Messages into Connections with two-tab inbox.

Surface connection availability in Directory and Profiles.

Migrate mutual contacts to connections, remove Contacts system.

Staff visibility into connection program health.

Content model, seed data, and pack generation service.

Dashboard card with State A (no role) and State B (role selected) variants.

Public roles page and staff management interface.

9 string replacements and 3 email template rewrites for source-aligned copy.

FAQ, empty states, flash messages, landing page, and wizard copy.

Three-tier model (Member/Champion/CL) derived from existing data; 8-stage journey engine cached in DB.

New Cp::HomeController + /home route with stage-aware views and 3-tier visual card hierarchy.

Unified discussions/news/photos feed with recency + engagement scoring.

Stage partials for onboarding, exploring, connecting, and engaged member journeys.

Contextual prompts, champion recognition badges, and role ideas in digest emails.

New member welcoming for community leaders.

Contextual nudges guiding Tier 1 Members toward Champion opt-in, plus 3-page Champion Role microsite.

Dashboard freshness signals, milestone celebrations, connections sidebar redesign, and community activity badges.

Status enums, submission fields, thread/message models.

News and event submission forms, CTAs, submission history.

Staff review interface with tab-filtered queue and actions.

Email notifications, in-app notifications, and 'Submitted by' attribution.

All card/panel containers converted from rounded-xl/2xl to rounded-md.

bg-gray-50 border-b headers added to show-page cards.

ALL CAPS section/form labels removed; standardized to Title Case.

Cosmetic content-area gradients replaced with flat design tokens.

In-app policy pages (ToS, Privacy, Community Guidelines, Cookies) with versioned consent tracking at registration and re-consent mechanism.

Privacy enum for education records with 3 levels (show all, hide year, hide all). Ripples into directory, search filters, and matching services.

True account deletion replacing privacy-only stub. Discussion posts anonymized to 'Former Member', PII purged. Plus 'Download My Data' JSON export.

Unsubscribe language in all email footers, full physical address in text emails, List-Unsubscribe headers.

Content Security Policy (report-only), Permissions-Policy, Referrer-Policy headers enabled.

Age confirmation checkbox at registration (18+). Records attestation timestamp.

Publicly accessible /champions page that educates visitors about the Alumni Champions program.

Update / landing to articulate two-tier value proposition (join network vs. become Champion).

Remove public /signups/* flow, preserve ChampionSignup data conversion pipeline.

Document ChampionSignup data pipeline, preserve staff management tools.

Finalize field mapping, derivation rules, and API compatibility contract before schema work.

Create Education and EducationAreaOfStudy schema and associations alongside legacy tables.

Stand up new CRM education + areas-of-study CSV importers with background-job pipeline, polled status page, and downloadable gap CSV.

Centralize old-field derivation (ug_*, gr_*, pref_college) from the new model.

Preserve current lookup API payloads while moving internals to the new education model.

Move Degree Stats and engagement analytics aggregations to a shared Education::AggregateScope query object (Education-first w/ Degree fallback). Stats UI gets a side-by-side ?source=legacy|education toggle and coverage banner so parity is visible before cutover.

Migrate the data-export surfaces (Alumni CSV, Event RSVP CRM converter, AlumniFilterService) from legacy degree joins to the AggregateScope + EducationProfile stack established in 18.6.

Move per-enrollment current-student data (school, program, intended degree, expected graduation year, per-record student_status) out of denormalized alumni columns and into the educations table. Retire Csv::CurrentStudentImporter in favor of a single education-feed pipeline.

Freeze the legacy degrees/majors/colleges read path: retire the side-by-side stats toggle and coverage banner, migrate every remaining per-record and filter read onto Education::AggregateScope + Alumni::EducationProfile, and keep the EducationProfile fallback + physical tables until a later cleanup tag (coverage ≥ 99%).

Add 7 new columns to champion_signups, wire domain-scoped routes under public/ namespace, scaffold the controller with all step stubs, and render the landing page.

Steps who_you_are, belmont_experience, and where_you_are are live with simplified data capture. Record is created on step 1 and tracked via session.

Role hub (direct pick or 7-question quiz), quiz results with recommendation, light interest capture, and a role-celebrating confirmation page — all under the public/ namespace.

Full affinity browse/search on the Interests step, source tagging, and email delivery on completion. Replaces the 19.3 light-interest checkboxes with the full affinity dataset and restores the signup mailer.

Confirmation UX and staff review surfaces finalized, including secure no-role follow-up and expanded queue filters.

Post-feedback UX polish based on user testing of the full signup flow.

Move signup completion up to a single Congrats/Profile page reached right after contact info. Drops the Belmont Experience step, and the same page doubles as a returnable, on-demand-link 'update your info' profile for the remaining optional sections.

Replace the single-winner role quiz with an interest spectrum across the same 4 areas, shown on both the public results screen and the staff admin side.

DB-backed feature flags with a Champion Admin toggle UI. Infrastructure only — no gating yet.

Controller guards, community-page reflow, nav/footer links, dashboard events sidebar, activity-feed filtering.

Roles microsite, dashboard role ideas + role card, wizard role-step skip, Your Impact card.

opportunities + opportunity_responses tables and their models. Nothing routed or publicly reachable.

Staff author opportunities in the admin — copy, questions, and the live/off toggle — instead of a developer ticket and a deploy.

The CMS relocates into the Signup Admin shell and the responses queue lands beside it, so staff do the whole job in one place.

The anonymous-capable public form at alumnichampions.com/opportunities/:slug, its thank-you page, and the conversion loop into the existing signup flow.

Returning signups see live opportunities on their profile hub, pre-filled and attributed.

Three limits the 21.1–21.5 MVP left in place, each hit by staff running live forms. Questions could only take one answer. Activating a form was the same switch as advertising it, so a board-only or newsletter-only opportunity was impossible. And responses only reached people with a Lookup Portal account, which the person who owns a given opportunity often isn't.

Staff were typing the three facts an alum most needs — when, where, and what we're actually asking — as hand-written lines at the top of the intro copy. That made them formatted differently on every form, present nowhere except the form itself, and impossible to sort or expire by. An alum who said yes to an event had no record of the date anywhere but the page they had just navigated away from.

21.8 made the event details structured; it rendered them as a plain label column, which read as an afterthought beside the Alumni Network's event listings. And because Where is one text field, a real venue arrived as a run-on grey line with the street address crowding out the name anyone actually reads.

Give StaffNotification the UI it never got — a real per-user inbox with a receive → clear → gone flow.

One dropdown, two halves that must not be merged: a clearable feed above the standing queues.

Wire the mature CrmDataChange pipeline to the signup flow. Linked signups only — a change Advancement Services can't attach to a constituent is unusable.

Diff signup-reported employment against the Phase 24 employments table, and student orgs against alumni_affinities.

Surface unlinked signups as 'needs identity match'; linking one retroactively runs the CRM logger so the held update isn't lost.

employments + employment_import_batches tables and their models. Nothing routed or reachable.

Csv::EmploymentImporter — the parse, gap classification, and the per-BUID replace that keeps employment current instead of accumulating.

Settings → Data Imports → Employment (CRM): the same background scan → preview → commit flow as the 18.3 education imports, with the delete count made impossible to miss.

Employment card on alumni#show, after Degrees — all current rows, most recent first.

The point of the whole phase: find alumni by where they work, tolerant of partial input and misspelling.

Alumni::SignupProfile — one canonical signup per alum and every derived value read from it. Nothing routed or visible.

alumni#show finally shows what v2 collected: effective location, interest leaning, self-reported groups, signup history.

District and affinity search stop being blind to what alumni told us.

The export carries what the alum said, beside — not instead of — what the CRM holds.

Six options describing v1's five-step wizard become one question: did they fill out the form?

A rename removes today's collision; a test prevents tomorrow's. The cheapest item in the phase and the only one that enforces rather than describes.

Split the signup ecosystem by audience, not auth state. public/ described the wrong axis — signed-in returning-visitor pages lived there too.

Corrects a false premise in the phase spec — that every file belongs to exactly one app. It is false for the core domain objects, and the walls were causing the misroutes.

The collision the hold gate exists for. Renames the Alumni Network Admin after the product it administers. Held surface — explicit approval granted for this named scope.

The documentation half of the refactor-vs-document question. Not an alternative to 23.1–23.4 — it is what makes them navigable, and it has to record a cut, not just renames.

Ships first. A front door for a mechanism that already worked, plus the metering the rest of the phase depends on.

Prevent what can be prevented before the submit, resolve the rest staff-side, and stop a merge from silently killing the link that got them there. No create-time merge — the prevention happens before, the resolution after.

Upgrades the 2-week session 27.2 shipped into a 6-month remembered device, with the recognized/verified split that makes a long-lived cookie safe on a shared machine. Shipped as one release with 27.6, because the cookie ships with its disclosure or not at all — and that coupling is now asserted in tests rather than left to a launch checklist.

Brings the recognized tier to the form that collects the most contact data. Half of the original scope turned out to already exist — 21.6 shipped the anonymous responder's account offer — so what was actually missing was that the opportunity controller had never adopted 27.3's tier model. It still carried the private current_signup it was written with in 21.2, resolving only verified credentials, so the alum the header greeted by name was an anonymous stranger one click later.

What a signed-in alum can see and do about their own record. Sign out already shipped in 27.2/27.3, so this is the responses list and the device list — both built entirely on what 27.3 already put in place.

Reverses Decision B. The recognized tier — a 6-month cookie deliberately weaker than a session, granting a first name and a masked email but never the hub — was the single largest source of complexity on this surface, and its own premise did not survive the device-list cut: that feature was dropped because 'they can just sign out', which is exactly the mitigation the tier existed to avoid depending on. Passwordless was never the cost and does not change (Decision A) — a password would add a credential people forget on a conversion funnel plus a reset flow, and a password reset flow IS a magic link, so the mechanism would stay and a second one would join it.

Written against the shipped 27.7 flow rather than against a spec — somebody walked it and found four things. Three of the four turned out to be the same defect wearing different clothes: a SECOND COPY of a decision, each of which had drifted within one sub-phase of being created. A second sign-in form (27.2 put one on the landing page and 21.6 inlined a third on the thank-you page; 27.7 then added the code box and the consent checkbox to only one of them, so submitting either copy produced an email whose main instruction pointed at a page with nowhere to follow it). A second call to action (the landing page kept selling 'Get Started' under a 'Welcome back, Chip' banner — and that button carries no signup_token, which handle_who_you_are reads as 'creating', so following it opened a second signup under the same address). A second reading of 'home' (the header logo and sessions#create each decided independently). The fourth was a comment documenting a second copy, which leaked onto a public page. The rule that would have prevented all four is already in CLAUDE.md §7; what this adds is the operational form — when a page needs a control another page already has, LINK to that page, do not copy the control. Two of the three fixes were simply deleting the copy.

Shipped in the same release as 27.3. The March cookie policy said 'that's it — one cookie'; this adds a second, and corrects two other statements that had quietly become untrue.

Ships first — auto-linking a verified identity is unsound while an address can name two rows. A partial unique index on LOWER(email) WHERE deleted_at IS NULL, matching scope :active exactly.

The payload. One callback at /auth/signup_google/callback — a second provider name, because the portal's callback already claims /auth/google_oauth2/callback on the signup domain and narrowing its constraint would be a held-surface write.

Step 1 shortens to identity-only, which also repairs a live defect: ZIP has been a step-1 field since about November 2025, and calculate_status returns 5 ("Completed") the moment ZIP is present. Five active rows reported Completed having done only step 1.