Inspection Session
Read-only sessionYou are reading the live obligation register of one SEBI-registered stock broker in a read-only inspection session. The clause citations, evidence hashes and audit chain are the record — the prose is only navigation. Nothing on this side of the session can approve, edit or upload.
The inspection route runs claim → clause → evidence → history. Take the four stops in order, or jump to whichever question you came with.
Each of the 43 register entries carries a verbatim clause excerpt with character offsets into the circular text. Open any row, open the cited paragraph, and confirm the obligation says what the regulation says — no paraphrase stands between them.
43 entries · clause-grounded · 33 base + 10 CUSPA delta
24 artifacts — documents, data-checks and live scans — each stamped with its connector of origin, capture time and content hash, and bound to the obligations it evidences. Where evidence is absent, the register shows a gap rather than a claim.
24 artifacts · hashed · connector provenance on every item
56 hash-chained events from first ingest (Jun 2025) to sim-today: every obligation created, evidence bound, mapping approved and amendment applied, with agent or human attribution. Run the chain verification yourself — a single altered event breaks the chain.
56 events · GENESIS-anchored · agent + human actors attributed
A read-only, inspector-scoped MCP endpoint exposes 7 query tools over the identical record this session renders — obligations, mappings, evidence, amendments, gaps. Your own tooling gets byte-for-byte the answers you see here.
7 tools · read-only scope · same record, machine-readable