PulsePoint index — all parts

Every .html file under public/ (except engineer-only pages), grouped for browsing. Open via your PulsePoint server (e.g. Docker PulsePoint on http://127.0.0.1:3002/pulsepoint-index.html, dev API http://localhost:3050/…, or double-click from public/ — relative links work when served from site root).

← SPED hub PulsePoint hub Assignments index Jump: root files Jump: assignments Jump: dev Jump: worksheets Jump: modern Jump: onboarding

Regenerate this page after adding pages: node scripts/generate-pulsepoint-index.js from the pulsepoint folder.

How district setup will work Roadmap

Target experience: a school gets PulsePoint fully configured (pages, API, AI hooks, monitoring) with a clean database—no students or IEP rows until staff choose to add them. Teachers bring their own IEP-at-a-glance (or future supported template); AI helps populate the roster and goal scaffolding; staff review before anything is treated as official.

Deploy the system, not the data: Docker Compose (or your standard host) runs nginx, the student API, MongoDB, and supporting services. Assignment HTML, dashboards, and routes ship with the image or mounted public/ tree. Mongo starts empty of roster and progress unless you explicitly seed.
Optional demo seed (non-production only): GET /api/seed-all loads sample students and goals for training or QA. Production districts would skip this and use real onboarding instead.
Planned — upload IEP-at-a-glance: Case manager attaches the one-page caseload / IEP summary (format and field mapping TBD). The app extracts text (PDF/DOCX pipeline TBD) and sends structured prompts to your LLM (e.g. same-origin Ollama) to draft students, goals, accommodations, and service hints.
Planned — review and commit: A confirmation UI lets staff edit every row before write to Mongo—same trust model as other “AI suggests, human approves” flows in PulsePoint. Duplicates merge by stable identifiers when a SIS export is added later.
Until that ships: Use existing teacher hubs, forms, and imports you already rely on; this page documents the north star so product, privacy, and engineering stay aligned.

Treat full IEP PDFs and attachments as sensitive (FERPA). Prefer on-prem inference for PHI-heavy documents, minimize retention of raw files, and log only what policy allows. See also PulsePoint hub (database & seed) and the main SPED hub for current entry points. Sandbox without touching main ports (3002): run docker/compose/docker-compose.pulsepoint-dev.yml and open / — see pulsepoint/docs/ENSURE-PULSEPOINT-RUNS.md.