How we build
Any single platform in this portfolio can be copied. What is harder to copy is the rate at which the next one gets built, and the fact that the fourth one costs a fraction of the first. That rate is a written method, not a habit and not a temperament, which is the only reason it survives the person who wrote it.
Published here because it is the part a serious engineer or operator will want to interrogate before anything else, and because nobody at this tier publishes it.
The bench
An experienced engineering bench of 50 practitioners, across banking, land and health infrastructure. The bench flexes with the work; the method does not.
Four disciplines
These are the four that survived contact with real builds. They are stated with the mechanism attached, because the mechanism is the only part that can fail visibly — and a discipline that cannot fail visibly is not being practised.
01
The platform is shaped to the enterprise’s own process, data and behaviour, rather than the business being bent around a template.
The mechanism. That process is written down first, and acceptance criteria are written against it — each one naming the evidence that would satisfy it. Work that meets no criterion is out of scope by construction, so scope has to be changed deliberately rather than absorbed quietly.
02
The reviewer is never the author. Nothing is certified by the person who made it, including the instruments that do the certifying.
The mechanism. A build is graded against the contract it opened with, by a reviewer holding the contract rather than the intent, and the grade is sceptical by default — a thing is not working until it has been shown working.
03
A choice made in July can be examined in December, including the options that were rejected and why they were rejected.
The mechanism. A decision record states the alternatives, the reason, and what would have to change for it to be reopened. A decision that names no condition for its own reversal is a preference wearing a decision’s clothes.
04
What more than one platform needs is built as one component behind a boundary and consumed by all of them, rather than rebuilt slightly differently each time.
The mechanism. A component shared by more than one platform is specified with a boundary, an interface and a data contract before it is extracted — and if it cannot be specified that way, it is not shared infrastructure yet and does not get treated as if it were.
Isolation
Each customer’s data, identity and audit trail are isolated by default rather than by configuration. One customer’s failure is not another customer’s incident.
Isolation by default rather than by configuration is the distinction that matters. A boundary that has to be switched on is a boundary somebody eventually forgets to switch on.
AI as architecture
Models read, extract and draft. They do not decide what is true, move money or transfer a legal interest — those steps terminate in a record a person is accountable for.
The distinction is architectural rather than editorial. A model sits where its output can be checked against something, and the check is part of the design rather than a policy written next to it.
Transition
The new system runs alongside the old one against live data before anything is cut over, and the old one is decommissioned only once the record has been reconciled.
Standards
Named so they can be checked, and stated as what the work is built against rather than as an approval anyone has granted it.
Commercials
Engagements are structured against defined outcomes. What counts as the outcome is written down before work starts, which is the first discipline applied to the commercial relationship.
What you get
A published method is only worth reading if it changes what you receive. Four things follow from ours — and because a page claiming only upside is not credible, each one names what it costs us to keep.
Acceptance criteria are agreed before anything is built, so what “finished” means is your sentence rather than ours, settled while it is still cheap to change. It costs the first build real time, at the point where enthusiasm is highest and patience lowest.
An independent gate returns work, including work that felt finished. That is unpleasant on our side of it, and it is the entire point — the alternative to being told by your own instrument is being told by your customer.
Every consequential decision is recorded with its reasoning, so a handover, an audit, or a new team six months on inherits the argument and not only the artefact. Recording a decision costs more than making one, and it is paid now and collected later.
What more than one platform needs is built once and consumed by all of them, so you inherit a part that has been in production rather than paying for its first version. Pulling a component out behind a clean boundary is real engineering with no visible feature at the end of it.
The honest summary is unchanged: this method is a poor choice for one product built once, and it compounds from about the third. The group is in the business of the third build — which is what makes the trade a good one here, and would not make it a good one everywhere.
Where it shows
Each platform in the portfolio was built this way and each one consumes components the others paid for. That is the whole argument for holding them together rather than separately.
Written answers
The questions people actually ask, answered in advance. Nothing on this panel is generated.
It builds and runs the systems of record for assets in the real economy — land, trade, capital and provenance. One engineering group and one method, across seven platforms.
Stactray Private Limited, incorporated in Pune in 2024, CIN U74909PN2024PTC231186. Two named officers: Sandeep Musti, Chief Executive Officer and signatory; Sunil Musti, Co-Founder, Strategy and Product.
Digital Personal Data Protection Act 2023 and India Stack — DEPA, Account Aggregator, ONDC. NIST CSF. OWASP ASVS. W3C Verifiable Credentials. OpenAPI. WCAG 2.2 AA. These are standards the work is built against, not approvals anyone has granted it.
Against defined outcomes rather than elapsed time or seats. What counts as the outcome is written down before work starts.
Yes. Data, identity and audit trail are isolated per customer at the platform boundary, by default rather than by configuration.
No. It does not manage third-party money and does not operate a fund or any pooled vehicle. Nothing on this site is an offer, an invitation or a solicitation of any kind.
A five-axis framework the group applies to its own platforms, asking in five ways what survives when the analysis layer above it becomes cheap. The framework is published; what any platform reads against it is not.
Not answered here? enterprise@stactray.tech reaches a named officer, not a queue.