Your model
Language, ambiguity, planning, extraction, presentation, and the user experience you already built.
When an answer needs evidence, route it through Lois by API or MCP. She applies your source policy, builds Peel’s proprietary evidence trace, tests the claim, and returns structured evidence to the application you already use.
Lois is the Perslis model your application calls when an answer needs evidence, provenance, hypothesis testing, or trusted-source constraints. She does not replace the model you already use. She gives it a governed scientific reasoning layer.
Evidence-constrained scientific reasoning
Use the language model, agent framework, research product, or proprietary ML system you already trust. Route only the questions that need evidence through Lois.
Language, ambiguity, planning, extraction, presentation, and the user experience you already built.
Permitted-source retrieval, evidence standing, contradiction checks, visible unknowns, and a complete provenance chain.
NO SOURCE → NO CLAIMThe calling application sets the job and the source boundary. Lois returns the result, its standing, and the path that produced it.
trusted_sourceRestrict Lois to PubMed, FDA, named journals, internal data, or any allowlist you control.
evidenceReturn a claim only when it connects to evidence. Unsupported statements remain exposed.
hypothesisGenerate candidate explanations while separating support, contradiction, and the unknown for each one.
discoverySearch across the permitted corpus for relationships the original question did not anticipate.
verifySubmit an answer from another model and ask Lois: can this claim survive the evidence?
provenanceReturn the complete chain for citations, evidence graphs, audit trails, and Peel traces.
Send an objective, a mode, the material to evaluate, and a source policy. Receive evidence as structured state—not prose you are forced to trust.
{
"objective": "Can this claim survive the evidence?",
"mode": "verify",
"input": {
"claim": "BRCA1 loss predicts PARP inhibitor response"
},
"source_policy": {
"allow": ["PubMed", "FDA", "internal:trial-results"]
}
}{
"standing": "partially_supported",
"claims": [{ "status": "supported", "evidence": 7 }],
"contradictions": [{ "evidence": 1 }],
"unknowns": ["clinical context not specified"],
"provenance": ["PMID:…", "FDA:…", "internal:…"],
"peel_trace": { "inspectable": true, "retained": true }
}Each inspectable trace can carry provenance, source identity, claim standing, contradictions, unresolved unknowns, relationships, hypotheses, and the checks performed—so another system can render citations, graphs, audit trails, or a full research record.
Schema shown for product illustration. Confirm the supported production contract, source connectors, quotas, and deployment requirements during your API pilot.
Perslis Science becomes infrastructure other products consume—not another destination researchers must remember to visit.
Give a chat or copilot an evidence path for the moments when fluent generation is not enough.
Let an agent call Lois before it promotes a researched claim into a plan or report.
Add source-governed answers and complete traces inside the workspace scientists already use.
Combine approved public sources with internal company data without hiding where a conclusion came from.
Start with one high-value question, one source policy, and one product surface. We will scope the API or MCP path with you.
A recorded tour of the scientific tools and research workspace.
Recorded on a research prototype. The recording shows the scope demonstrated at that time.
Explore the research floor yourself →Start with a target, a dataset or a research question. Inspect what the evidence supports, what it rejects and what remains unknown.