← Back to the MOM demo · raw .md

# MOM (mom.veridian-aios.com) - design note, 7 Nov 2026

Folder: `C:\ct\mom-aios` (outside every git repo). Local only: no deploy, no DNS, no push.

## 1. What already existed (10-line finding)
1. Searched `C:\ct\aoa-rwa`, `C:\ct\aoa-rwa-demo4`, the memory notes and `C:\ct\ct\src`.
2. **compliance-tracker** has a real meetings feature: `src/app/(app)/veri-meetings`, `src/app/api/veri-meetings/[id]/{action-items,audit-log,export,generate-intelligence}` and a `veri-meeting-service`.
3. Its action item holds only title, assignee user id and due date. It has no status, no updates, no last update and no per-change log.
4. It is tied to Next.js, Drizzle, Supabase, tenant context and user ids. It cannot be lifted into a free Cloudflare product, and it uses mobile/user-id style accounts.
5. A separate PMS/PROJEXA meetings API (`/api/pms/meetings`, `outcomes`) is construction-project specific.
6. Townhall (`aoa-rwa`, `aoa-rwa-demo4`): its "minutes" screen (`lib/stages-meeting.js`) is marked DESIGN only; the engine has no written minutes and no follow-up points.
7. Nothing was found in memory notes or old sessions for "Minutes of Meeting" or "Points of Action".
8. Reused: the idea of an audit log per meeting (veri-meetings audit-log), the Townhall demo layout (zero-package Node server, start/stop cmd, sample data), brand colours and fonts.
9. Not reused: any code from compliance-tracker (wrong stack, wrong data model).
10. So the owner's "built earlier" is partly true: meetings with simple action items exist in the compliance product, but not this MOM product.

## 2. Screens
Sign in (e-mail code only) -> My MOMs -> Create a MOM -> MOM page (details, notes, point list with filters by status / responsible / due / overdue / search, add a point) -> Point page (edit the five fields, post updates, full Log) -> All points (same filters + only mine) -> Team (up to 10 e-mail users, owner adds/removes) -> Plan (Rs 499, about USD 6, Razorpay not switched on) -> Demo mailbox (shows the notices that would be e-mailed).

## 3. Data per Point of Action
Point of Action, Responsible (e-mail ID), Date (due), Status (Not started, In progress, On hold, Done, Dropped), What to do, Updates (text, optional status, who, when), Last update (time of the latest change), Log (who, what, when, for create, every field change, every update, status change). Overdue is worked out from the due date and status.

## 4. Rules built in
- E-mail IDs only. Sign-in code by e-mail (shown on screen in the demo). Notices by e-mail only. A mobile number is refused as an e-mail ID.
- A team is one organization of up to 10 users. The first person to sign in with a new e-mail ID starts a team and is its owner. Only the owner adds/removes people. The 11th is refused kindly.
- One team never sees another team's data (checked).
- Payments only via IT SERVICES BY RAJAT AGARWAL through Razorpay, nothing is charged, no payment script is loaded.
- Wording is third person, gentle and plain.

## 5. Stack and how it maps to free Cloudflare later
Plain Node server (no packages) and one JSON file today. Later: Pages for the screens, Workers for the `/api` routes, D1 for the tables (orgs, users, moms, points, updates, log). The e-mail code and notices would use the existing Resend/IT Services mailbox setup. Not started; waits for BOSS.

## 6. Run
`C:\ct\mom-aios\start-demo.cmd` opens http://127.0.0.1:4177/ . `stop-demo.cmd` stops it. Sample team: asha@sunrise-demo.example (owner), ravi@, meera@, kabir@ at the same address. Sample data resets by deleting `data\db.json`.