Regulator approval desk — supervisory side of the rail
One filing. Two entirely different lanes.
You are signed in at the desk — , . This page is what the supervisor sees. An Automatic-route filing is machine-cleared and merely noted; an Approval-route filing stops here until six named desks sign it.
In plain words
Most overseas investments are allowed automatically — the computer checks them and the regulator only records what happened. A few need real permission first, and on those a human officer at each authority has to press approve before the money can move.
AD Category-I bank — live processing
AD Category-I bank — live processing tape
0 eventsNo filing on the rail yet. File one from the Corporate Application desk and every bank action appears here as it happens.
Qwen · reasoning
Statutory reasoning model reads the rule and the filing together, and writes the conclusion with the rule quoted.
LangChain · orchestration
Chains the retrieval, tool calls and checks in a fixed order so every filing is examined the same way.
Alibaba Cloud · compute
Runs the heavy document and screening workloads in an India-resident region.
Federated ledger
Each result is hash-chained into a block every regulator node holds a copy of.
Human desk
A named officer signs this off. The machine only prepares the file.
In plain words
Your bank is the pipe between the company and the regulators. Every action it takes on your file scrolls past above, in the order it happened.
Queue — split by route
Automatic route — machine cleared, noted on the record
Nothing in this lane. File one from the Corporate Application desk.
Approval route — prior permission required
Nothing in this lane. File one from the Corporate Application desk.
Federated blockchain — manual and automated decisions on one chain
The chain starts the moment a filing clears its first checkpoint.
In plain words
Every line above is sealed to the line before it, so nothing can be quietly changed later. Red tags are decisions a person took; grey tags are checks a machine ran. Each regulator keeps its own copy of this record, which is what makes it federated.
Ledger sync — live node health
Federated ledger sync · supervisory view
6 member nodes · All proofs verified
0 ms
Checkpoint ingestion latency
Time from a desk clearing a step to every node holding the block.
—
Last confirmed block
No block committed yet on this device.
0
Confirmed checkpoints
0 checkpoints currently in flight.
0 / 0
Retries / failed proofs
Re-broadcasts and rejected proofs, both regenerated before commit.
Retry and proof-failure log
No retries and no failed proofs on the checkpoints committed so far.
In plain words
This panel shows how quickly each cleared step reaches every regulator's copy of the record, when the last one landed, and whether any had to be sent again before it was accepted.
Regulator action timeline — expand any checkpoint
Select a filing from either lane to open its checkpoint-by-checkpoint action timeline.
In plain words
Open any checkpoint to see exactly which parts a person approved and which parts a machine ran, together with the fingerprint of the evidence sealed at each one.
Audit console — supervisory queue
0 of 0 blocks
Corporate
Checkpoint stage
Officer / designation
Status
From (UTC)
To (UTC)
| Reference | Corporate | Checkpoint | Cleared by | Timestamp (UTC) | Digest | Status |
|---|---|---|---|---|---|---|
| Nothing matches these filters. Widen the stage, officer or UTC window. | ||||||
In plain words
Narrow the record to one company, one checkpoint, one officer or one window of clock time, switch between the blockchain checkpoints and the human action trail — who did what, when, and from which page — and download exactly that selection as a spreadsheet or a PDF. You only ever see the filings your role permits.