Section 07 — Security and federated architecture
A live rail, and a live breach.
Two demonstrations on one page. First, one treasury filing routed to six regulators at once on a federated hash-chained ledger, with the exact hand-off gaps between each authority. Second, a working attack simulation — press a button, watch the rail detect, contain and recover in milliseconds.
In plain words
Money leaving India passes many desks. This page shows those desks working at the same time instead of one after another, and then shows what happens the moment somebody tries to break in or change a number they should not.
01 — Federated routing, treasury to six regulators
Treasury operations
Originating desk
Human desk
Route election, Rule 7 headroom computation and the document set are sealed into one packet and signed with the treasurer's key.
Plain: The company's finance team fills the form once and locks it with a digital signature.
Starts T+0.0s · holds 4.0s · ends T+4.0s
Rail gateway
Validation + fan-out
LangChain · orchestration
Schema, signature and completeness validated, then the packet is split into six regulator-scoped views — each authority receives only the fields its statute lets it see.
Plain: The rail checks the file is complete and then sends each regulator only the part that concerns them.
Starts T+4.0s · holds 3.0s · ends T+7.0s
Federated ledger commit
Hash-chained block
Federated ledger
Block written simultaneously to all eight nodes; a decision is valid only when a quorum of nodes holds the identical hash.
Plain: Everyone gets the same sealed copy at the same moment, so nobody can change it later on their own.
Starts T+7.0s · holds 2.0s · ends T+9.0s
AD Category-I bank
Remitting channel
Alibaba Cloud · compute
Form A2 build, FEMA classification, sanctions rescreen and the funds-availability lock, running in parallel with the regulator window.
Plain: The bank prepares the actual money transfer while the regulators are still looking at the file.
Starts T+9.0s · holds 21.0s · ends T+30.0s
FIU-IND node
Financial Intelligence Unit
Alibaba Cloud · compute · gap +2.0s
Beneficial ownership, PEP and sanctions screening across the whole step-down chain.
Plain: An automatic check confirms nobody behind the deal is on a watch list.
Starts T+9.0s · holds 11.0s · ends T+20.0s
DPIIT node
Sector conditions
LangChain · orchestration · gap +2.0s
Strategic-sector flags and sectoral conditions applied to the target activity.
Plain: The rules for that particular industry are applied automatically.
Starts T+9.0s · holds 14.0s · ends T+23.0s
CBDT node
International taxation
Qwen · reasoning · gap +4.0s
Section 195 withholding and treaty relief tested against Form 15CA/CB, then signed by the assessing officer.
Plain: The tax office confirms the correct tax is held back before the money leaves.
Starts T+11.0s · holds 26.0s · ends T+37.0s
IFSCA node
GIFT IFSC conduct
Human desk · gap +5.0s
Unit conduct, offshore leg and the fund-flow route through the IFSC verified by the conduct desk.
Plain: The GIFT City authority checks the offshore side of the deal is properly run.
Starts T+12.0s · holds 30.0s · ends T+42.0s
MoF (DEA) node
Economic affairs
Human desk · gap +7.0s
Policy conformity for outbound capital of this size and corridor.
Plain: The finance ministry checks the deal fits national policy on money leaving India.
Starts T+14.0s · holds 34.0s · ends T+48.0s
RBI node
Overseas Investment Division
Human desk · gap +9.0s
Rule 10 justification, UIN allotment and the final release instruction to the AD bank.
Plain: The central bank takes the last call and releases the money.
Starts T+16.0s · holds 42.0s · ends T+58.0s
In plain words
Each bar is one desk. Because the bars overlap, six regulators and the bank are reading the same sealed file at the same time. The old paper process runs these one after another, which is why it takes weeks instead of minutes.
Forecast first — Security desk
Singapore · SGD · ₹475 cr · ODI · tape reconnecting
Clearance
This packet will sit for about 21.9 minutes — evidence, not the corridor, is the delay.
Recommended action
Close the 3 open evidence items before release.
Each missing document converts an engine-cleared check into an officer-signed one, which is the only step measured in hours.
Clearance falls to roughly 11.8 minutes.
Also forecast on this desk
A 21.6% chance of a regulator query — and a query resets the clock, not the step.
watchp50 21.6 % · p90 30.3 % — Run the pre-flight evidence tracker and attach the valuation certificate and UBO chart before release.
02 — Live breach simulation
Synthetic intelligence theatre · 3D federated mesh
All four attacks, automated end to end. The mesh below is the live ledger in three dimensions — eight nodes, every hash link drawn, the hostile vector shown arriving and being cut.
Run parameters · reproduce an exact outcome
Pressure of the hostile vector: consensus pulse weight, halo strength and spin rate.
How many sealed ledger copies are drawn in the federated mesh.
Share of nodes that must agree before the record commits.
The 4200 ms response stretched over this many seconds of wall clock.
Pause on the restored state before autopilot injects the next breach.
Run signature · int=1.0 · nodes=8 · quorum=75% · window=4.2s · hold=1.6s
Parameter presets · reproduce a run exactly
No presets saved yet. Set the sliders, name the configuration and save it — it is stored on this browser and reloads the exact same run.
01 · queued
Unauthorised access attempt
02 · queued
Ledger tamper attempt
03 · queued
Bulk data exfiltration
04 · queued
Payment instruction hijack
Live performance metrics · this run
T+0 ms · lanes 0/6Time to quorum
—
Run an attack to measure
Avg lane latency
—
Mean processing time across the six regulator lanes at this intensity
Containment
—
Enough honest nodes remain to commit the containment decision
Success rate over time
—
Completed runs accumulate here
FIU-IND nodeAlibaba Cloud · compute
waiting · 0 ms / 561 ms
DPIIT nodeLangChain · orchestration
waiting · 0 ms / 715 ms
CBDT nodeQwen · reasoning
waiting · 0 ms / 1327 ms
IFSCA nodeHuman desk
waiting · 0 ms / 1531 ms
MoF (DEA) nodeHuman desk
waiting · 0 ms / 1735 ms
RBI nodeHuman desk
waiting · 0 ms / 2144 ms
Deviation alerts and telemetry archive
Lane latency ceiling
420 msAny regulator lane that clears slower than this raises an alert.
Time-to-quorum ceiling
1600 msAlerts when the mesh takes too long to agree on containment.
Success-rate floor
80 %Alerts when containment across completed runs falls under this share.
Alert feed · newest first (0)
Nothing has crossed a threshold yet. Raise the intensity, widen the quorum requirement or lower a ceiling above and run an attack to see the feed fire.
In plain words
You set the limits: how slow a regulator lane may be, how long agreement may take, and how often containment must succeed. Cross any of those and a line appears here as it happens. The two export buttons save everything — the limits, the run history, the lane times and every alert — as a spreadsheet file or a machine-readable file you can archive.
In plain words
Press one button and the rail attacks itself four times in a row while you watch. The rotating picture is the actual network of eight sealed copies: red lines are live agreement between them, the outside dot is the attacker, and you can see the moment the line to it is cut.
Rail status · Secure — no incident
Pick an attack above. The response below runs on a real clock, in milliseconds, exactly as the rail would behave.
In plain words
Nothing here is a screenshot. The timings, the containment order and the evidence fingerprints are produced live each time you press the button — and every one of those events is written into the same shared ledger the regulators read, so an incident can never be quietly deleted.
03 — Why a federated design survives this
No single copy to attack
Eight nodes hold the same hash-chained record. A change is only real when a quorum agrees, so breaking one machine changes nothing.
Everyone holds an identical sealed copy, so one bad copy is simply outvoted.
Least-sight by statute
Each regulator node receives only the fields its own statute entitles it to read. There is no all-seeing account to steal.
No single login can see everything, so no single stolen password is worth much.
Value never moves on trust
The release instruction is checked against the beneficiary hash sealed at clearance. A changed account halts the payment before value leaves India.
Money can only go to the account that was approved — nothing else.
Security response — 3D process simulation
Detection to containment on the federated mesh, with the ledger untouched.
Live USD/INR
₹86.9565 ▬
Tape status
Syncing
Print sequence
#0
Paper today → rail
24 days → 9 min
Who acts
Mesh sensors
What happens at this stage
Anomalous access or payload detected on a lane.
Elapsed 2s of 18s on the rail · stage cost 2s
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.