A.L.E.X. · PIR®
Roadmap
Where A.L.E.X. has been, where it is now, and where it's going. A.L.E.X. is built by PIR®'s volunteer Tech Committee in the open, one careful step at a time.
Why we're building it
PIR®'s committees ran on WhatsApp threads and Zoom: requests got lost, and nobody could see what was in flight. Members and newcomers asked questions the website already answered. A.L.E.X. answers from PIR®'s own pages with sources, and turns requests into tickets a committee can see, claim and resolve.
Where we've been
| When | Milestone |
|---|---|
| Oct 3–4, 2026 | Planning with the Tech Committee. A unified, plain-language PIR® privacy policy. PIR®'s literature and brand assets get a home on GitHub. |
| Oct 5, 2026 | A.L.E.X. goes live in PIR®'s Discord. /ask answers with citations; five helpdesks (/techcom, /litcom, /github, /pr, /mod) tested end to end; public pages for every desk. |
| Oct 6, 2026 | The ask-alex chat panel (private answers, follow-ups, turn-into-a-ticket). A new look for every page. The web helpdesk with password-free email sign-in. Channel guides across the server, the 7th-tradition channel, and a Web3 preview. The always-on server for conversation mode is built. |
| Oct 7, 2026 | Every channel description rewritten with links and guidance. Server rules, safety & ethics and "Meet A.L.E.X." posts. This roadmap and the sustainability page. |
Now
- Conversation mode in #ask-alex: members type normally and A.L.E.X. answers in a thread, in that one channel only.
- Finishing onboarding: every group and medicine channel selectable when you join.
- Private groups by request: a gentle request desk reviewed by each group's trusted servants, never an automatic click.
Next
- A separate "ops" helper for server upkeep, so A.L.E.X. stays purely member-facing.
- Self-serve notification roles (announcement pings, meeting reminders, time zones).
- Living status boards for each helpdesk.
- Faster, sharper answers: a cached FAQ, links that jump straight to the quoted sentence, and Claude Haiku if the Tech Committee approves it.
Later (each needs a Tech Committee or Board decision first)
- A testnet Web3 desk with anonymous, non-transferable service badges: no money, no tokens for sale.
- A De Vine News submission desk for the newsletter.
- Telegram, if and when PIR® goes there, with the same safety rules.
- Verified roles (for example "service role holder") through Discord's Linked Roles.
Help shape it
Ideas and feedback: type /techcom in PIR®'s Discord, or use the web helpdesk. Every suggestion becomes a ticket the Tech Committee can see.