Samanvay: what we built, and how to try it

For the CRM2 team. 21 Oct 2026. All names and numbers in the demo are invented.

This is a demo. Try it, then send us your notes. Nothing here changes your own code or data.

2main apps: Leads and Teams

4demo accounts

6languages in the home screen

0.97 sto open Leads, desktop test, 20 Oct (was 1.88 s)

1. What this is

Samanvay is our proposed name for the CRM2 volunteer app. The group decides (section 8). Same code, same team.
We added new apps to its home screen. Leads and Teams are the main ones.
Each app has an on/off switch. You see only the apps your role may use.

Open the demo

Works best on a phone. A desktop browser also works.

Samanvay home screen with the Leads, Wisdom, Resources and Ask AI tiles

2. Try it

Open crm2-proto.anantmb.workers.dev. Sign in with one username below.

Password for every account: Jaigurudev123

Persona	Username	Try this
Teacher	`tour.teacher`	Open Leads. Tap Call on a lead. Open Survey. Look at your own QR. Open Teams. See your centre.
Volunteer	`tour.volunteer`	Open Seva. Sign up for a shift. Open Seva Rides. Tap Need a ride. Open Promote. Share a video.
Second volunteer	`tour.volunteer2`	Open Seva Rides. Tap Offer a ride. Answer the first volunteer's request. Go to Home on both phones. Watch the bell.
Coordinator	`tour.coordinator`	Open Leads. See the whole centre. Open Admin. Read Support requests. Open Announcements. Post a notice.
Admin	`tour.admin`	On Home, tap Turn apps on or off. Switch Promote off. Go Home. The tile is gone. Switch it on again.

Tip: for the two volunteers, use two phones or two browsers.

3. The apps

Each tile on Home opens one app. You see only the apps your role may use.

An org admin can turn any app off. Go to Home > Turn apps on or off. The tile hides at once. No rebuild.

Main apps

Leads

Follow up with people you invited. Call or WhatsApp in one tap.

Try

Tap Leads. Find "Assigned to you".
Tap Call or WhatsApp on a lead.
Tap Keep/share. Keep it, or share it with your centre.

One lead per phoneDo not contact needs a reasonUndo the last stepClosed list with reason

Teams

Your centre and its team. Invite people. Set the centre's place on the map.

Try

Tap Teams. See your centre.
Tap Add team member.
Change "Days before an idle lead returns". Tap Save days.

More apps

Survey

The Happiness Survey. Each teacher makes their own QR link.

Tap Survey.
Open your QR.
Tap Results.

Seva

Seva you can join near you. Sign up, check in, log hours.

Tap Seva.
Pick This week.
Open a card and sign up.

Seva Rides

Shared rides to programs and seva.

Tap Seva Rides.
Tap Search near here.
Tap Need a ride.

My Programs

Programs you run or attend.

Tap My Programs.
Open a program.
See who comes.

Find Programs

The Art of Living program catalog.

Tap Find Programs.
Search a program name.
Open one.

Announcements

Notices from registered centres. Filter by centre.

Tap Announcements.
Read the newest.
Teachers: post one.

Promote

Videos, posters, your program links and ready messages.

Tap Promote.
Pick Videos.
Tap Share.

Admin (staff only)

Accounts, support requests, return rules, data import, connected apps.

Sign in as coordinator.
Tap Admin.
Open Support requests.

Profile and account

Your details and your language.

Tap the round initial at top right.
Change the language.
Open any app. It uses your language.

Apps from the CRM2 team

These tiles show demo data in this demo.

Wisdom · talks by GurudevResources · posters, videos, templatesAsk AI · find or create anythingVTP · Volunteer Training ProgramCentres · find a centreEvents · events and sign-up

4. How it fits together

One home. All apps open from one tile screen.
One top bar. Back, app name and account look the same in every app.
Your tiles only. The app list is read at sign-in. Your role decides the tiles.
Off without a rebuild. An org admin switch hides a tile. An added app then answers "not found".
Two teams, no clash. CRM2 modules and added apps keep separate data. They meet only in the home screen and through APIs.

5. What changed in CRM2

Item	Before	After	Why
App list	The tile list was fixed in code.	Home reads the list at sign-in.	A team adds an app with one row in its own list. One id row in the shell, which a check keeps equal.
On/off switch	Every person saw every tile.	Each app has a permission and a switch.	An admin hides an unready app in one tap.
Top bar and app frame	CRM2 modules shared one header. AOL was a separate site with its own bar.	AOL apps open under the same top bar. Their own bar is hidden.	Every app looks like one product. App teams build no header.
One web address	The shell talked to CRM2's own backend only.	Added apps run under the same address.	One sign-in, one cookie, no cross-site setup.
Icons and languages	Generic icons. English and Hindi.	Sunburst icons. Six languages in the Samanvay build: English, Hindi, Marathi, Telugu, Gujarati, Kannada.	One look, and the languages volunteers speak. The last four are drafts.
Speed	Sign-in 1.12 s. Open Leads 1.88 s.	Sign-in 0.57 s. Open Leads 0.97 s.	A tile tap no longer reloads the whole page.

Speed: median of 3 runs, desktop browser at phone size. Phones were not measured. Timed on the 20 Oct builds; the current build is not re-timed.

Changes to the CRM2 core

Part 1: the Samanvay shell. Part 2 (AOL split) follows.

A board with sockets; teams plug tiles in; one switch dims a tile.

RegistrySwitchDoorOne frame

The core becomes a plug-in board

173 files+11,126 / −375

9 → 17tiles

2 → 6locales · VITE_SHELL=aol

≈2 s → ≈1 sopen an app · desktop · before one-frame

Overview: phone, shell with bar, grid, registry, door and frame, binding, AOL Worker and D1

Plug in

2.1 Tile = data row

Registry diagram: 8 dev edits; mounted AOL app needs one shell id row

Dev: 8 edits · native tile: 10+ stepsWithout: Every tile ships shell

Row carries permission and switch

2.2 One switch

Switch diagram: edit code and deploy before, one tap after

Deploys 1 → 0Without: Faulty app stays on

Bad app off in one tap

2.3 Admin > Apps

Admin Apps flow: org admin toggles AOL D1 switch; grid refetches

5 files ≈+270Without: Only developers switch

Org admins switch tiles

2.9 AOL registry

AOL app registry: shell keeps lists; check catches id and path drift

Shell classifier removed · drift caught by checkWithout: Two lists drift

Shell keeps app lists; check pins ids and paths

One frame

2.4 One bar

Shell bar diagram: before, AOL was a separate site with its own bar; now AOL pages sit under the shell bar

AOL apps under the shell barWithout: AOL stays a separate site

AOL's own chrome stays hidden

2.5 Door + frame

Door and frame: one first-party AOL session, five frame-to-shell and two shell-to-frame messages

Sign-ins: 1 (AOL's session, first-party)Without: Separate AOL site

One origin, one session

2.6 Speed

Desktop speed measurements from before one-frame; SPEED-5 and deploy-1022 were not timed

Sign-in 1123 → 572 ms · desktop, before one-frameWithout: ≈2 s every tap

Deploy-1022 one-frame state was not timed

2.8 Bell

Notice count appears only on Home; tap opens Notices in the frame

4 files ≈+150Without: Notices go unseen

Notice seen from Home

Look + proof

2.7 Languages

Locale choices: 2 to 6 in the AOL shell build only; 4 drafts

Locales 2 → 6 · AOL shell buildOther builds: en + hi

Six locales in the AOL shell build

2.10 Flows + chunks

Shell flows run against deployed proto; chunk count is checked at build time

17 chunks checkedWithout: Breaks found on phones

Breaks caught before team release

2.11 Other edits

Seva → Samanvay: own PR, refusable
Leads link
Local stubs: never ship
rbac test +2

26 files +84/−69Without: Brand forced on team

Brand change can be refused alone

≈ marks an estimate. Speed figures are desktop measurements from before the one-frame change; deploy-1022 was not timed. Phones were not measured.

Changes to the AOL app: one PR per app

Part 2. Part 1 is the CRM2 shell above. The real cut is AOL-Connect-app b48d7e60 at integration tip eefb3ef4: 1,729 files, +275,738 lines vs dev f27a587e. Fair-run rows remain 55df3634 vs afcf4e05; add/remove compare 55df3634 with b48d7e60 after PRs #395–#397.

A central hub; teams carry blocks that dock to it; one block is dimmed.

CoreApps plug inOne PR eachSwitch off

One core, apps plug in

15 PRs1,729 files · +275,738 lines vs dev f27a587e

4,341 passintegration · 0 fail · core UI alone 466 pass · Leads bulk 1,931 pass

50 → 6hand-written core → app imports · afcf4e05 → ba3653b5

11/16 → 6/14conflict files / hunks · fair run · afcf4e05

Honest rows: total core → app imports rise (50 → 57), Leads first load is 301 B larger, and /app is 4.1 ms slower in the fair run. The add/remove recipe counts below use 55df3634 vs b48d7e60. The gain is where the links sit and who can switch an app off. Removing an app touches more files (44 → 85: the Rides tests, pages and flows now move with it; core 8 → 5, reviewer 44 → 5).

Since #394, the generated lists merge with 0 conflicts (ba3653b5).

Structure

A.1 Folder tree

Real cut b48d7e60: 1,729 files and +275,738 lines vs dev f27a587e.

1,729 files · +275,738 lines vs devWithout: Apps mixed in src/ and frontend/src/

Apps move out; core keeps listed leftovers

A.2 Plug-in board

Nineteen app ids plug into twelve hook keys; apps:list writes six generated lists.

19 ids · 12 hook keys · 6 generated listsWithout: Hubs import every app

Apps plug into twelve hook keys

A.3 Import graph

Hand-written core-to-app imports fall from 50 to 6 and app-to-app from 2 to 0; the total core-to-app count rises from 50 to 57 because generated lists name each app. Commits 55df3634 and ba3653b5.

Hand-written hub imports 50 → 6 · app → app 2 → 0Without: Worse: total core → app 50 → 57 (generated lists)

Core imports no app by hand

A.4 One owner per app folder

Path	Owner (proposed)
`core/`, migrations, scripts, tests	aol-core
apps/leads	aol-leads
apps/teams	aol-teams
apps/programs	aol-programs
apps/survey	aol-survey
apps/seva, apps/rides	aol-seva
apps/announcements, apps/promote	aol-comms
apps/admin	aol-core

Each folder has one ownerWithout: all code in one review lane

Owner names are proposed; no CODEOWNERS file in the cut. The boundary check fails a new cross-app import.

The PRs

Fifteen AOL split PRs. Real cut b48d7e60: 1,729 files and +275,738 lines vs dev f27a587e; non-integration PR review scope runs from +897 to +46,935 lines.

PR 6 Tooling

Build, scripts, CI

Alone: not run alone; tested in core UI chain (466 pass / 0 fail)

75 files · +31,835 lines · base dev · tip edf81d77

Read first: package.json, then ci.yml

Without: No app builds or runs the boundary check

PR 7 Core server

Server core, 87 migrations

Alone: not run alone; tested in core UI chain (466 pass / 0 fail)

301 files · +33,109 lines · base tooling (PR 6) · tip 5280b3f0

Read first: core/server/app-registry.mjs

Without: Nothing runs

PR 8 Core UI

Client core, UI kit, built bundle

Alone: 466 / 0 (was 427 / 220)

266 files · +19,082 lines · base core (PR 7) · tip 5ab4eefa

Read first: the two registry readers

Without: Core alone fails 220 tests

PR 9a Leads

Queue, detail, follow-ups

Alone: tested with Leads bulk (1,931 pass)

237 files · +46,935 lines · base core-ui (PR 8) · tip 2fbfe484

Read first: two registration files, then routes

Without: No Leads tile

PR 9b Leads intake

Intake, ads, coverage

Alone: tested with Leads bulk (1,931 pass)

36 files · +9,186 lines · base leads (PR 9a) · tip e0c919f1

Read first: server/apps/leads-intake.mjs

Without: No intake or ads screens

PR 9c Leads bulk

Import, export, refer

Alone: core + Leads 1,931 / 0 (was 189 / 120)

23 files · +7,121 lines · base intake (PR 9b) · tip 6c28f269

Read first: server/apps/leads-bulk.mjs

Without: No CSV import or referrals

PR 10 Teams

Team tree, invites, centre profile

Alone: 2,064 / 0

70 files · +9,402 lines · base leads-bulk (PR 9c) · tip 24e170dd

Read first: server/apps/my-centres.mjs

Without: No Teams tile; Admin cannot land

PR 11 Programs

My and Find Programs

Alone: 697 / 0

94 files · +17,613 lines · base core-ui (PR 8) · tip 727594b3

Read first: both registrations, then apps/programs/routes/events.mjs

Without: No programme pages

PR 12 Survey

Happiness Survey, form builder

Alone: 505 / 0

67 files · +7,911 lines · base core-ui (PR 8) · tip afc07b01

Read first: server/apps/survey.mjs

Without: No Survey tile

PR 13 Seva

Callouts, shifts, roster, safety

Alone: 570 / 0

93 files · +14,181 lines · base core-ui (PR 8) · tip da4bba91

Read first: server/apps/seva.mjs (hooks)

Without: No Seva tile; Rides cannot land

PR 14 Rides

Ride offers, needs, notices

Alone: 619 / 0

78 files · +8,735 lines · base seva (PR 13) · tip f43a9ebe

Read first: server/apps/rides.mjs (cron, notices)

Without: No Rides tile

PR 15 Announcements

Announcements tile (the template)

Alone: 479 / 0

36 files · +897 lines · base core-ui (PR 8) · tip e0fd3c28

Read first: all 7 app files: copy this PR for a new app

Without: No Announcements tile

PR 16 Promote

Videos, posters, links, messages

Alone: 485 / 0

48 files · +1,877 lines · base core-ui (PR 8) · tip 5d7d35db

Read first: server/apps/promote.mjs

Without: No Promote tile

PR 17 Admin and profile

Staff hub, own profile

Alone: 2,114 / 0

73 files · +8,087 lines · base teams (PR 10) · tip 8710a88a

Read first: both registrations; the one declared link

Without: No Admin hub or profile page

PR 18 Integration

Integration tip equals the whole moved tree

Alone: 4,341 / 0

1,729 files · +275,738 lines · base dev + 6 leaf tips · tip eefb3ef4

Read first: test names only

Without: No proof the apps work together

Alone = tests of core plus the apps on the branch chain, in a separate checkout. Tips, bases, sizes and pass counts use branch-status.md, table “real cut b48d7e60”. Leads and Leads-intake were tested with Leads bulk (1,931 pass).

Workflows

C.1 Add an app

Add demo-x: 12 to 7 files, core files 4 to 3, reviewer files 11 to 3; lines +26/-11 to +20/-0. Build and suite pass.

12 → 7 files · core 4 → 3 · reviewer 11 → 3+26/−11 → +20/−0 lines · build and suite pass

4 app files; 3 generated lists stay committed

C.2 Remove or switch off

Remove Seva Rides: 44 to 85 files, core files 8 to 5, reviewer files 44 to 5; apps/rides and locales/rides hold its code, tests, pages, flows and words. Switch-off remains one tap in the CRM2 shell for mounted apps when EMBED_ENABLED is 1, with Seva exits kept open.

Core 8 → 5 · reviewer 44 → 544 → 85 files · +61/−4,062 → +0/−10,505 lines · build and suite pass

The Rides and locales/rides folders hold all its code, tests, pages, flows and words; deleting them removes all.

Off in one tap, no deploy

C.3 Review and merge one app PR

Review size falls from +275,738 lines for the whole cut to +897–+46,935 lines per app PR; in the fair run, conflicts fall from 11 files and 16 hunks to 6 and 14.

Conflicts 11/16 → 6/14 (fair run)Without: One +275,738-line review

Each team reviews its folder only

C.4 A user opens an app

A tap on Leads goes through the shell door and service binding to the AOL Worker; if the app is switched off it answers 404, else the registry route reads AOL D1.

No behaviour change · Leads open 0.0574 → 0.0546 sWithout: Core knows every app

Same tap, registry finds the app

C.5 Database migrations

Eighty-seven migration files stay in core; 0645 is file 58 of 87 and 0666 is file 77, shell_handoff plus app_switch.

One ordered line, held by coreWithout: Two apps pick the same number

All 87 migrations stay in PR 7

Benchmarks

Metric	Before	After	Why
Core → app imports, all	50	57	Generated lists name each app (51 of 57). Hand-written: 50 → 6 (afcf4e05 → ba3653b5).
Add demo-x: files / core / reviewer	12 / 4 / 11	7 / 3 / 3	Lines +26/−11 → +20/−0; build and suite pass. 55df3634 → b48d7e60.
Remove Seva Rides: files / core / reviewer	44 / 8 / 44	85 / 5 / 5	Lines +61/−4,062 → +0/−10,505; build and suite pass. The Rides and locales/rides folders hold all its code, tests, pages, flows and words; deleting them removes all.
Leads first load (gzip B)	109,541	109,842	55df3634 → ba3653b5; +301 B, inside the 109,850 B budget.
/app page (local)	0.0302 s	0.0343 s	+4.1 ms; no cause isolated.
Sign-in to 303 (local)	0.0376 s	0.0381 s	+0.5 ms; no cause isolated. Leads open is faster: 0.0574 → 0.0546 s.

Not measured: per-app test time (run only one app's tests). Fair-run rows (build, sign-in, Leads open, /app page) are 55df3634 vs afcf4e05, median of 3, same machine; they were not re-run on ba3653b5. Fair-run conflicts: 11/16 → 6/14 (55df3634 vs afcf4e05). Add/remove compare 55df3634 with b48d7e60 after PRs #395–#397. Local times are local-stack times, not phone times. The core-name guard (tests/core-names-no-app.test.mjs) covers 5 apps: Seva, Survey, Announcements, Promote and Rides. By rule, the /health schema probes name Seva, Survey, Announcements and Rides. Core still deliberately names Leads and Programs for the lead store. Ten Seva form JSON files still sit in core (frontend/src/forms); a follow-up will move them. The changed core and reviewer files are committed generated lists (*.gen.*) because deploys run no build step.

6. User manual

How to read this. Each block is one app. Steps are in order. Each picture shows the screen for that step. All names and numbers are invented demo data. The pictures show the app on its own. In the demo the Samanvay top bar replaces its header and bottom bar. In the pictures, Teams is called My Teams.

Leads for volunteers and teachers

Goal: Add a person, call them, log what happened.

Open Leads. Active leads show first. Closed leads have their own tab.
Tap + Leads. Type a name and a mobile number. Pick how you know them, and write a short comment. The comment is required.
Tap Send 1 to my team. A number your organisation already holds is skipped, and the screen says so.
Search by name or phone. Tap Filters to narrow by status, program or source.
Open a lead. Tap Call or WhatsApp. WhatsApp fills a message from a template. Tap Open WhatsApp to send.
Tap Log. Pick the outcome, add a comment, then tap Save update. Tap Undo in the bar if you tapped wrong.
To stop all contact, pick Not interested and tick the do-not-contact box. The lead closes and shows Do not contact.
Tap Keep/share to keep a lead, show it to your team, or open it to the team. Tap Save.
Tap Assign to give a lead to someone else. Pick a team or a person, then tap Take this one or the assign button.

Teams for team coordinators

Goal: See your teams, add a team, add a person.

Open Teams. You see each team with its calls and registrations, and the people in your area.
Tap Add a new team. Type a name. Pick a map place if you want one. Tap Add team.
Tap Add team member. Type a mobile number and pick a role. Tap Add. Anybody already in the app joins at once. A new number gets an invitation on WhatsApp.

Announcements for teachers

Goal: Post a notice at one centre.

Open Announcements. Tap New announcement.
Pick the team. Type a title, pick a date and type a message. Tap Post.
Everyone can read it in the same screen. You can edit or remove your own notice.

Find Programs for everyone

Goal: Find a program by place, language or PIN code.

Open Find Programs. Sessions for the next 30 days show first, grouped by when.
Type a place, language or PIN code in the search box.
Tap the chat button on a session to share it on WhatsApp.

My Programs for teachers

Goal: See your sessions and share them.

Open My Programs. You see coming up and running sessions, and weekly sessions.
Tap a session for dates, place, contribution and who to contact.
Tap Share on WhatsApp to invite people. You can also set a map place or look at rides and seva for the session.

Promote for volunteers

Goal: Find links and material to share.

Open Promote. Tap My links to see your own link and how many clicks and registrations it has.
Tap Videos to find a video. Use Kind, Language and Max minutes. Tap Share.
Posters and Messages are in this demo with sample data. The real posters and texts come later.

Seva Rides for volunteers and riders

Goal: Offer or ask for a ride to a session.

Open Seva Rides. Pick My location, My centre or PIN code, and a distance.
Tap Search near here. Pick Going or Coming back. Open a ride to ask for a seat.

Seva for volunteers and coordinators

Goal: Find seva near you and sign up. Coordinators add seva.

Open Seva. Tap Near me or Near my centre. Use Any date, This week or 30 days to narrow it.
Open a seva. Tap I will do this. Tick that you are 18 or older. Tap I will do this again.
Coordinators (and volunteers, where allowed): tap Add seva opportunity. Pick the team, the kind of seva, the time and how many people. Tap Add a shift for more times.
Tap Publish. The seva shows in the list.

Survey for teachers

Goal: Make a link or QR code for a survey and read the answers.

Open Survey. Ready-made forms are listed. Tap Survey for another source.
Pick a form and a source. Set how many days the link works. Tap Make the QR.
Share the link or the QR. Tap Copy link or Share on WhatsApp. Tap Stop this link to close it.
Tap Results to see the answers and the new leads that came from the survey.

Profile and account for everyone

Goal: Change your language, see your profile, ask for a change.

Tap your round account button at the top right. Pick a language from the six listed. The screen changes at once.
Open Profile and Account. To change your name, areas or PIN codes, send a request. An admin approves it.

Not in this manual yet: Admin, Wisdom, Resources, Ask AI, VTP. Posters, messages and videos in Promote show sample data.

7. For developers

Architecture (team target; in the demo CRM2 tiles use mock data)

The shell (apps/volunteer2-fe) owns the sign-in screen, the top bar, the tile grid and the app frame. AOL checks the account.
CRM2 modules use volunteer-be and Postgres, as before.
Added apps run in the AOL-Connect Worker on D1.
Both sit under one address, so every cookie is first-party and no CORS is needed.

How an app plugs in

Add one row to AOL's app list (src/routes/apps.mjs) and the same id to the shell list (packages/app-registry). A check keeps the two equal.
GET /api/apps returns only the rows this person may open.
A tap opens /x/<id>/. This "door" checks the session and the switch.
The shell draws the top bar. The app page loads below it, with no bar of its own.
The page talks back with 5 messages only: back, ready, title, badge, language. The shell sends 2: open and language. Each is checked.
Switch off: the tile hides. The door and the app's API answer 404.

The PR plan: 21 branches, app by app

Every branch opens a PR into feature/samanvay, not into dev. One bad PR then cannot break dev for the team.
When all 21 are merged and the team agrees, one PR merges feature/samanvay into dev.
Shell (1 to 5) and AOL core (6 to 8) go at the same time. Then one PR per app, each on core. Leads and Teams first.
Leads is too big for one PR. It goes as three stacked PRs: 9a, 9b, 9c. Each passes its own tests.
Teams comes after Leads. Its centre view reads the Leads API.
All database steps (87 migrations) go in the AOL core PR (7). D1 applies them in one fixed order.
AOL code stays outside the team's pnpm workspace. Its own CI lane runs its build and tests.

#	Branch	What it adds	Lines (estimate, before the app split; re-cut pending)
1	`feat/app-registry`	Runtime app list, permission per tile, switches, Admin › Apps	~1.9k
2	`feat/shell-bar-frame`	Top bar, app frame, door, Home and Back, sign-in handoff	~2.1k
3	`feat/shell-brand-icons-i18n`	Samanvay brand, Sunburst icons, six-language shell	~5.3k
3b	`chore/brand-samanvay`	Seva → Samanvay in team apps (the team may refuse this one alone)	~0.2k
4	`perf/shell-speed`	Cached assets, boot data in the page, one chunk per module	~0.3k
5	`test/shell-flows`	Browser flows for the shell	~0.7k
6	`chore/aol-core-tooling`	Package, seeds, invented test data, boundary check, CI lane	~16k
7	`feat/aol-core`	Auth, session, scope, roles, people, lead store, all migrations	~25k
8	`feat/aol-core-ui`	UI kit, router, store, core texts	~14k
9a	`feat/app-leads`	Lead queue, detail, follow-ups, status	~32k
9b	`feat/app-leads-intake`	Intake, ads, coverage, lead sources and fields	~27k
9c	`feat/app-leads-bulk`	Import, export, refer, offline book	~12k
10	`feat/app-teams`	Team tree, members, invites, centre profile	~10k
11	`feat/app-programs`	My Programs and Find Programs	~21k
12	`feat/app-survey`	Happiness Survey and form builder	~11k
13	`feat/app-seva`	Seva callouts, shifts, roster, safety	~14k
14	`feat/app-seva-rides`	Ride offers, needs, notices	~10k
15	`feat/app-announcements`	Announcements tile	~1k
16	`feat/app-promote`	Videos, posters, program links, messages	~2.3k
17	`feat/app-admin-profile`	Staff hub and own profile	~12k
18	`test/aol-integration`	Tests that cross two or more apps	~26k
	Total	estimate, before the app split; re-cut pending	≈245k

What stays in the demo only

Stays in the demo	What the team uses
Demo sign-in with AOL accounts (the stub code is for local tests only)	CRM2's own sign-in. The added apps accept the shell's handoff.
Our AOL sign-in screens inside the shell	None. A CRM2 person maps to an AOL user by verified phone. A handoff never creates an account.
Local stub of the CI SDK and the demo Worker config	The real CI SDK and the team's own config.
The link to our own demo database	The team links its own AOL-Connect Worker and D1 per environment.
The name "Samanvay" in team-owned apps	Only if the group agrees (branch 3b).

8. What is next

The team tries the demo and sends notes.
Core PRs (6 to 8) open first. Then one PR per app on core. Leads and Teams first.
The user manual covers Admin, Wisdom, Resources, Ask AI and VTP.
Hindi is checked. Then Marathi, Telugu, Gujarati and Kannada.
The group decides on the name, and on D1 for new apps.