Practitioners thinking together.
iFeed Community is the practitioner space alongside Academy — where QA professionals, RegOps leads, AI engineers, and founders working at the intersection of regulated life sciences and AI compare notes, share artefacts, and build the operational vocabulary the field is still acquiring. Profiles, discussions, cohort spaces, regulator-watch threads.
Four archetypes, one room.
Profiles · discussions · regulator-watch threadsThe community is built around four practitioner archetypes — QA leads, RegOps heads, AI engineers, founders — who each bring a different decision-set into the same room. The threads they trade are concrete: regulator-watch updates, validation artefacts, governance template critiques, AI-incident post-mortems. The shared output: an operational vocabulary the field is still acquiring.
What the community offers.
Member benefitsThe community is built around the cohorts and the methodology. Membership is free during the founding phase and gated by application — practitioners actually working in the regulated AI space, not vendors selling into them. The aim is signal, not scale.
Profile.
A profile that surfaces your thinking, your domain, your current focus. Directory of practitioners visible to other members.
Discussion threads.
Topical threads on regulator clarifications, deployment patterns, validation puzzles. Not Twitter — long-form, signed, archival.
Cohort spaces.
Active cohorts have private spaces for capstone work, peer review, and continuing alumni connection after the course completes.
Regulator watch.
Curated weekly digest of FDA / EMA / MHRA / HPRA / ICH publications relevant to AI in regulated life sciences. The signal layer.
Member profiles.
Preview · founding membersThe community starts with one profile — the founder's. Named members will be added as practitioners join and contribute their first archival thread. The community will not list placeholder seats or fictional rosters; what you see below is the real and current state.
Methodology architect. Pharmacy at the foundation (BPharm 2011–15, NIPER M.S. Pharm 2015–17), production-floor years across CRO, sponsor, and MedTech environments since 2017, with intentional intervals spent strengthening the foundation and synthesising the substrate into the iFeed methodology. Galway-based, Pune-rooted. Building the methodology and the community that surrounds it.
When the first practitioner-members join, their profiles will appear here — named, with their domain, current focus, and the threads they have contributed. The community is in the open and being built in public.
The threads we'll be reading.
Discussion previewThe threads below are illustrative of the kind of conversations the community is designed for. Members propose, engage, and archive. Threads turn into reference material the next time the same question comes up.
How are you classifying your AI inventory against Annex III?
PCCP architecture for adaptive AI: what passes 510(k) review?
Annex 22 readiness: what are we actually doing in our shops?
Reference test sets for non-deterministic AI: what's working?
ICH M11 structured-protocol fluency: how soon are sponsors mandating it?
All twelve current notes · notes/index.html →
Help shape the founding cohort.
Practitioners interested in joining the community as founding members can register interest below. Founding-member input shapes how the platform actually works — what threads matter, what tools help, what frequency is sustainable.