<aside> 📦

Workshop tool. Every feature/requirement for the IPN Member Portal — now a live database, one page per requirement, each with room for a detailed build spec. Source: the requirements doc (projects/IPN Member Portal/requirements.md) and the Member Experience Workshop output. The Priority property reflects the last Community Task Force session — open any requirement page to flesh out its spec.

</aside>

<aside> 🧭

Build Queue & Self-Assignment. Use the Proposed build sequence (v1.0) list below the database as the dependency-ordered backlog. When either Justin or Luke has spare capacity, claim the next unclaimed item: set Owner (Person) to your name, set Status to In progress, and fill in Start Date — so the other person sees it's taken and we don't double-dip. Mark Status Closed (or Done - Revisit if more iteration is expected) + Completed Date when finished. Use Sub-items to break a requirement into trackable subtasks — expand a parent row in the table to see its children. #13 Mobile-responsive UI is cross-cutting (a quality bar on every UI feature), so it doesn't get its own slot in the sequence.

</aside>

How to use this database

1. Pre-workshop (now): Justin reviews each requirement — sanity-check the proposed Value / Effort.
2. At the workshop: Walk requirement-by-requirement. Agree the final Member Value and tier; capture the call in Priority (with Decision Notes for detail).
3. Detailed specs: Open a requirement page and fill in the spec template in the page body — What we're building · Pain point · Requirement details · Acceptance criteria · Scoring & decision rationale · Suggestions / Edits (table at the bottom for proposed changes). Quick-fire open questions go in the Next Steps / Open Questions property on the requirement row.
4. Output: The filled-in Priority is the canonical scope; v1.0 effort gates the build timeline.
5. Sequencing: Use the Proposed build sequence (v1.0) list below plus the 2×2 quadrant at the bottom to debate ordering and self-assign work via Owner + Status.

How to fill in the "Priority" property

The Priority property captures the team's final tier per requirement — either confirming the proposed MVP Tier or overriding it. Use this convention so it stays scannable (put any detail in Decision Notes):

Once scope is set, go back to v1.0 rows and add Owner and Status (and Start Date when work begins).

Scoring legend

Member Value (1–5)

• 5 — Solves a workshop pain point cited verbatim in transcripts; foundational to multiple other features
• 4 — Strong workshop / survey signal; addresses a stated member need
• 3 — Useful but not headline; "polish" feature
• 2 — Nice-to-have; few members would notice if missing
• 1 — Speculative; no clear signal it's wanted

Build Effort

• S — <5 hrs of focused work
• M — 5–15 hrs
• L — 15+ hrs (or significant content production)
• Where effort varies by platform path, the page body notes which path is faster

MVP Tier

• v1.0 — Must ship for launch (PsychedelX 2026 target)
• v1.1 — Post-launch first quarter
• v2 — Later (Q4 or beyond)
• Out — Descope entirely; not in roadmap

Personas key

From the 2025 member survey breakdown. Abbreviations keep the database cells readable.

• R — Researcher
• G — Grad Student (45% of members)
• U — Undergrad Explorer (17%)