Streaming 24h · Cash session shut · Connecting · --:--:-- UTC

USD/INR—0.00%EUR/INR—0.00%GBP/INR—0.00%JPY/INR—0.00%AUD/INR—0.00%SGD/INR—0.00%CHF/INR—0.00%HKD/INR—0.00%
Reliance Industries → Singapore · ₹475 cr · ODI

About · 02 — Architecture & functional diagrams

How CorpVidesh AI works, drawn to the grid.

Choose a diagram from the menu. Each one explains how every stage is used and how it connects to the rest of the platform, with a link to the working desk.

05 · Trust & isolation

Tamper-evident, separated

EVENT 1Case openedprev: genesishash: h1linksEVENT 2Checklist completeprev: h1hash: h2linksEVENT 3Form FC filedprev: h2hash: h3linksEVENT 4Lane actionsprev: h3hash: h4linksEVENT 5Proof issuedprev: h4hash: h5Changing any earlier event breaks every later hash — tampering becomes visible. This is record integrity, not blockchain consensus.Private deskscompany-scoped recordsassigned regulator rolesROW ISOLATIONPublic showcase desksshared demo sign-inscannot see private casesServer checks every writerole → company → workflow orderno client-side authority

Boundary: Hash chains prove record integrity only; they are not consensus, approval or certification.

Usage & integration — trust & isolation

01 · Hash chain

UsageEach case event stores the previous event's hash.

IntegrationDatabase trigger locks order; browser re-verifies the chain.

GIFT portal →

02 · Row isolation

UsagePrivate and public showcase desks never see each other's cases.

IntegrationRestrictive database policies per desk and company.

Regulator portal →

03 · Server authority

UsageRole, company and workflow order are checked on every write.

IntegrationLocal selectors never authorise server data.

Security demonstration →