ARGUS
Investigation intelligence
Product tour
The case flow

From a sheet of paper
to a court report

One case, one continuous sequence. The report arrives, the paper becomes data, the machine reads what it extracted, the findings appear, the records are requisitioned and parsed, every source lands on one timeline, the money is followed, and the report is signed. Ten steps — scroll through them.

PaperExtraction FindingsRecords CorrelationMoney Report
STEP 01

A report arrives on paper

An 80-year-old complainant walks into the station. The report is written, signed and scanned — a PDF, or a photograph of a printed form, in whatever script the station works in. At this moment every fact in the case exists only as marks on paper.

FIRST INFORMATION REPORT
FIR / Crime88 / 2026read
Police stationMadurai Cyber Crimeread
SectionsBNS 318(4), 319(2), 61(2)parsed
Complainant80 yrs · 1 contact numberrole: victim
Accused4 WhatsApp numbersrole: accused
Accounts5 · 3 opened by studentsflagged
Total lost₹53,00,000reconciled
Replay
STEP 02

The paper becomes structured data

The officer drags that file into the create-case box and does not touch the keyboard again. Text is lifted in the browser, so the scan itself never leaves the machine. Script is detected; a corrupt text layer is sent to optical character recognition instead of being read as garbage. Twenty to thirty labelled particulars arrive on the server as text, and the case exists.

Indian script detected
புகப்பாளர் முக்கிய புகப்பின் சாரம்
நிகழ்வு நாள் : 12.02.2026
காவல் நிலையம் : மதுரை
read
Script detectedTamil · Noto subsetok
Text layercorrupt — sent to OCRrecovered
Occurrence date12 Feb 2026parsed
Police stationMaduraiparsed
Replay
STEP 03

The machine reads what it extracted

Now the extraction is examined rather than merely stored. The offence narrative is matched against the definitions and the sections are proposed. Numbers are attributed to a role. Individual transfers are reconciled against the stated total, so an incidental figure in the narrative is never mistaken for the sum defrauded.

The callers represented themselves as officers of a central agency, confined the complainant to her home for five days by continuous video call, and by deceiving her into believing a warrant existed induced her to transfer ₹53,00,000 across five transactions to accounts opened in the names of students for a monthly consideration.
BNS 318(4)Cheating
BNS 319(2)Cheating by personation
BNS 61(2)Criminal conspiracy
BNS 336(3)Forgery
IT Act 66DImpersonation by computer
Replay
STEP 04

The findings appear before anything is requisitioned

Fourteen to seventeen observations, each a specific claim with its evidence attached and a link through to the record. The rented mule layer. The absence of any GSM contact at all. The fact that the complaint names one student while the transaction pattern implicates three. None of this required a single external record.

Rented mule layerhighThree beneficiary accounts opened within eleven days, all by students of one college.
No GSM contact at allhighThe accused numbers made no calls to the complainant. Contact was entirely over WhatsApp.
Complaint names one, pattern implicates severalmediumThe complaint names a single student; the transactions span three accounts.
Five-hour session on transfer dayhighA continuous WhatsApp session covering the window in which the first transfer left the account.
Terminal beneficiary identifiedact nowThe trail stops at one account. Marked for freeze.
Replay
STEP 05

Which tells the officer exactly what to ask for

Eight prioritised steps, in order, each naming the record it needs. Preserve first, against the accused-facing numbers only. Requisition CDR and IPDR separately with the exact date range — because on this case a CDR-only notice will come back empty. Serve the bank on the beneficiary and obtain the account-opening file.

Preserve before the window closesNotice to the operator against the accused-facing numbers only — never the complainant’s.
Requisition CDR and IPDR separatelyWith the exact date range. A generic notice returns only the first.
Serve the bank on the beneficiaryAnd obtain the account-opening file, which is where a rented account shows itself.
Resolve the operator after portabilityBefore the notice is drafted, or it reaches the wrong nodal officer.
Freeze the terminal beneficiaryLayer-one money is recoverable; money at the cash-out is not.
Replay
STEP 06

The records come back and are read

The operator’s spreadsheet is dropped in and parses on upload — events, towers, handsets, SIMs and internet sessions. The insight card is written out in sentences, the anomalies are picked out and made clickable, the movement plays back along the timeline, and the coverage is drawn as a sector rather than a circle.

argus / signals — analysis✦ ARGUSAnalysisAI FindingsTimelineEventsDevicesNetworkNight hours9840 71 •••••4,182 events · 12 Jan – 28 Feb 2026 · Airtel, Tamil NaduARGUS INSIGHTSBusiest hour 21:00 · 38% of activity after dark · probable home tower Anna Nagar · 3 handsets on this SIMMOVEMENT MAP · REPLAY▶ play · by day · by week · whole periodACTIVITY · DAY × HOURSilence gap · 3 daysNew frequent contactHandset changeNight tower cluster4,182events219contacts38%after dark3handsets41towers
STEP 07

Ask it anything, in your own words

Four thousand events is not a thing anyone reads. One box takes the question the way an officer would say it, prints how it understood you, and answers — every result starrable into the findings tray with a single click.

number 9840 71•••••
time night hours
place Coimbatore
period March 2026
duration > 5 min
03 Mar9840 71••• → 9500 22•••07:12
11 Mar9840 71••• → 9500 22•••12:48
11 Mar9840 71••• → 8870 41•••06:03
19 Mar9840 71••• → 9500 22•••22:31
Replay
STEP 08

Every source lands on one timeline

The phone extraction, the bank statement and the call records now sit in the same case. Device coordinates are compared against every tower by true distance; device parties are matched against the call records on the last ten digits. Each match is scored, mapped and pinned. This is the sentence that closes the case, and it is produced without being asked for.

argus / case — insights✦ ARGUSCase detailsAI FindingsCase flowDocumentsEvidencesData sourcesReportFIR 88 / 2026 · Madurai Cyber CrimeBNS 318(4), 319(2), 61(2) · NCRP 21902260012345 · ₹53,00,000CASE BRIEFAn 80-year-old complainant was held in a five-day “digital arrest” bycallers posing as officers. ₹53,00,000 moved in five transfers to twobeneficiary accounts, then through three accounts opened in students’ names.PARTIESComplainant1 number, 1 accountAccused4 WhatsApp numbersSuspect accounts5 · 3 rentedAI FINDINGSRented mule layerThree beneficiary accounts were opened within eleven days of each Complaint names one, pattern implicates severalThe complaint names a single student; the transaction pattern spanNo GSM contact at allThe accused numbers made no calls to the complainant. Contact was AI DIRECTION01Preserve records — accused numbers only02Requisition CDR and IPDR separately03Serve the bank, get the opening file04Resolve the operator after portability05Freeze the terminal beneficiary
STEP 09

The money is followed to a freeze list

Victim to beneficiary to mule layer to cash-out, laid out from the bank statement, with pass-through accounts, same-day layering and the terminal beneficiary flagged as the graph is built. In a fraud case this is measured in hours, not days.

argus / finx — money trail✦ ARGUSMoney trailFreeze listAccountsReport₹53,00,000 · five transfers · sixteen accountsBuilt from the bank statement. Layers resolved automatically.VictimComplainant₹53,00,000 outBeneficiaryAccount A₹38,00,000Account B₹15,00,000Mule layerStudent 1rentedStudent 2rentedStudent 3rentedCash-outATM, out of state₹22,00,000Crypto exchange₹19,00,000FLAGGED FOR FREEZEPass-through · forwards 70% or more Same-day in and out Terminal beneficiary Out-of-state ATM Crypto off-ramp
STEP 10

And it ends in a document a court accepts

Everything starred anywhere in the case — on an event row, a tower, a chat message, a correlation — has been collecting in one tray the whole time. Categorised and ordered, it becomes fourteen numbered sections carrying the certificate that Section 63 of the Bharatiya Sakshya Adhiniyam now requires. Nothing is re-typed, and every paragraph traces back to its source row.

argus / report✦ ARGUSFindings reviewCase narrativeCourt reportAudit logREPORT UNDER SECTION 173 BNSSAnalysis of Call Detail and Internet Detail RecordsFIR 88/2026 · Madurai Cyber Crime Police StationACase particularsBConnection and subscriber particularsCData source and integrityDExecutive summaryECommunication statisticsFMost-contacted numbersGLocation findingsHDevice and SIM analysisIKey findings and anomaliesJFeatured eventsKObservations and opinionLSeized devices, chain of custodyMDevice–CDR cross-correlationNCase narrativeCERTIFICATE — SECTION 63(4), BHARATIYA SAKSHYA ADHINIYAM 2023Part A signed by the person in charge of the system. Part B signed by the expert.Every paragraph traces back to a starred finding, and every finding to its source row.
The whole of it, in one sentence. A sheet of paper walks into a police station, and forty minutes later the officer has a structured case, seventeen findings, a prioritised list of exactly which records to requisition and from whom, and a report skeleton that will carry the Section 63 certificate — without having typed a field, reshaped a spreadsheet, or opened a second application.