Research + intelligence systems · 03
Psychedelic Operations Intelligence
Live source-verified monitor · sweep overdue, reported on the build
Turn a fast-moving legal and scientific field into operational intelligence.
What I noticed
The psychedelic field moves across law, clinical research, state programs, professional education, organizations, funding, and public claims. Conventional news feeds preserve documents but not the relationships needed for decisions.
What I researched
Regulatory programs, legislation, scientific evidence, institutions, professional actors, operational signals, source provenance, update cadence, and the decisions different users need to make from the same field data.
What I built
A public dashboard over six verified official source endpoints, with a weekly sweep, a source-policy gate every candidate must clear before display, per-category sweep state, and a published collection-health block reporting how many days old the last successful sweep is. On the most recent sweep seven candidates passed the policy and forty-one were rejected as noise.
Who it serves
Researchers, regulated operators, policy teams, legal professionals, educators, and organizations that need current field intelligence with source traceability.
What it demonstrates
Cross-domain taxonomy, database and dashboard design, evidence provenance, monitoring logic, and decision-oriented synthesis.
Verified build record
What is actually running, and what it is not.
LiveLive · sweep overdue by more than two cycles, reported on the page
The problem. Psychedelic regulation moves through state programme portals and rulemaking pages that publish on no fixed schedule. Most trackers in the space blur an official rule change together with a press release or an advocacy claim.
What it does. Watches six verified official source endpoints — Oregon Health Authority psilocybin services, Colorado natural medicine, and four others — on a weekly cycle. Every candidate a query returns is put through a source policy before it is shown; on the most recent sweep, seven candidates passed and forty-one were rejected as noise. The page reports per-category sweep state, how many sources were healthy, degraded or failed, and how many days old the last successful sweep is.
Built on. Vercel serverless functions with an Upstash Redis store and an explicit source-policy module that every candidate must clear before display.
What it does not establish. Screened candidates are unreviewed. A record in the source registry means the endpoint is monitored, not that something new was published there. Not legal advice.
This record is generated from the same inventory as the complete build index: the production URL was checked at the last regeneration, and the status line above repeats what the build reports about itself rather than restating an intention.