A session is research material, not advice
A session is the full record of an AI research run: the papers Argus read, the hypotheses it registered, the code it ran, the checks each claim had to pass, the audit, and the questions reviewers put to it. It is produced by software and checked by fixed code, not by a human expert in your field.
A session is not legal, medical, financial, investment or any other professional advice, and it is not a substitute for peer review or for expert judgement in a regulated domain. Use it as evidence you can inspect, not as a final answer.
What a verdict means
Each hypothesis in a session ends with a recorded verdict and the evidence behind it:
- Supported means the hypothesis's registered test came out as predicted, and every check that covers the claim passed. If a prediction was registered after its result, the audit says so. Where a fixed checker exists, as for the size and distance of a code, its result decides.
- Inconclusive means the evidence did not settle the question either way. The session says what was tried.
- Set aside means the hypothesis was dropped, with the reason recorded. It stays in the session.
An audit agent compares each verdict with the evidence and may disagree; its reports are part of the session. A passed check covers what that check tests and nothing more. None of these labels is a warranty of truth.
Errors, corrections, retractions
We will make mistakes. What matters is how quickly and visibly they are corrected. If you spot something wrong in a published session, email connect@obvix.io with:
- The session's link, as shown in your address bar.
- The disputed claim, quoted.
- The evidence for your correction: sources, data or code.
Then:
- We acknowledge within five business days, in writing, with a reference number.
- We check it. Where the correction holds, we revise or retract the affected claim, record the change with its date and evidence, and publish a new revision. Earlier revisions stay readable.
- Where we disagree, we write back with our reasoning and the underlying evidence.
What we do not take on
We decline questions that ask Argus to:
- Investigate a named private individual, including their medical, financial or personal history.
- Produce material designed to harass, deceive or coerce an identifiable person or group.
- Help with anything illegal in India, the United Kingdom or the European Union.
We may also decline a question because code could not check its answer, or because it is too broad to scope. We will say so.
Citing an Argus session
Each published session has a readable address at argus.obvix.io/library/<slug> and an unchanging revision address containing /published/<slug>/r/<revision>/. Published sessions are licensed under CC BY 4.0. For an exact citation, use the revision address:
Argus (Obvix Labs). 2026. <Session title>, revision <n>. argus.obvix.io/published/<slug>/r/<n>/ (accessed YYYY-MM-DD).
We add a new revision whenever a published session changes. Record the revision number and access date; the readable library address can later point to a newer revision.
Commitments we hold ourselves to
- Public questions we accept, and research Obvix Labs runs itself, are published in full for everyone, free. Private research stays private unless its owner chooses to publish it.
- We publish sessions whole, including the hypotheses that failed. We do not edit a session's record for the page.
- Public research is free. Private research is paid for the work, never for a particular outcome.
- We publish corrections in the same place and at the same visibility as the original.
Limits of liability
Subject to applicable law and the limitations in our Terms of service, Obvix Labs Private Limited's aggregate liability arising from or related to a session is capped at the greater of (a) ₹10,000 or (b) the amount you paid Obvix Labs in the twelve months before a claim arose. We are not liable for indirect, incidental or consequential damages, including lost profits, lost business opportunities or reputational harm, except where that harm is the direct and proximate result of an error we failed to correct after timely notice.
These limitations apply to the maximum extent permitted in your jurisdiction.
Contact for corrections
For corrections and complaints, write to connect@obvix.io with a subject line beginning Correction:. We escalate these internally within 24 hours of receipt.
Last updated: 14 November 2026.