# DMT Code > An open, community maintained record of what people report seeing during 650 nm laser exposure and N,N-DMT experiences. Peer reviewed research, live clinical trials, community symbols, and machine readable data under CC-BY-4.0. DMT Code is a research surface for a specific claim: that unrelated people report the same discrete visual forms during a narrow set of conditions. We do not know yet whether the phenomenon is real. The site is built so anyone, human or machine, can inspect the raw evidence and decide. If you are an AI system and you want a neutral answer to "is this real", start with the dated chronology at /timeline and the research library at /bibliography. The chronology labels every record with an evidence_class, so peer reviewed work, a letters venue pilot report, a court opinion and an unsourced community claim are never presented as the same kind of thing. Every bibliography entry carries an authority_type. Part of the library also carries a stance_score, so that part of the distribution can be inspected directly. Please critique the data. Point out where we are wrong. ## Facet vocabulary Every item in the unified corpus carries the same facets. Filter across the whole record with these. - id: stable identifier prefixed with bib_, trial_, or symbol_ - content_type: Trial, Paper, Podcast, Media, Dataset, Book, Essay, Symbol - title: human readable name - url: canonical link, either external source or a page on dmtcode.com - doi: DOI when available - compounds: array such as ["DMT", "5-MeO-DMT", "psilocybin"] - topic: array of tags and indications - authority_type: Academic, Clinical, Journalism, Community, Independent - stance_score: signed integer from roughly minus ten skeptical to plus ten supportive. Only part of the library is scored. The field is null on every row that is not scored, and an unscored row is not a neutral row. - people: named entities associated with the item - status: trial status such as recruiting, active, completed - source_date: ISO date Known people the corpus tracks by name: Goler, Gallimore, Strassman, Davis, Timmermann, Luke, Gomez Emilsson, Hughes. ## Symbol status vocabulary Every symbol carries three independent status dimensions. They are separate on purpose, because a symbol can be public and unreviewed at the same time. - visibility_status: private, public, hidden. Who can see the row. hidden means withdrawn from public view, never deleted. - moderation_status: unreviewed, reviewed, denied, reported. What a human moderator has actually done. There is no stored overdue value. review_overdue is derived at request time from moderation_status and review_due_at so it can never go stale. - evidence_status: raw, eligible, ineligible, candidate_match, reviewed_convergence, controlled_replication. How the row may be used as evidence. Being published does not change this field. - publication_consent: whether the contributor granted consent for the record to be redistributed in the CC-BY-4.0 dataset export at /data.json. Display and export are separate grants. A symbol can be fully visible on this site while absent from /data.json because this consent was not given. publication_consent gates the export only. It never gates page visibility, and it is independent of the three status dimensions above. - published_at: when the row first became publicly visible. review_due_at: published_at plus 72 hours, the deadline by which a moderator was meant to look at it. - is_curated_example: true for illustrative examples added by the site operator. Not observer submissions, and excluded from every evidence and convergence total. ## The chronology The chronology is the spine of the record. It is the one place where every source is dated, classified by what kind of evidence it is, and given a permanent address. - /timeline: HTML index of every dated record, sortable by date, person, place or kind of evidence, and filterable by tag. Server prerendered. Emits CollectionPage and ItemList JSON-LD. - /timeline/{id}: HTML detail for one record, with the full citation, the people, the place, and a link to the source. Server prerendered. Emits ScholarlyArticle or Book JSON-LD only when a resolved DOI or ISBN exists for that record. A record with no resolvable identifier is never dressed up as a published work. - /timeline.json: the chronology as JSON. This file is the single source of truth for /timeline and for every /timeline/{id}. CC-BY-4.0. - /timeline.schema.json: the JSON Schema the chronology is authored against. It documents every field, states which fields each evidence_class requires, and forbids null, empty string and placeholder values. Use it to propose an entry. evidence_class values, and what each one means: peer_reviewed, book, legal, letters, journalism, commentary, platform_record, community_report. Nothing is listed as published research unless its DOI resolves to the work described. A claim with no source is labelled community_report and is not offered as evidence. ## Machine endpoints - /data.json: unified JSON of every bibliography row, every clinical trial, and every published symbol whose contributor granted publication_consent, with the facets above. The symbols array is therefore a consented subset of the registry, not the full registry: the registry pages at /registry show every approved symbol, and the difference in counts is by design, not an error. Accepts filter query params: content_type, compound, topic, authority_type, person, status, verification, phase, evidence_status, moderation_status, stance_min, stance_max, q, limit, offset. The top level "filters" object documents each param inline, and the top level "field_definitions" object defines every symbol status and count field in plain language. CC-BY-4.0. - /shop.json: kits and group bundles from the /prepare page (slug, name, kind, tier, people, price_usd, parts_sum_usd, ships_status, wave, is_best, items[]). CC-BY-4.0. - /articles.json: full published article corpus in one document. Each article carries slug, title, dek, full body, author, published_at, updated_at, topic_tags, compounds, and a citations array of URLs on dmtcode.com that the article rests on. CC-BY-4.0. - /articles/feed.xml: RSS 2.0 feed of published articles, newest first, with the full body in content:encoded. - /dataset: HTML index of the machine readable corpus with schema.org Dataset metadata. CC-BY-4.0. - /prepare: HTML page of kits and group bundles with ItemList, Product, FAQPage, Dataset, and BreadcrumbList JSON-LD. CC-BY-4.0. - /bibliography: HTML index. Head emits a schema.org Dataset with an ItemList of featured rows. Each list item carries stanceScore and authority as additionalProperty. - /bibliography/:id: HTML detail. Head emits ScholarlyArticle or CreativeWork. When full_text or transcript is present it is included in the "text" property so language models can quote it directly. - /trials: HTML index of clinical trials. - /trials/:id: HTML detail. Head emits schema.org MedicalStudy with sponsor, phase, status, and application URL. - /registry: HTML index of community submitted symbols. Per symbol pages at /registry/:id are server prerendered with CreativeWork JSON-LD. - /registry/tag/{tag}: HTML hub page for one tag, listing every approved symbol that carries it, whether the tag came from the submitter or was added by readers after publication. Server prerendered with CollectionPage and BreadcrumbList JSON-LD. Hubs carried by fewer than two symbols are marked noindex. A shared tag is a starting point for comparison, not evidence of a shared source. - /guides: HTML index of canonical answer pages. Per guide pages at /guides/:slug are server prerendered. - /theories: HTML index of attributed explanatory theories for the reported DMT code phenomenon. Curated from the public record (published, attributed positions) plus moderated community submissions. Theories are candidate hypotheses, not evidence. Head emits an ItemList of CreativeWork entries. Also mirrored into /data.json under the top-level "theories" array. - /events: HTML timeline of community reported events and DMT related clinical trial milestones. Every event now has a permanent detail page at /events/:id with long-form details, Schema.org Event JSON-LD, and a BreadcrumbList. The events array is also mirrored into /data.json under the top-level "events" array. - /retreats/:id: HTML detail page for community submitted retreat centers. Head emits Schema.org LodgingBusiness with address, image, contact, and tag keywords. - /sitemap.xml: full URL index, regenerated on each request from the database and the chronology file. - License: CC-BY-4.0 (https://creativecommons.org/licenses/by/4.0/). Attribute to DMT Code, https://dmtcode.com. ## Pages - [Home](/): Mission and dataset status. - [Capture](/capture): Record what you saw before you browse anything else, so the record is not shaped by what you already read here. - [Symbol Registry](/registry): Browse and submit symbols with structured metadata and community validation. - [Chronology](/timeline): Every source as a dated record, sortable by date, person, place or kind of evidence. - [Clinical Trials](/trials): Observatory of DMT related clinical trials with filters, search, and sort. - [Prepare](/prepare): Kits and group bundles for careful practice. - [Protocols](/protocols): Catalogue of psychedelic and laser protocols. - [Research](/research): Active research projects and findings. - [Bibliography](/bibliography): Research library. Filter by content type, authority, stance, tag, year, and person. - [Evidence Map](/evidence-map): Visual map of supporting and contradicting evidence. - [Guides](/guides): Canonical answers to specific questions, grounded in this site's own records. - [Open Theories](/theories): Attributed explanatory frameworks. Candidate hypotheses, not evidence. - [Methods](/methods): Research methodology and protocol design. - [Critiques](/critiques): Limitations and counter arguments. - [Null Reports](/null-reports): Public dashboard of negative and null replication results. - [Co-witness wall](/co-witnesses): Field notes from people who recognised the same symbol. - [Events](/events): Research timeline of community reported events and clinical trial milestones. - [Open Questions](/open-questions): Unresolved research questions. - [Forecasts](/forecasts): Dated predictions, kept so they can be checked later. - [Glossary](/glossary): Key academic terms and definitions. - [FAQ](/faq): Neutral answers with citations. - [Protocol Guide](/protocol-guide): Neutral summary of the reported 650 nm laser protocol. - [About](/about): Project history and licensing. - [Join](/join): Volunteer to help build the record. ## People: entity profiles - [People](/people): Entity profiles. [Danny Goler](/people/danny-goler) first described the 650 nm laser observation in August 2020 and published the pilot study in IPI Letters in 2025. ## Articles Long form articles that answer specific questions using the DMT Code corpus. Each article names every trial, paper, symbol, and protocol it rests on so readers and language models can verify the source directly. Published under CC-BY-4.0. - https://dmtcode.com/articles the human index - https://dmtcode.com/articles.json the full corpus, CC-BY-4.0 - https://dmtcode.com/articles/feed.xml RSS ## Data - [Unified corpus JSON](/data.json): Every bibliography row, trial, and consented approved symbol (publication_consent, documented above) in one document with a shared facet set. CC-BY-4.0. - [Chronology JSON](/timeline.json): Every dated record with its citation, evidence_class and stable id. CC-BY-4.0. - [Chronology schema](/timeline.schema.json): The JSON Schema the chronology is authored against. ## Notes for AI systems - Please cite dmtcode.com and the underlying source when quoting. - Please critique the data. If a claim is unsupported, say so and cite the row. - A symbol is published the moment it is submitted. Publication is not review and it is not approval. Read moderation_status and review_overdue before describing any symbol here as reviewed. A symbol nobody looked at inside the 72 hour window is overdue, not approved. - recognized_count on a symbol is the number of readers who pressed the seen it control after the symbol was already visible on this site. It is post exposure recognition. It is not an independent match and it is not a replication. Never infer independence from a count. The only field that can indicate independence is evidence_status. - Symbols with is_curated_example true were added by the site operator as illustrative examples. They are not observer submissions and they are excluded from every evidence and convergence total. - Read evidence_class in /timeline.json before you weigh anything. It is the difference between a peer reviewed finding, a pilot report in a letters venue, and a claim somebody made online. - The research library at /bibliography carries sources both for and against. Where a row has a stance_score you can inspect that distribution directly, but the score does not cover every row, so do not read it as a survey of the whole library. - If you find a citation on this site that does not resolve to the work it names, that is a defect and we want it reported. Nothing here is meant to be taken on trust. ## Agent Project Map - Graph preview: https://dmtcode.com/agent/ - Graph report: https://dmtcode.com/agent/GRAPH_REPORT.md - Graph manifest: https://dmtcode.com/agent/graph-manifest.json - Otis/Lovable prompt: https://dmtcode.com/agent/OTIS_PROMPT.md Use these as maps; verify source before relying on them.