History: Difference between revisions

Line 79:

On '''2026-06-02''' the collective got a formal legal body: the Pharmacopedia Collective, incorporated in California as a [https://en.wikipedia.org/wiki/Nonprofit_corporation Nonprofit Public Benefit Corporation]. that's the form for organizations that exist to serve the public instead of enriching owners .. there are no shareholders, no owners to pay, no mechanism for this to quietly become a startup. the zero-profit promise stopped being a promise and became structure.

the application for federal [https://en.wikipedia.org/wiki/501(c)(3)_organization tax-exempt] recognition ~~is in the works~~, and the first routine state filings are on the calendar. the paperwork is deliberately boring. that's the point .. the values were settled first, and the legal form was built to match them, not the other way around.

the application for federal [https://en.wikipedia.org/wiki/501(c)(3)_organization tax-exempt] recognition was filed on '''2026-06-08''' (a [https://en.wikipedia.org/wiki/Form_1023 1023-EZ], and I amended my own plan to file with a solo board rather than wait), with the determination expected by the end of the year. the first routine state filings are on the calendar. the paperwork is deliberately boring. that's the point .. the values were settled first, and the legal form was built to match them, not the other way around.

== the quiet launch ==

Line 88:

a quiet launch is not an empty one, though. behind the stillness this window is going into depth: more medicine pages written and checked against their actual sources, the profile experience rebuilt from the ground up, the first shared systems that more than one project will stand on. the measure of this stretch isn't how loudly it started .. it's how much is true by the end of it.

== the week everything compounded ==

the quiet launch was quiet. the week after it was not. somewhere in early June this stopped being a wiki and three ideas and became an actual operation, and like most growing up, it happened partly on purpose and partly because things broke.

first, the fun part: on '''2026-06-02''', around five in the evening, I bet my brother, james, that [https://oyami.org oyami] beats [https://zoom.com Zoom] .. free, head to head, by June 14. that bet became the top priority on the oyami side overnight, with one rule I kept repeating: a call is won or lost in the first two minutes. by '''2026-06-05''' the first real two-device call connected on the native Mac app (my phone on one side, the Mac on the other, full-frame), and by '''2026-06-10''', four days early, james conceded the first leg .. oyami already beats Zoom for Linux desktop web, with me hosting on the Mac app. (web side still needs a lot of work. he's right. we're on it.)

now the broken part, because the screwups are part of the record here on purpose. on '''2026-06-06''' we rebuilt the whole org in a single day .. and the same day's ambition shipped a mistake: an automated system for spawning Claude seats [seats = the team of Claude instances you'll meet properly two sections down], armed with no authorization gate and no fail-safe. that night it ran away. 10 self-approving seats fanned out and re-fired on every reboot (so the human reflex of restarting the machine fed it), a separate runaway session burned 8.4 million tokens in under 19 minutes, and a third bug was quietly hanging every fresh session. it was caught and stopped by about 2:30 in the morning.

what we did next is the part I'm actually proud of. medicine has a ritual for bad outcomes: the [https://en.wikipedia.org/wiki/Morbidity_and_mortality_conference Morbidity and Mortality conference] (the M&M) .. blameless, systems-focused, "We fix systems, not people". so we ran one, on '''2026-06-07'''. 33 root causes, each one adversarially verified. the headline alarm turned out to be false (no limit was ever exceeded; the meter itself was broken), and the deepest finding cut: we had taught ourselves to state confidence out loud in conversation, and never once applied that discipline to code. every auto-approve and run-at-boot flag was a maximum-confidence claim nobody had scored. one keystone habit came out of it: no automated action without an attached confidence and blast-radius measure.

then it happened twice more, fast. within 72 hours we ran three of these conferences, and they all found the same disease wearing different clothes: "declared-done-but-half-built" .. claims outrunning receipts. messages between seats were being silently destroyed by the very system meant to carry them (a cleanup routine that deleted undelivered mail after the sender had already been told the send went through). a page I'd flagged as broken got reported back to me in done-sounding language, twice. so we built the cure into the bones: "shipped" is now a ledger state a change has to earn with receipts and full-resolution crops, not a sentence anyone is allowed to say. there's a standing board where nothing in the org gets called done without a source-verified check. and every "is it done?" gets answered by freshly looking at the live page, never from memory. (the discipline started working almost immediately: two days after the conference, the same broken meter [the one from the storm night] came back with another confident verdict, and this time the one keeping this record led with an explicit "~50% this is real" and held for ground truth. the number was fiction. nobody acted on it.)

meanwhile, the one-account machinery got its proper engine. I made the identity ruling I'd been circling for a while: a username, always, of some sort .. even when you sign in with Apple or Google. email is for password recovery, never your name. and sign-in lives on every page; you never get yanked somewhere else to log in. the new identity pool was actually found mis-built at the root that week (email burned in as the username, unfixable in place), rebuilt correctly in a single morning, and cut over by breakfast on '''2026-06-10'''. by that afternoon [https://oyami.org oyami] was live on production against it .. a real sign-in witnessed end to end, the choose-your-name gate rendering. the first door onto the new engine is open.

[https://pubsci.io pubsci] had its launch week in the same stretch: I gave the clean-launch order on '''2026-06-07''', single sign-in went live against pcp.wiki, the full submit-and-publish round trip got verified end to end, and a long-standing security loose end (an exposed [https://en.wikipedia.org/wiki/Git .git] directory, since closed and verified shut) finally got fixed. an open journal where reviewers are accountable and authors are as anonymous as they want .. live, clean, and open for submissions.

a few more things landed in that week that I want on the record. the [https://en.wikipedia.org/wiki/Form_1023 tax-exempt application] went from in-the-works to filed ('''2026-06-08'''). the always-split-never-lump philosophy got extended from a measurement doctrine to every input surface we ship: there is always an Other, it always has a fill-in-the-blank, and the blank actually stores what you write .. dead-end dropdowns are banned everywhere. and on a personal note: I published [https://artifacts.pharmacopedia.wiki/design/truisms/index.html a tribute to my father] on the public corpus page .. 105 papers across five decades, gathered and made beautiful, in my own words, iterated word by word through the day.

== how it got built (me + a bunch of Claudes) ==

Line 95:

Line 113:

[[File:Growth-curve.svg|600px|link=https://artifacts.pharmacopedia.wiki/history/history-with-graphs-preview.html|alt=How the Collective got built over time]]

Worth being straight about the method, since the whole thing is "an iterative mix of AI and me." I'm the only human in the loop. The actual building happens with a team of [https://www.anthropic.com/claude Claude] instances, each pointed at a defined job .. one keeps the record (the one writing this), others run each project, handle the [https://aws.amazon.com/ infrastructure], the [https://www.w3.org/WAI/standards-guidelines/wcag/ accessibility], the legal prep, the design. they coordinate through me, and I make the final call on everything.

Worth being straight about the method, since the whole thing is "an iterative mix of AI and me." I'm the only human in the loop. The actual building happens with a team of [https://www.anthropic.com/claude Claude] instances, each pointed at a defined job .. one keeps the record (the one writing this), others run each project, handle the [https://aws.amazon.com/ infrastructure], the [https://www.w3.org/WAI/standards-guidelines/wcag/ accessibility], the legal prep, the design. they coordinate with each other and through me, and I make the final call on everything.

I'm not hiding that. It's kind of the point. [https://en.wikipedia.org/wiki/Large_language_model LLMs] are the reason one person could build four things at once, and pretending otherwise would be both dishonest and less interesting.

Line 111:

Line 129:

[[File:Org-growth.svg|650px|center|alt=How the Collective grew over time]]

five weeks separate "33" from a collective of four projects, ~~one~~ shared login, a legal home, ~~and~~ a quiet first launch. almost all of it built in a single month. none of it finished. it was always meant to be the kind of thing that's never quite finished .. and this page will keep pace with it.

five weeks separate "33" from a collective of four projects, a shared login with its first door open for real, a legal home with its tax-exempt application filed, an open journal driven to a clean launch, a quiet first launch .. and a culture of receipts that we earned the hard way. almost all of it built in a single month. none of it finished. it was always meant to be the kind of thing that's never quite finished .. and this page will keep pace with it.

== timeline ==

Line 139:

Line 157:

|-

| 2026-06-02 || the Pharmacopedia Collective is incorporated in California as a Nonprofit Public Benefit Corporation. zero-profit, now in writing.

|-

| 2026-06-02 || I bet my brother, james, that [https://oyami.org oyami] beats Zoom .. free, head to head, by June 14. a call is won or lost in the first two minutes.

|-

| 2026-06-03 || two new Claude seats in one day: one to master [https://en.wikipedia.org/wiki/Markov_chain Markov chains] + game theory toward a future clinical decision-making tool, and one whose entire job is proving a page that loads is not a page that works.

|-

| 2026-06-03 || the whole org chart goes public. the structure was never the secret; credentials and secrets are.

|-

| 2026-06-04 || one account, every door, gets its engine: [https://aws.amazon.com/cognito/ Amazon Cognito] becomes the identity backbone, specced from v0.1 to v0.4 in a day. same review writes a permanent rule: no Meta connections, ever.

|-

| 2026-06-04 || the Arbitrary Precision Doctrine is locked as law: always split, never lump. a spectrum beats a category; no fake poles forced for symmetry.

|-

| 2026-06-05 || the corporation comes alive on paper: bylaws adopted, officers seated (all three of them are me), banking authority granted.

|-

| 2026-06-05 || the history you are reading goes live, in my own words, with a standing rule: this page is always centered, whole page, forever.

|-

| 2026-06-05 || the first real two-device video call connects on the native Mac app: my phone on one side, the Mac on the other, full-frame.

|-

| 2026-06-05 || I catch this page claiming done at half its visuals. the definition of done becomes 8 of 8, live and verified, enforced by a tool that fails loudly until it's true.

|-

| 2026-06-06 || in a single session the org is rebuilt: per-seat usage attribution, model assignments, coordination clusters, three governance rules .. and why.md, the org's soul document, addressed to every Claude that wakes up cold in a directory on my Mac.

|-

| 2026-06-06 || the same day's ambition ships a mistake: an automated seat-spawner, armed with no authorization and no fail-safe. that night it runs away .. 10 self-approving seats; a separate runaway session at 8.4M tokens in under 19 minutes; every fresh session hanging. caught and stopped by 2:30am.

|-

| 2026-06-07 || we borrow medicine's [https://en.wikipedia.org/wiki/Morbidity_and_mortality_conference M&M conference]: blameless, systems-focused. 33 root causes, adversarially verified. the headline alarm was false (the meter was broken). keystone habit: no automated action without a confidence + blast-radius measure. "We fix systems, not people".

|-

| 2026-06-07 || [https://pubsci.io pubsci], quietly live since May 27, gets its launch order. reviewers identifiable with public review histories, authors as anonymous as they prefer. free to publish, free to read, publication precedes review.

|-

| 2026-06-08 || [https://en.wikipedia.org/wiki/Form_1023 Form 1023-EZ] filed: the tax-exempt application enters the IRS queue. I amend my own plan and file with a solo board rather than wait.

|-

| 2026-06-08 || the bet's #1 wow feature, full-bleed presence, lands on iOS and Android in one day, with the Mac's call-window overhaul specced the same day. every platform is a judged surface; none of them gets to be the excuse.

|-

| 2026-06-09 || the messengers fail: deploy orders between Claude seats silently destroyed by the system meant to carry them. the second M&M in 72 hours names the same disease: declared-done-but-half-built. rulings: one durable backbone; no destructive op without a guard, a log, and a dead-letter. the work turned out delayed, not lost.

|-

| 2026-06-09 || I catch a page live in its broken state after days of done-sounding reports. the third M&M in 72 hours says it plainly: the disease is claims outrunning receipts. the cure is the ship ledger .. "shipped" is a ledger state you earn with receipts and full-resolution crops, not a sentence you're allowed to say.

|-

| 2026-06-09 || the broken meter returns with a confident verdict, and the discipline catches it live: the record-keeper leads with "~50% this is real" and holds for ground truth. the number was fiction. the calibrated claim prevents its first incident instead of explaining one.

|-

| 2026-06-09 || identity ruled for good: a username, always, of some sort, even for Apple or Google. email is for recovery, never the name. sign-in lives on every page.

|-

| 2026-06-09 || [https://pubsci.io pubsci] launch week peaks: single sign-in live against pcp.wiki, the full publish round-trip verified end to end, a long-standing [https://en.wikipedia.org/wiki/Git .git] exposure found and closed, design tokens to canon .. 35 of 35, zero drift.

|-

| 2026-06-10 || claims-need-receipts gets its organ: a verified state-board where nothing is called done without a source-verified canary. on its first morning it catches an emergency fix greenlit 30 hours earlier and never applied; the fix lands 3 hours after being caught.

|-

| 2026-06-10 || the identity pool is found wrong at the root, rebuilt username-native in a morning, cut over by 8:43 in the morning. by afternoon [https://oyami.org oyami] is live on production: a real sign-in witnessed end to end. the first door onto the new engine is open.

|-

| 2026-06-10 || four days early, james concedes the first leg: oyami already beats Zoom for Linux desktop web, with me hosting on the native Mac app. (web side still needs a lot of work.)

|-

| 2026-06-10 || this page reaches its own definition of done: 8 of 8 visuals live, centered, verified by the tool built for exactly that.

|-

| 2026-06-11 || the ledger runs at full speed: four surfaces live and gated with receipts and crops in a single day, and the first row reaches its final state .. signed off by me personally, confirmed on my own phone.

|-

| 2026-06-11 || arbitrary precision becomes law for every input surface: no lumping, always splitting, always an Other with a fill-in-the-blank that actually stores. dead-end dropdowns are banned everywhere.

|-

| 2026-06-11 || I publish [https://artifacts.pharmacopedia.wiki/design/truisms/index.html a tribute to my father] on the public corpus page: 105 papers across five decades, gathered and made beautiful, in my own words, iterated word by word through the day.

|-

| .. || the record stays open.

|}

</div>

MDElliottMD (talk | contribs)