What is Numa?
Numa is the record of the office: one place where a constituent's case, the official's positions, the office calendar, and every reply that went out live together, searchable, with an audit trail. It's organized into nine tabs — Home, Casework, Constituents, Legislative, Comms, District, Analytics, Operations, and Kennedy, the office AI — with Admin under the avatar menu. Each has a guide in the rail to the left.
Every office has a structured scope — municipality, county, or legislative district — that filters everything: constituent matching, casework intake, district intelligence. A council office only ever surfaces its own ward, even where the underlying data covers more. From anywhere, ⌘K opens the command palette — cases, constituents, involved parties, and tabs, one search. Staff sign in with a password, a passkey, or Microsoft, and an account can work across more than one office — you pick where you're working today.
THE VOICE OF THE RECORD
Numa's verbs are verbs of record: open, assign, promote, reject, close, track, stand. If an action matters, it's on the case; if it's on the case, it survives staff turnover, FOIA requests, and the next transition.
Getting started — the setup week
NJR runs onboarding; your staff's part is about a week of short sessions:
By the end of the week the queue is real: open cases with owners and SLA clocks, not an empty database waiting for good intentions.
Campaign vs. office
Romulus runs the campaign; Numa runs the office. They share a family — the same editorial system, the same team behind them — and nothing else. No foreign keys cross the namespaces; the separation is enforced in CI, not by policy memo.
The compliance regimes differ on purpose: campaign data answers to election law, office data answers to FOIA and public-records statutes. Campaign history appears inside a case only when the constituent is voter-linked and a role explicitly grants the permission — and that view is itself audit-logged.
Security & privacy
Access is role-based down to individual permissions — an intern can work the queue without seeing campaign history or exports. Every sensitive action lands in the audit log with actor, action, and outcome, searchable from Admin.
Public surfaces expose only what the office publishes: status links carry no sensitive notes, the portal shows a constituent only their own cases, and Kennedy drafts but never sends. Everything exports to CSV at any time — the record is the office's, not ours.
Questions the guides don't answer go to info@northjerseyresearch.com — the people who built the module you're asking about.