Graduated drawdown ladder
Losses do not hit a single cliff. Risk is withdrawn in stages, so a bad morning narrows the book instead of ending it.
Reduce New risk halved
Block No new entries
Flatten Book closed
Pravrtti Elements · built with Codexonic
Built to refuse.
PRAMITT runs your strategy, byte for byte, and wraps it in a risk layer that can only tighten — never widen. Loss mitigation outranks profit here. That is a rule the code enforces, not a value on a slide. Beyond execution sits a four-part capability ladder that is built but mostly withheld — and we publish exactly which rung ships.
The ledger below is a recorded replay of the 2026-07-16 tape across the full F&O universe, with option chains approximated from candles — research grade, which is why not one of its rows is evidence-eligible. No live capital is deployed, and no return is claimed.
204 of 210 evaluated 3 entered 201 refused
Controls may tighten, never widen Broker ambiguity halts — it is never re-placed on another venue A paper profit confers no live authority Four parts are built; only execution ships Missing data refuses loudly A simulation may never become evidence Your strategy is immutable — a bug is flagged, never silently fixed One enforced risk authority, no bypass
01 Why this exists
Nothing in this architecture is a preference. It is a response.
The system that came before PRAMITT had a risk manager. It sat beside the engine — advisory, bypassable, and never a binding authority. An AI sat in the trade-approval path. No edge was ever measured before capital went in. Every one of those three facts is now structurally impossible.
What failed
- Risk controls that advised rather than bound.
- A model with a seat in the approval path.
- Live capital ahead of a measured edge.
- One monolith, so one failure reached everything.
What replaced it
- One enforced authority that every order path must clear.
- Models are advisory only, with no live order path at all.
- Go-live is human-gated behind a fresh edge attestation.
- Per-tenant isolation: one account's failure is quarantined.
02 The capability ladder
Each rung is built on the ones before it.
You cannot buy suggestions on a book we do not run, nor the overlay without all three rungs beneath it. The four parts compose upward; none of them detaches into a product you could purchase on its own.
A, B, C and D are all built. Only A ships. We publish that gap the same way we publish that our own strategy is inconclusive — because a vendor who overstates its roadmap will overstate your returns.
-
Execution
Live · paperYour bible executed byte for byte — backtest and paper today. Live is built and deliberately gated shut at the control plane until a human-approved paper-to-live transition exists.
The foundation — B, C and D each build on it
-
Model suggestions
Built · withheldThe channel is built and provably cannot place an order — but it ships silent. With no news corpus and no fitted model, its honest output today is abstentions. We would rather emit nothing than fabricate a signal.
Builds on A
-
Observation → proposal
Built · no client surface yetWatches your strategy and proposes a new or modified one — proven end to end on a client's own recorded evidence. It is a suggestion only: nothing changes until you put it in. Today a proposal reaches an operator, not yet you.
Builds on A
-
Freehand overlay
Built · paper-only by construction PaperAI trading on your base strategy with freehand. Paper-only is an unforgeable property of the object, not a configuration flag — it has never run outside its own tests, and cannot.
Builds on A, B and C
03 The order path
Five gates. The quantity only ever falls. None can add.
This is the entire route from a signal to an order. There is no second route. A quantity can be reduced or refused anywhere along it, and increased nowhere — no gate, advisory, model or operator can widen a cap your strategy did not ask for.
- Gate 01
Your strategy
Proposes
Your logic, unmodified and content-hashed. Immutable in CI — a bug we find is reported to you, never quietly patched.
- Gate 02
Shrink-only controls
May reduce
Six advisory domains — capacity, portfolio, stress, surveillance, treasury and mitigation — submit content-hashed constraints. Each is re-validated at the install boundary; one that widens is rejected outright.
- Gate 03
BasicGuard
May refuse
The sole enforced risk authority, scoped per tenant. No order path in the system may bypass it, and none is permitted to exist that does.
- Gate 04
Venue checks
May refuse
Capability and margin, verified against the broker. If margin cannot be confirmed, the order is blocked — never assumed into existence.
- Gate 05
Order intent
Records
Only now does an intent exist. If the venue's answer is ambiguous it is reconciled and halted — never re-placed somewhere else on a guess.
Quantity surviving 1,200 at gate 01 · proposed
Reduction is the only direction of travel. A strategy that asks for 1,200 may leave with 500 — or with nothing. It can never leave with 1,201.
04 The loss stack
The controls that run whether or not anyone is watching.
A supervised loop evaluates these on every tick. They act only by reducing a submitted quantity, tripping a kill switch, or halting the guard — never as a parallel enforcer competing with it.
Kill-switch hierarchy
Three scopes. The widest one always wins.
PlatformAll tenants
TenantOne account
StrategyOne book
Reconciling failover
Three venues behind one execution contract. When a venue's answer is ambiguous, the platform reconciles and halts — it does not re-place the order elsewhere and risk a double fill.
UpstoxPrimary
DhanStandby
ZerodhaAmbiguous · halted
Fail-closed margin monitor
The dangerous state is not "low margin" — it is "margin unknown". If headroom cannot be verified, new risk is blocked, which is what keeps a broker's auto-square-off from making the decision for you.
Verified headroom · unverified region is blocked, not estimated
Fat-finger guard
Notional, quantity and price sanity, applied before anything reaches a venue — including to the platform's own operators.
Qty × 100 · refused
Blast-radius containment
Every client runs in an isolated runtime with its own guard, capital, state namespace, decision log and kill switch. A crash or a halt is quarantined to that tenant — it is never allowed to propagate, and the platform-wide roll-up never nets a single tenant's breach away into an average.
05 The rulebook
Principles are optional. These are not.
Every rule below has an enforcement point in the source tree. A test asserts that each one is still enforced, so a rule cannot decay into a comment. There are no warnings — a rule either halts, refuses, or fails the build.
Rulebook fingerprint e060d375a84a8a60de59ffcb5cdad4ad38b1bc2350a3194e2e60ea36327875de
P1-paper-only Prime Halt
No real order may ever be placed. Every execution path is paper or dry-run.
Not waivable. A live adapter would require an explicit flag
plus credentials that do not exist in this system.
P4-strategy-ip-immutable Prime Fail CI
Client strategy IP is immutable. It changes only via a ledgered owner
acknowledgement whose hashes match the pushed bytes exactly.
A strategy bug is flagged and reported. It is never
silently fixed — your logic is not ours to edit.
R1-single-enforced-authority Risk Halt
BasicGuard is the sole enforced risk authority. No order path may bypass it.
The predecessor system's risk manager was advisory.
This is the rule that closes that hole.
R3-loss-mitigation-outranks-profit Risk Refuse
Where a change trades safety for return, safety wins. No component may promise
or imply a return; edge must be measured before it is claimed.
This rule is why there is no performance chart
anywhere on this page.
D4-no-fabricated-values Data Refuse
Missing or unusable market data refuses loudly. It is never silently replaced
with a zero, a stale value, or a guess.
A fabricated input produces a confident, wrong
decision — the most expensive kind.
X1-no-lookahead Execution Refuse
A decision made on a bar fills at the next bar's open. No component may consume
information it could not have known at its decision timestamp.
Paired with X2: the same inputs must reproduce the
same outputs, to the rupee, on replay.
G4-no-exceptions-without-a-waiver Governance Halt
There are no exceptions except an owner-ratified waiver naming the rule, the
actor, the reason and an expiry.
Urgency, convenience, a green test suite and a
persuasive argument are explicitly not waivers.
06 Evidence
Our own strategy has not passed the gate. So we say so.
Every setup a strategy sees is written to a ledger — including the ones it declined, which is what makes an honest comparison possible at all. The statistical gate then needs sixty independent sessions before it will even consider returning a verdict of EDGE.
We are at one. So the verdict is INCONCLUSIVE, and it will stay that way until the arithmetic says otherwise. A platform that would overstate its own results would overstate yours.
1 of 60 sessions recorded 59 short of quorum
- Nulls compared
- — none; the gate stops before n=2
- Search space priced
- 14 tunable parameters
- Deflated Sharpe
- — not computable at n=1
- Evidence grade
- live-chain rows only · none recorded
The haircut for parameter search is applied before any verdict, so a strategy cannot pass by being tuned until it looks good. An INCONCLUSIVE result is the gate working, not the gate failing.
07 Bringing a strategy
Four stages, and a human at the only one that matters.
Your strategy is validated, never edited. Nothing advances a stage automatically, and the final stage does not advance without a person deciding it should.
-
Ingestion
A static safety scan rejects filesystem, network and dynamic-execution access. A behavioural sandbox then runs your code against bar context alone, checking it is deterministic, well-formed and bounded.
Validates · never edits
-
Release
The accepted version is content-hashed into an immutable registry. Every production run afterwards re-verifies that hash against the bytes on disk, so no run can assert a strategy by name alone.
Hash-pinned · versioned
-
Shadow
It runs in paper alongside the incumbent, writing every setup it sees to the ledger — refusals included. Drawdown, not return, is the primary comparison.
Paper · fully recorded
-
Gated go-live
Promotion requires a fresh attestation and a human approval, recorded in a hash-chained ledger. A challenger that worsens drawdown is retired even when it has an edge.
Human decision · reversible
08 Claims we refuse to make
Everything a platform like this would normally tell you, and why we won't.
01
Guaranteed returns
No component may promise or imply a return. That is rule R3, and it is enforced in the tree — not a disclaimer bolted on at the end.
02
AI that predicts the market
The learning layer has no live order path at all. Today it ships silent: with no news corpus and no model fitted to your book, it abstains rather than emit a signal. When it does speak, its advice can only tighten — and still never touches an order path. The last system put a model in the approval path; that is precisely what we removed.
03
Production-ready today
It is not, and we publish the gap. Direct live onboarding is disabled, venue behaviour is not yet certified with credentials, and the option loss envelope is not economically complete. You will hear that from us before you hear it from your P&L.
09 Posture & custody
Your IP, your data, and where we stand with the regulator.
Three questions every desk asks before a walkthrough — answered in the open, not buried in an accordion.
Your IP
Your strategy is immutable and owner-controlled. The platform validates it, hashes it and runs it — it never edits it. If we find a bug in your logic we report it to you; we do not fix it, because a silent fix would mean you are no longer running the strategy you approved.
Corpus participation is a separate, explicitly negotiated agreement — never a default.
Your data
The access form on this page opens your own mail client and stores nothing — no server receives it and this page keeps no record. Inside the platform, every client runs in an isolated runtime with its own guard, capital, state namespace and decision log.
One tenant's state is never pooled with another's, and the platform-wide roll-up never nets a single tenant's breach away into an average.
Regulatory standing
SEBI's algorithmic-trading framework has been mandatory since 1 April 2026. A written posture memo sets out the classifications a platform like this could sit in, the bright lines for each, and the controls we hold against them.
The classification decision itself sits with the board and SEBI counsel. We will not describe ourselves as registered or empanelled until we are.
10 Engagement
Scoped to what you actually need protected.
Commercial terms are set per engagement against your capital, venue count and strategy complexity — so we quote after a walkthrough rather than pricing a risk envelope we have not seen.
- Individual traders A small book and one strategy — execution and the loss stack from day one.
- HNIs Larger capital where the downside, not the upside, is the whole point of the mandate.
- Hedge funds & institutions Desks and corporates bringing their own strategies at scale, on negotiated terms.
Part D is paper-only for every segment, hedge funds included. The overlay's paper confinement is an unforgeable property of the object, not a setting a larger client can negotiate off — there is no branch that turns it off for anyone.
Automation
For a desk that already trusts its strategy and wants it executed the same way every single session.
- Deterministic execution of your strategy, unmodified
- Full setup ledger, refusals included
- Point-in-time replay of any past session
On the roadmap — not yet shipping
- Multi-broker spine with reconciling failover — built and tested; reachable once live onboarding opens
Most engagements
Automation + mitigation
For capital where the downside matters more than the upside — the reason this platform exists.
- Everything in Automation
- The full loss stack: ladder, margin monitor, fat-finger, kill hierarchy
- Isolated per-tenant runtime with its own guard and capital
- Gated lifecycle with human-approved promotion
On the roadmap — not yet shipping
- Portfolio-level risk analytics and stress replay — computed today, not yet surfaced on the console
Platform partnership
For desks willing to contribute strategy behaviour to the training corpus on negotiated terms.
- Everything in Automation + mitigation
- Direct line to the engineering team
On the roadmap — not yet shipping
- Corpus participation under an explicit IP agreement
- Early access to platform-generated candidates, gate-cleared only
11 Straight answers
The questions that actually get asked.
No. Every execution path is paper or dry-run, and direct live onboarding is disabled in the codebase. That is enforced by the first rule in the rulebook, which is not waivable. When it changes, it will change as a deliberate, ledgered decision — not as a configuration flag someone flips.
We will not answer that, and you should be wary of anyone who does. The honest statement is: expected return is unknown until an edge verdict is measured on your strategy; downside is structurally capped by the loss stack; and the catastrophic case — an unbounded, unattended drawdown — is what the architecture exists to exclude.
Upstox, Dhan and Zerodha sit behind a single execution contract, with official-source and catalog-identity boundaries implemented for all three. Credentialed venue and account behaviour is not yet certified, which is why the platform stays in paper — that certification is a prerequisite, not a follow-up.
The order is reconciled against broker truth and the path halts. It is never re-placed on another venue on the assumption that the first one failed — that assumption is how a hedge becomes a double position. Broker truth must also arrive scoped to your broker and account, even when the book is empty; an unscoped snapshot blocks callbacks and blind exits until an exact one is available.
Request access
Bring us the strategy you are most afraid of.
A walkthrough is a working session, not a pitch: we run your strategy through ingestion, show you the ledger it produces — refusals and all — and tell you plainly where the platform is not yet ready for it.
Pravrtti Elements Pvt Ltd · built in partnership with Codexonic.