Task & standardisation platform for FETS test centres (Cochin · Calicut · Centre #3 soon). Single-file web app, comic-doodle design, Supabase backend.
| File | What it is |
|---|---|
actionables.html |
The entire app. Open locally or host anywhere (e.g. Hostinger). |
setup_fets_actionables.sql |
One-time database setup — paste into Supabase SQL Editor and Run. |
patch_fets_os.sql |
The FETS OS tables: Centre Rollout, Launch Playbook, Compliance Calendar — run once (safe to re-run). |
patch_delete_policy.sql |
Only if your DB was created with an older setup script. |
reset_fresh_start.sql |
⚠ Wipes ALL data and re-seeds Midhun + the three centres (Mangalore launching). |
add_team_members.sql |
Adds named staff records ready to link to their Supabase Auth logins. |
patch_lead_delete.sql |
Lets an actionable's lead delete it too (only needed after the auth switch). |
deploy_act.sh |
Deploys the app to fets.live/act on the VPS (see script header). |
PROJECT_CONTEXT.md |
Full project memory. Read this first — new developers AND Claude sessions. |
- Supabase project → SQL Editor → run
setup_fets_actionables.sql(once). - SQL Editor → run
patch_fets_os.sql(once) — enables the Centre Rollout board, Launch Playbook and Compliance Calendar. - Open
actionables.html(or upload to your host) — dashboard lights up with ACT-01 & ACT-02. - Optional: Chat Alerts page → paste a Google Chat incoming-webhook URL for team notifications.
Clone this repo, open a Claude (Cowork) session with the repo folder connected, and say:
"Read PROJECT_CONTEXT.md — let's continue the FETS Actionables project."
actionables.html embeds the Supabase anon key,
and the database currently has open policies (see Security section in PROJECT_CONTEXT.md).