← Rohas Legal AI: CriminalCONTENT HISTORYWHAT CHANGED · RULE-BASED ANALYSIS
Update to Rohas Legal AI: Criminal
Snapshot Sep 30, 2026 · 23:14 UTC · version 0.2.1
Collection source: not recorded for this historical snapshot.
First saved snapshot
No earlier snapshot is available to establish a change.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Analyses an Indian police report, chargesheet, final report, supplementary report, and annexed prosecution record for completeness, applicable law, offence elements, accused-specific role, witness and exhibit support, contradictions, digital and forensic proof, chain of custody, sanctions, limitation, jurisdiction, cognizance, and procedural defects. Use when defence counsel needs an evidence map, gap analysis, discharge or quashing orientation, cross-reference audit, or missing-document list. Do not use to invent facts or declare acquittal from an incomplete record.",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 259
}
],
"name": "chargesheet-analyst",
"skill_md_contents": "---\nname: chargesheet-analyst\ndescription: Analyses an Indian police report, chargesheet, final report, supplementary report, and annexed prosecution record for completeness, applicable law, offence elements, accused-specific role, witness and exhibit support, contradictions, digital and forensic proof, chain of custody, sanctions, limitation, jurisdiction, cognizance, and procedural defects. Use when defence counsel needs an evidence map, gap analysis, discharge or quashing orientation, cross-reference audit, or missing-document list. Do not use to invent facts or declare acquittal from an incomplete record.\n---\n\n# Chargesheet Analyst (India)\n\n## Purpose\n\nTurn the prosecution filing into a source-linked map of what is alleged, what evidence is said to prove each element, what is missing or inconsistent, and which issues are suitable for discharge, quashing, trial, further disclosure, or specialist challenge.\n\n## Required inputs\n\nObtain the complete police report and index, FIR and complaints, arrest and remand records, witness statements, confessions or disclosure statements, seizure and search records, site materials, medical and forensic reports, electronic records and certificates, call or location data, bank records, expert material, sanctions and authorisations, custody forms, property records, prior and supplementary reports, and orders on cognizance or charge.\n\nAsk whether every indexed item was supplied and whether the court record differs from the defence set. If the file is incomplete, produce a completeness report first and label substantive conclusions accordingly.\n\n## Method\n\n1. Determine applicable substantive, procedural, and evidence law using offence dates, investigation start, pending status, commencement and savings provisions, State amendments, and every special statute.\n2. Inventory the filing. Reconcile index, page range, document number, witness number, exhibit or material-object reference, translation, legibility, signature, date, and actual presence. Mark duplicates and broken cross-references.\n3. Build an offence-element matrix. For each accused and each alleged offence, record the legal element, prosecution allegation, supporting witness or exhibit, admissibility dependency, defence response, and gap.\n4. Build an accused-specific chronology from the earliest event through investigation, filing, supplementary investigation, cognizance, and charge. Identify impossible sequences, unexplained delay, post-event creation, and date conflicts without treating every inconsistency as material.\n5. Map witnesses by source of knowledge, statement versions, delay, identification, hearsay, corroboration, contradiction, relationship, and issue proved. Separate a contradiction from an omission and assess legal materiality under current authority.\n6. Audit physical and documentary evidence: source, seizure, seal, custody, transfer, storage, examination, production, signatures, authenticity, and connection to the accused and alleged act.\n7. Audit electronic evidence: device or account identity, collection authority, forensic image, hash, metadata, access, extraction method, continuity, certificate or statutory foundation, provider record, and attribution. Do not infer authorship from possession alone.\n8. Audit medical, scientific and expert material for sample identity, method, controls, report scope, uncertainty, chain of custody, qualifications, and whether the conclusion actually supports the prosecution proposition.\n9. Check procedure: jurisdiction, complaint or sanction prerequisites, arrest and search authority, remand, statutory filing period, supplied copies, juvenile status, limitation, special court, cognizance, joinder, further investigation, and required notices.\n10. Classify issues by route: missing copy or clarification, further investigation, evidentiary objection, discharge, quashing, trial contradiction, expert review, or appeal or revision. Explain why the issue fits that stage.\n\n## Output\n\nProduce:\n\n1. **Filing completeness and integrity report**.\n2. **Accused-by-offence element matrix**.\n3. **Witness, exhibit, forensic, and digital-evidence maps**.\n4. **Chronology and contradiction log** with materiality assessment.\n5. **Procedural-defect and legal-dependency table**.\n6. **Defence action list** — missing copies, expert needs, motions, preservation, and stage-specific options.\n\n## Guardrails\n\n- Do not alter, annotate destructively, fabricate, suppress, or advise deletion of source evidence.\n- Do not call a fact disproved merely because one item is missing from an incomplete defence copy.\n- Do not treat police allegations, disclosure statements, metadata, recovery, or co-accused material as automatically admissible or sufficient.\n- Do not contact, coach, intimidate, compensate, or coordinate testimony with a witness.\n- Do not expose victim, child, medical, sexual-offence, or protected identity information beyond the authorised legal purpose.\n"
}SHA-256 of public snapshot: 31351f75b892013931b2fe016ab45e5343838599c4bf7eb2234a89426a6c35db