// MetalDrug Documentation

Frequently Asked Questions.

Learn how MetalDrug, Moleculogic, SEI, ExergyNet, virtual wet lab audits, verified molecular compute, regulatory deal rooms, compute credits, and blueprint licensing fit into one compute-to-regulatory platform.

60 / 60 shown
No matching FAQs. Try a broader term such as compute, FDA, SEI, credits, or licensing.
Understanding MetalDrug

Understanding MetalDrug

MetalDrug is a verified molecular evidence platform for early drug development. It helps teams design therapeutic blueprints, audit scientific logic, run molecular simulations, verify compute provenance, interpret results with SEI, and organize evidence for regulatory workflows. It is built around one practical chain: design, audit, compute, verify, interpret, and package.

MetalDrug uses AI, but it is not only an AI drug discovery tool. Most AI drug discovery platforms focus on finding or optimizing molecules. MetalDrug focuses on the complete evidence chain that connects therapeutic design, virtual wet lab audit, verified molecular compute, SEI interpretation, and regulatory packaging.

Early drug programs often fail because the evidence chain is fragmented. A team may have a molecule, a mechanism, a simulation, regulatory documents, and investor materials, but those pieces often do not connect. MetalDrug helps convert scattered scientific material into a structured, traceable, reviewable development workflow.

MetalDrug is built for biotech startups, academic spinouts, drug developers, computational chemists, medicinal chemists, regulatory consultants, CRO partners, investors evaluating therapeutic programs, and pharma teams reviewing external assets.

Traditional molecular software usually gives a prediction or simulation output. MetalDrug adds logic audit, compute provenance, and regulatory interpretation. The platform does not only ask what the molecule predicts computationally. It asks what was computed, can the execution be verified, what does it imply, and where does it belong in the regulatory package.

Moleculogic and SEI

Moleculogic and SEI

Moleculogic is the molecular reasoning and simulation layer inside MetalDrug. It helps users create, test, and refine therapeutic blueprints before committing to expensive wet lab work. It includes tools such as the Moleculogic Navigator, Functional Drug Complex Designer, Metal-Drug Complex Blueprint Builder, Virtual Wet Lab, and AskMO / SEI workspace.

SEI stands for Synthetic Evolving Intelligence. In MetalDrug, SEI is the reasoning layer that evaluates molecular logic, evidence gaps, contradictions, regulatory risk, and next-step recommendations. SEI does not replace scientists or regulatory experts. It organizes complex evidence and exposes weak assumptions before they become expensive failures.

Logic means the structured therapeutic reasoning behind a drug concept. It can include the disease environment, biological trigger, metal core, payload, release condition, target tissue, safety boundary, mechanism of action, and regulatory evidence path.

Logic = IP means the therapeutic blueprint itself can become valuable intellectual property. The invention may be the conditional architecture: when a disease environment exists, under specific biochemical triggers, a therapeutic complex activates, releases a payload, stays within a safety boundary, and serves a clinical objective.

No. If you upload your own molecule and use MetalDrug tools, you own your molecule. If MetalDrug or SEI materially creates or co-develops a new therapeutic blueprint, licensing, royalty, milestone, or equity terms may apply through a separate agreement.

MetalDrug Tools

MetalDrug Tools

The Functional Drug Complex Designer helps users build complex therapeutic systems by defining the scaffold, linker, targeting layer, trigger layer, logic gate, payload, therapeutic objective, delivery route, and disease target. It is useful when the therapy is a functional architecture rather than a simple single molecule.

The Metal-Drug Complex Blueprint Builder focuses on metal-based therapeutic design. It helps define metal core, coordination geometry, binding mode, trigger system, activation threshold, payload release mechanism, disease environment, and environmental conditions.

The Moleculogic Navigator is a visual logic canvas for building therapeutic blueprints. It lets users connect metals, triggers, functions, disease contexts, simulation parameters, risk flags, activation profiles, and SEI overlay metrics.

The Virtual Wet Lab is a pre-synthesis audit environment. It checks whether a proposed molecule, mechanism, pathway, toxicity profile, and synthesis plan are internally coherent before the user spends capital on wet lab work.

AskMO is the conversational and regulatory reasoning interface inside MetalDrug. Users can ask questions about compounds, mechanisms, evidence gaps, regulatory pathways, and package readiness. AskMO is connected to SEI so it is designed for structured analysis rather than casual AI chat.

Secure Compute and ExergyNet

Secure Compute and ExergyNet

MetalDrug Secure Compute lets users run molecular simulations and related computational jobs through a verified compute workflow. Supported categories can include ADMET profiling, toxicity prediction, full library screening, encrypted virtual screening, molecular dynamics, protein-ligand docking, pathway checks, logic audits, and regulatory package audits.

ExergyNet is the decentralized compute and verification layer connected to MetalDrug. A user launches a job, MetalDrug packages it, ExergyNet dispatches it to a compute node, the node performs the work, the node signs the result, ExergyNet verifies the receipt, ZK verification confirms input/output integrity, and the result returns to MetalDrug for SEI interpretation.

ExergyNet can use decentralized compute resources, including permissionless laptop or local nodes. The user does not need to manage the node. The platform handles dispatch, verification, and result return.

ZK verification helps prove compute integrity, not biological truth. It can help verify that the job was executed, the input hash matches the submitted job, the output hash matches the returned result, the compute receipt is valid, and the result was not silently modified after execution.

A compute receipt is a record of a verified compute event. It may include job ID, simulation type, input hash, output hash, node signature, proof hash, timestamp, model version, compute class, and settlement record.

Compute truth asks whether the job was executed as claimed, whether the result is linked to the submitted input, and whether the output was altered. Scientific truth asks whether the result matches real biology, whether the model is validated for the context, and whether experimental evidence supports the prediction.

Scientific Evidence and Validation

Scientific Evidence and Validation

No. MetalDrug simulations are evidence-generating and evidence-prioritizing tools. They can help identify risk, rank candidates, find contradictions, and plan experiments. They do not replace wet lab validation, animal studies, clinical trials, or FDA judgment.

Evidence grade tells the user how much weight a result should carry. Example levels include exploratory, screening-grade, decision-support, and submission-supporting. Submission-supporting evidence requires validation, documentation, and human review.

Yes. SEI can analyze blueprint gaps, compute outputs, and regulatory needs to recommend next studies such as cytotoxicity panels, metabolic stability assays, hERG risk assessment, CYP interaction screens, molecular dynamics follow-up, tumor selectivity assays, formulation stability tests, and NAM evidence plans.

A contradiction audit checks whether the proposed therapeutic logic contains internal conflicts. For example, a design may claim acidic activation while targeting a physiological pH environment, or a document may claim low toxicity while the toxicity flag indicates high hERG risk.

Entropy telemetry is a system-level way of measuring uncertainty, instability, or disorder in a blueprint or reasoning path. It helps identify where uncertainty enters the design and which parts of the blueprint need more evidence.

Regulatory Workflows

Regulatory Workflows

MetalDrug can help prepare, organize, audit, and validate regulatory materials. It can support Pre-IND evidence gap reports, Type B meeting packages, FDA question lists, CMC remediation packages, NAM summaries, nonclinical overview drafts, in-silico safety packages, eCTD technical validation, and regulatory deal room organization. Qualified human teams should review and approve all FDA-facing materials.

The Regulatory Deal Room is a controlled workspace where users can organize documents, collaborators, evidence, simulations, audit logs, and package status. It supports document drafting, role-based collaboration, checkout and commit workflows, review and release workflows, evidence attachment, AI-assisted review, eCTD export preparation, and audit history.

A verified compute result can be attached to a regulatory document. For example, an ADMET result can support a Nonclinical Overview, a molecular dynamics result can support a Risk-Based Credibility Assessment, a toxicity flag can generate an FDA meeting question, and a ZK receipt can become part of an evidence appendix.

Yes, under the right controls. A deal room can support Bring Your Own AI, allowing users to connect SEI, OpenAI, Claude, Gemini, Azure OpenAI, or local models. Each AI should only access documents that the user is permitted to access.

No. AI can assist with drafting, review, contradiction detection, summarization, and evidence mapping. Final approval must remain with authorized human users. The correct workflow is AI suggests, human reviews, human accepts or rejects, and the system logs the decision.

No. MetalDrug can help improve evidence organization, package readiness, technical validation, and regulatory strategy. It cannot guarantee FDA acceptance, approval, clearance, or clinical success.

IP Protection and Privacy

IP Protection and Privacy

MetalDrug’s IP model separates private molecular material from public proof records. Raw molecular structures stay private, while proofs, hashes, and verification records can be anchored externally or shared selectively.

They should not be published publicly by default. The safer model keeps raw molecular files in private storage while salted hashes and proof receipts provide verification without exposing the underlying molecule.

A salted hash is a cryptographic fingerprint of a file that includes a private salt. It allows the system to create a verification record without exposing the original molecule. In simple terms, the platform can prove the file existed and was not changed without showing the file to the public.

No software can fully prevent bad behavior by every person. MetalDrug can create stronger evidence of origin, lineage, timestamp, authorship, and derivative relationships, which can support IP records, patent strategy, licensing discussions, partner diligence, dispute resolution, and regulatory traceability.

Merkle-linked blueprint lineage means each blueprint version can carry a cryptographic relationship to its parent version. This allows the platform to show how a genesis blueprint, modified blueprint, derivative blueprint, and clinical candidate relate to each other.

Payments, Credits, and Access

Payments, Credits, and Access

MetalDrug can support platform subscriptions, compute credits, per-report purchases, regulatory package fees, deal room workspace fees, enterprise contracts, and blueprint licensing. The simple version is: subscribe for tools, buy credits for compute, pay for premium evidence packages, and use licensing only when MetalDrug contributes therapeutic logic.

Compute credits are prepaid units used to run simulations and audits. They can cover ADMET profiles, toxicity prediction, molecular dynamics, library screening, blueprint audits, SEI regulatory reviews, and ZK receipt generation.

Token pricing is useful for internal accounting, but drug development users usually want outcome-based pricing. Instead of asking users to think in tokens, MetalDrug can package work as a Blueprint Audit, ADMET Interpretation, FDA Questions Report, Evidence Gap Report, eCTD Validation, or IND Recovery Sprint.

An IND Recovery Sprint is a focused remediation workflow for teams that have received an FDA rejection, denial, hold, or deficiency response. It can include deficiency mapping, CMC remediation, pharmacology/toxicology evidence planning, in-silico safety support, Type B meeting package preparation, FDA question strategy, eCTD/ESG technical validation, and investor-ready scientific dossiers.

An IND Release Fee is a milestone payment for unlocking a complete, high-value regulatory package or evidence bundle. It may apply when MetalDrug has helped compile a CMC package, nonclinical package, SEI logic foundation appendix, manufacturing SOPs, simulation reports, eCTD files, or supporting datasets.

Blueprint Licensing

Blueprint Licensing

MetalDrug should receive a royalty only when there is a separate agreement showing that MetalDrug generated, co-developed, or materially improved the therapeutic logic being commercialized.

If you upload your own molecule, run standard tools, and do not ask MetalDrug to co-invent the therapeutic blueprint, the normal model should be that you pay for software, compute, or reports, and you keep your molecule.

A Licensing Transition Event occurs when a blueprint moves from digital design into physical development, synthesis, regulatory submission, or clinical translation under a commercial agreement. At that point, the parties may define ownership, license scope, royalty, milestones, territory, field of use, derivative rights, data handover, and regulatory package access.

In a joint venture model, MetalDrug may contribute therapeutic logic, computational evidence, regulatory package assets, or blueprint lineage, while a partner contributes capital, wet lab work, clinical operations, or commercial infrastructure. The result may be a program-specific NewCo.

Case Studies and Proof

Case Studies and Proof

Yes. MetalDrug | Moleculogic has been used in a QRX-3 IND remediation context involving CMC generation, FDA re-engagement, strategic positioning, and in-silico pharmacology/toxicology support.

It means a program had a regulatory setback, then required structured remediation. A recovery workflow may involve identifying FDA deficiencies, rewriting meeting materials, reframing the evidence path, building missing CMC logic, generating in-silico safety support, creating an FDA interaction roadmap, and validating eCTD/ESG submission structure.

No. One case study proves applied use, not universal validation. The correct conclusion is that MetalDrug has demonstrated applied translational utility in a real program context, while more programs, external review, benchmark studies, and wet lab confirmations increase validation maturity.

Safety, Limits, and Compliance

Safety, Limits, and Compliance

No. MetalDrug provides scientific, computational, and regulatory intelligence tools. It does not provide medical advice, diagnose patients, prescribe treatment, or replace licensed professionals.

MetalDrug can help organize regulatory logic and package evidence, but sponsors should work with qualified regulatory counsel, regulatory consultants, and scientific experts before submitting FDA-facing materials.

MetalDrug should not make clinical claims unless those claims are supported by appropriate evidence. The platform should distinguish hypothesis, simulation result, experimental result, clinical evidence, and regulatory conclusion.

No. MetalDrug can identify safety signals, evidence gaps, toxicology concerns, and simulation-based risks. Safety must be supported by appropriate experimental, nonclinical, and clinical evidence.

No. MetalDrug can help decide what should be tested, organize the evidence, run computational analysis, and create regulatory-ready summaries. Physical assays, GLP studies, and clinical work still require qualified labs and clinical partners.

MetalDrug is not a direct replacement for all of those systems. It is a connecting layer for design logic, virtual wet lab audit, verified compute, SEI interpretation, regulatory packaging, and deal room collaboration.

How to Start

How to Start

The best first use depends on the user. A researcher should start with a blueprint audit. A startup should start with an evidence gap report. A company with a molecule should start with secure compute and SEI interpretation. A team facing FDA issues should start with an IND Recovery Sprint. A partner evaluating an asset should start with a diligence room and verified evidence review.

Useful starting inputs include compound name, SMILES/SDF/PDB file, target protein, mechanism of action, disease indication, payload or metal core, expected trigger condition, available assay data, regulatory history, FDA correspondence, current CMC documents, and current nonclinical evidence.

You can still use MetalDrug to build a therapeutic blueprint. The platform can help define disease target, mechanism, trigger logic, metal core, payload class, delivery route, safety boundary, and evidence plan.

You can upload or define the molecule, then run a virtual wet lab audit, ADMET profile, toxicity prediction, molecular dynamics, library comparison, or regulatory evidence-gap review. The system can then recommend what evidence should be generated next.

MetalDrug helps drug teams move from therapeutic idea to evidence-backed regulatory package faster, with better traceability, stronger logic control, and verified compute provenance. The platform does not remove scientific risk. It makes the risk visible, structured, testable, and easier to act on.

Important boundary

MetalDrug provides scientific, computational, and regulatory intelligence infrastructure. It does not replace qualified scientific, regulatory, legal, clinical, or medical professionals. Simulations and ZK receipts can support evidence workflows, but scientific validity and regulatory sufficiency depend on context, validation, and human review.