History: Difference between revisions

{{DISPLAYTITLE:Pharmacopedia: A History}}

== What the Collective is ==

Today the Pharmacopedia Collective is four projects under one roof, each independent in its day to day work but joined by a single sign-in and a shared commitment to stay nonprofit forever:

* '''Pharmacopedia''' ([https://pharmacopedia.wiki pharmacopedia.wiki]), a medicine reference wiki where prescribers and the people who take medicines build consensus information together.

* '''Oyami''' (oyami.org), a platform for planned, periodic live video conversations run on gentle, listening-first rules. Its mission is helping people stay connected with one another.

* '''Trykl''' (trykl.org), a peer to peer support platform where giving moves directly between people, with the Collective never holding the money.

* '''PubSci''' (pubsci.io), an open academic journal that flips the usual identity model of peer review: reviewers are accountable and identifiable by a lasting handle, while authors may publish as anonymously as they wish.

A single account works across all four. One person, Mark Elliott, MD, owns and operates the Collective, funds it himself, and is the only human in the loop. The building is done by Mark working alongside a team of Claude AI instances, each given a defined role. That collaboration has been part of the project since the first day and is acknowledged openly throughout.

== Before the Collective: the 2020 seed ==

The oldest piece of the Collective is older than the wiki that started it, by more than five years.

On '''October 24, 2020''', Mark registered two domain names, pubsci.io and publicscience.io, through Network Solutions. They carry ten year terms that run to 2030. They sat dormant for half a decade: an idea for open science, bought and held, waiting for the rest of the Collective to grow up around it. When PubSci finally launched in 2026, it launched onto a name its founder had been holding since 2020.

Mark has said he regrets choosing Network Solutions as the registrar, a small and human footnote that has stayed true ever since. The domains will move eventually. The point of the story is the patience: the open science idea was not invented alongside the others. It was the seed that had been in the ground the longest.

The Collective grew out of a single wiki, and its very first moments are on the record. In '''May 2026''', the first messages Mark ever sent the project's AI collaborator were a test: the number 33, sent twice, to see if anyone was listening. "wait are you working?" Satisfied that someone was, he got to the point: "I'm building a wiki.js to become pharmacopedia."

The site already existed, running on the Wiki.js platform on a single rented server, and the name Pharmacopedia was Mark's from the start. But Wiki.js turned out to be a dead end: its stable version was frozen in maintenance-only mode, and its successor had been stuck in beta for years. So, the same night the work began, the project moved to MediaWiki, the software that runs Wikipedia, chosen above all for longevity. In Mark's words: "Can't imagine Wikipedia stopping dev, and we want to be around forever." Content is licensed CC BY-SA 4.0; the custom software is GNU GPL v3. Both open, in keeping with the values.

A small note on how this history corrects itself. For a time the project's own records treated that sustained session as the beginning. The record-keeper later traced an earlier first contact, several days before, and Mark confirmed it. The founding date on this page is the corrected one. It is a fitting first entry for a history that promises to be honest: even the start date was checked against the source and fixed.

: "a place for the people who recommend and/or use meds of the mind to collaborate and create consensus-driven information."

Three things were true from the beginning and remain true:

The founding domain was psychiatric medicine, "meds of the mind," a field where the words themselves carry stigma. That origin is why the Collective is careful with language to this day. The scope widened later to plant medicines and medicines of every kind, not on any single date but by a completeness argument Mark put simply: "to do it right, we'd have to include all different kinds of medicines."

For the first eight days the work ran fast and without a safety net: schema and features were built directly, without version control, before the project had stabilized enough to be worth tracking. Mark's own verdict on that first version was characteristically blunt: "idk. bad."

It was not bad. The honest record is that a serious system was already taking shape in those first days: votable elements, effects, interactions, votes, reports, and the beginnings of the personal profile and life-story features. It was simply built faster than it was documented. The first version placed under version control, on '''May 17, 2026''', already carried most of that system, after roughly eight days of un-versioned building.

The early days also produced the project's first hard-won operational lesson. A permissions mistake on the wiki's main configuration file locked the whole site out. Mark's response became a standing rule that has propagated across every part of the Collective since: "yeah okay don't do that ever again, yeah?" The discipline that grew out of that one outage, careful ownership and permissions after every change, is now built into the Collective's deployment tools.

<!-- HELD: two founding vignettes ("what's a tarball?" exchange + Claude's first-day "not bad for a.." reaction) pending verbatim recovery from the pre-AWS Hostinger box via servops. Do NOT publish unverified; insert verbatim once confirmed. -->

== The Collective is born ==

On '''May 23, 2026''', the single wiki became a collective. Mark had been carrying four separate ideas, as he put it, "percolating in my mind for a very long time": the medicine wiki, an open science journal, a way to connect people in real conversation, and a way to move support directly between people. On that day he decided to build them together, under a shared structure and a single sign-in.

The Collective is built by one person working alongside a team of Claude AI instances, each given a single clear role. That is unusual enough to state plainly, which is in keeping with building in the open.

The roles divide into shared functions that serve the whole Collective and teams that build each project. The shared functions include a record-keeper (which maintains this history), infrastructure and security, an accessibility specialist, design, and legal preparation. Each of the four projects has its own coordinator and its own builders. Everything is coordinated through Mark, who is the only human and the final word on every decision.

As of mid 2026 there are around forty-five such roles. Each is a distinct instance with its own written brief and its own lane. None of them acts as a person, signs anything, or stands in for Mark. They are tools with defined jobs; the work and the decisions remain his.

The founding project and the identity backbone for the others. A reference for psychiatric and, increasingly, all kinds of medicines, built on consensus between prescribers and the people who take them. It carries careful sourcing standards, a structured assessment system, and a privacy-first design.

A platform for planned, periodic live video conversations, designed around listening rather than debate. Its goal is simple and large: helping people stay connected with one another. Oyami is built as native mobile applications for the most reliable live experience.

A peer to peer support platform where money moves directly between people. A guardrail sits at its center: the Collective never takes custody of funds, never pools or holds them. Support flows straight from one person to another.

== One login, four projects ==

The projects are independent, but they are not strangers. Pharmacopedia is the identity backbone: a single account, created once, works across all four. Sign in anywhere and you are recognized everywhere, without a second password or a second profile. The shared sign-in came first; deeper connections between the projects are being built carefully and in order, with the founding rule that solid foundations come before new features.

The Collective is defined as much by what it refuses to do as by what it builds:

* '''Nonprofit forever.''' No revenue model, no paid tiers, no fees, no advertising, ever. Mark funds the work himself, with the door open to voluntary support. This is written into the legal structure, not just the policy.

* '''Open by default.''' Open content licenses, open source software, and a history told in the open, including the mistakes.

* '''Built right, not fast.''' Foundations are settled before things are built on top of them.

== From one server to a cloud ==

Pharmacopedia began life on a single rented server. As the Collective grew to four projects, that single server was no longer the right shape. Over late May 2026 the infrastructure was rebuilt on Amazon Web Services, organized into separate, properly isolated accounts for each project, with security and audit controls befitting the sensitive information the Collective holds.

Pharmacopedia itself moved to the new cloud on '''May 28, 2026'''. As part of that move, direct shell access to the live site was closed by design: changes now flow through a controlled, audited deployment path rather than hands on the live server. The original server remains as a frozen standby for rollback only. The result is a Collective that runs on one consistent, secure foundation instead of a patchwork.

== The launch window ==

On '''May 31, 2026''', Pharmacopedia was cleared for its first launch. The posture is deliberately quiet: no announcement, no banner, no campaign. The site simply becomes fit for anyone who finds it, and the work continues. A launch like this does not have to be defended as an event. It exists when the work exists.

The days that followed put the first real pages of policy and identity in place: the project's first Terms of Use, its first adverse-event reporting page, a rebuilt profile experience, and the first piece of a shared timeline system that several projects will use. Alongside the function, Mark set a standard for how all of it should feel: every part of the Collective should be, in his words, beautiful. The work of meeting that standard is ongoing.

== How this history is kept ==

This page is maintained by the Collective's record-keeper, whose job is to keep an honest and detailed account of how the Collective came to be: every project, every major decision, every milestone, and every lesson, from the founding forward. The record-keeper is itself part of the story it tells.

== Timeline ==

| 2020-10-24 || Mark registers pubsci.io and publicscience.io. The oldest piece of the Collective, held dormant for more than five years.

| May 2026 || The project begins as a Wiki.js site on a rented server. The first messages are a test: "33", twice. The same night, it moves to MediaWiki, chosen for longevity. Sustained development begins days later.

| 2026-05-17 || The Pharmacopedia software is first placed under version control after roughly eight days of rapid early building.

| 2026-05-23 || The Pharmacopedia Collective is founded: four projects under one structure and one sign-in.

| 2026-05-25 || PubSci joins as the fourth project, onto a domain held since 2020.

| 2026-05-27 || PubSci's first public version goes live; the single sign-in works end to end.

| 2026-05-28 || Pharmacopedia moves to a new, more secure cloud foundation on AWS.

| 2026-05-31 || Pharmacopedia is cleared for a quiet first launch; the first Terms of Use and policy pages follow.

This history is a living document and will be extended as the Collective grows.